You can subscribe to this list here.
2011 |
Jan
|
Feb
|
Mar
(38) |
Apr
(34) |
May
(20) |
Jun
(46) |
Jul
(6) |
Aug
(13) |
Sep
(50) |
Oct
(27) |
Nov
(10) |
Dec
(3) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2012 |
Jan
(7) |
Feb
(3) |
Mar
(4) |
Apr
|
May
|
Jun
(2) |
Jul
(4) |
Aug
(3) |
Sep
(1) |
Oct
(2) |
Nov
|
Dec
|
2013 |
Jan
(1) |
Feb
|
Mar
(4) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Paul P. <bay...@gm...> - 2011-08-04 07:01:15
|
FYI - daemon threads are now implemented, so if you update, applications will now terminate appropriately. Thanks, Paul On Wed, Aug 3, 2011 at 11:07 AM, Arno Puder <ar...@pu...> wrote: > > I suggest you write yourself a little shell script based on the > instructions I mentioned in my last message. > > Arno > > > On 8/3/11 9:01 AM, Shai wrote: > > Thanks Arno that explains allot. > > How do I add this to the build process at least for now (until there is > > a more official plugin architecture)? > > Do I just place the file in the native directory and recompile xmlvm? > > Do I need to list it somewhere in the build process? > > > > Thanks, > > Shai. > > > > ------------------------------------------------------------------------ > > *From:* Arno Puder <ar...@pu...> > > *To:* "Xml...@li..." > > <Xml...@li...> > > *Sent:* Wednesday, August 3, 2011 6:30 PM > > *Subject:* [xmlvm-dev] Native methods in the C backend > > > > > > there was a question on the mailing list regarding the native interface > > for the C backend. While XMLVM already makes extensive use of the native > > interface when cross-compiling Apache Harmony, we have not exposed this > > functionality in a proper way for applications. However, here a little > > how-to showing how this can be done. 'Proper' support would just do a > > better job at integrating the following steps into the XMLVM toolchain, > > but the basic principles would remain the same. > > > > Consider the following class NativeTest. The idea is to provide an > > implementation for nativeMethod() that prints out the array and then > > calls back to a Java method: > > > > package xmlvm; > > > > public class NativeTest { > > > > native void nativeMethod(int[] intArray); > > > > void methodToBeCalledFromNative() { > > System.out.println("Hello from methodToBeCalledFromNative()"); > > } > > > > public static void main(String[] args) { > > int intArray[] = {2, 4, 6, 8}; > > NativeTest instance = new NativeTest(); > > instance.nativeMethod(intArray); > > } > > } > > > > javac NativeTest.java > > xmlvm --in=NativeTest.class --out=out --target=posix > > mv out/src/xmlvm.m out/src/xmlvm.c > > xmlvm --in=NativeTest.class --out=native \ > > --target=gen-c-wrappers --gen-native-skeletons > > # Ignore the error that the last command will generate. This command > > # will generate a skeleton file for nativeMethod(). > > # In file native/native_xmlvm_NativeTest.c out/src/ inject the following > > code: > > > > //XMLVM_BEGIN_NATIVE[xmlvm_NativeTest_nativeMethod___int_1ARRAY] > > xmlvm_NativeTest* thiz = me; > > printf("Hello from nativeMethod()\n"); > > org_xmlvm_runtime_XMLVMArray* intArray = n1; > > JAVA_ARRAY_INT* data = (JAVA_ARRAY_INT*) > > intArray->fields.org_xmlvm_runtime_XMLVMArray.array_; > > int length = intArray->fields.org_xmlvm_runtime_XMLVMArray.length_; > > for (int i = 0; i < length; i++) { > > printf("%d, ", data[i]); > > } > > printf("\n"); > > #ifdef XMLVM_VTABLE_IDX_xmlvm_NativeTest_methodToBeCalledFromNative__ > > VTABLE_PTR func = > > > thiz->tib->vtable[XMLVM_VTABLE_IDX_xmlvm_NativeTest_methodToBeCalledFromNative__]; > > (*(void (*)(JAVA_OBJECT)) func)(me); > > #else > > xmlvm_NativeTest_methodToBeCalledFromNative__(me); > > #endif > > //XMLVM_END_NATIVE > > > > cp native/native_xmlvm_NativeTest.c out/src/ > > cd out/dist/ > > make > > ./build/out > > > > A few comments: the purpose of the special comment markers > > //XMLVM_BEGIN_* and //XMLVM_END_NATIVE is to clearly distinguish between > > generated portions of the file (outside the special markers) and > > injected code (inside the markers). When the skeleton is regenerated via > > --gen-native-skeletons (e.g., because of new added native methods in > > NativeTest), the injected code will be automatically migrated. > > > > Another comment regarding the ominous #ifdef: XMLVM performs various > > optimizations on the generated C code. If a method is never overridden > > in an application, XMLVM will not put it in the vtable of the class. The > > #ifdef will be true iff the method in question was overridden. In this > > case the method needs to be called via the vtable (the funky looking > > function pointer). If the #ifdef is false, it means the method was never > > overridden in the application and can therefore be called directly. > > > > Note that the application does not terminate. That is because the > > garbage collection thread is not yet a daemon thread and therefore > > blocks termination of the application. This will be fixed. > > > > Hope this helps, > > Arno > > > > > ------------------------------------------------------------------------------ > > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > > The must-attend event for mobile developers. Connect with experts. > > Get tools for creating Super Apps. See the latest technologies. > > Sessions, hands-on labs, demos & much more. Register early & save! > > http://p.sf.net/sfu/rim-blackberry-1 > > _______________________________________________ > > Xmlvm-developers mailing list > > Xml...@li... > > <mailto:Xml...@li...> > > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers > > > > > > > > > > > ------------------------------------------------------------------------------ > > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > > The must-attend event for mobile developers. Connect with experts. > > Get tools for creating Super Apps. See the latest technologies. > > Sessions, hands-on labs, demos& much more. Register early& save! > > http://p.sf.net/sfu/rim-blackberry-1 > > > > > > > > _______________________________________________ > > Xmlvm-developers mailing list > > Xml...@li... > > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers > |
From: Paul P. <bay...@gm...> - 2011-08-04 05:52:41
|
Very cool! Way to go guys! This will be very helpful. Paul On Tue, Aug 2, 2011 at 7:31 PM, Arno Puder <ar...@pu...> wrote: > > Guys, > > it is my pleasure to announce the availability of a tutorial that > demonstrates the use of XMLVM: http://xmlvm.org/tutorial/ > > I want to thank the following people for helping to make this happen: > Andrew, Sascha, Spoorthi, Panayotis, and Wolfgang. > > There are still a few rough edges and we also plan to add a few more > demo apps, but I'm sure you'll find the current version already helpful > to get you started with XMLVM. Please post questions/comments/feedback > to the mailing list. > > Arno > > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers > |
From: Panayotis K. <pan...@pa...> - 2011-08-03 18:59:30
|
On 3 Αυγ 2011, at 6:33 μ.μ., Arno Puder wrote: > > looks good to me. Is there an alternative to what you have proposed? > > Arno Yes, now it uses internal classes, which are organized by type. We can instead use what we usually do, with flat final integers inside a dummy public final class. The reason I propose this instead is clarity, yp organize things together instead of having everything in a flat file. |
From: Markus N. <mar...@gm...> - 2011-08-03 16:17:10
|
Hi, I am one of the guys working on the WP7 project. At the moment this project is still handled in a separate branch and we are using the same demos as for the iphone cross compilation (xokoban, afireworks, ...). We also have a few very simple WP7 demos which don't use android but use the WP7 classes directly (e.g. the WP7 equivalent to ifireworks for iPhone). When the Android compatibility library was originally written everything was hardcoded for exclusive use with iOS and we are at the moment refactoring this whole library into two parts: platform specific parts for iOS and WP7 and a shared platform independent part. I would say we are 2-3 month away from reaching a point where this refactoring will be done and the demo applications xokoban and afireworks will run with the WP7 backend. At this point we want to merge back to the trunk. However even after those two demos run the WP7 backend will be by far not as complete as the iPhone side and many things will still be missing (multimedia stuff, some UI widgets, etc.) @Access to C# API: You should be able to use native methods on the WP7 backend as well and access underlying C# functionality in them. Alternatively you can expose C# functionality as wrapper classes as we did for e.g. Buttons, Checkboxes, ... I hope this helps. Send me a follow up in case some things aren't clear. Regards, Markus On Tue, Aug 2, 2011 at 9:17 PM, <sha...@ya...> wrote: > Hi Guys, > first let me thank you guys for the amazing work you did on this project. > Its really moving along at an amazing pace, well done! > > I've been looking into moving some of our code to the iPhone, we have quite > allot of native iPhone code which I would like to merge with the Java > porting layer we have in place. The plugin approach recommended in the past > seems to be deprecated (the objc backend was always a no-go for us due to > its limitations) but I'm somewhat stuck with implementing native interfaces, > I'm trying to do this by example but allot of things are unclear to me... > > 1. Where do I put the native code? Do I just stick a native_package_class.c > file and it would get picked by the build or should I do additional work? > > 2. I'm looking at the native methods and they have special comments within > them, is this used by your parsing or just for debugging purposes? What's > important to know about implementing these methods? > > 3. Is there a tool for generating native method stubs? So far the best I > could find was removing the native keyword and running through XML VM. > > 4. I used the method XMLVMUtil_convertFromByteArray but I'm not 100% clear > on what it does and where I should use it (besides for the purpose of > extracting a string). > How do I access Java objects such as arrays/Strings etc.? > How do I invoke a Java method from the native code? I can just type in the > bytecode like the converter does or for simplification I can just call the > function but would that be "correct"? > > 5. Are there plans to support JNI? It would be really nice since I have > quite a bit of JNI code which should be pretty portable. > > > On a completely unrelated matter, what is the status of the Windows Phone 7 > code? > I didn't see examples of that around here and I'd like to get a leg up on > that port as well, here I will probably also need access to the underlying > C# API if you have any tips. > > > Thanks Again. > Shai. > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers > > |
From: Arno P. <ar...@pu...> - 2011-08-03 16:07:55
|
I suggest you write yourself a little shell script based on the instructions I mentioned in my last message. Arno On 8/3/11 9:01 AM, Shai wrote: > Thanks Arno that explains allot. > How do I add this to the build process at least for now (until there is > a more official plugin architecture)? > Do I just place the file in the native directory and recompile xmlvm? > Do I need to list it somewhere in the build process? > > Thanks, > Shai. > > ------------------------------------------------------------------------ > *From:* Arno Puder <ar...@pu...> > *To:* "Xml...@li..." > <Xml...@li...> > *Sent:* Wednesday, August 3, 2011 6:30 PM > *Subject:* [xmlvm-dev] Native methods in the C backend > > > there was a question on the mailing list regarding the native interface > for the C backend. While XMLVM already makes extensive use of the native > interface when cross-compiling Apache Harmony, we have not exposed this > functionality in a proper way for applications. However, here a little > how-to showing how this can be done. 'Proper' support would just do a > better job at integrating the following steps into the XMLVM toolchain, > but the basic principles would remain the same. > > Consider the following class NativeTest. The idea is to provide an > implementation for nativeMethod() that prints out the array and then > calls back to a Java method: > > package xmlvm; > > public class NativeTest { > > native void nativeMethod(int[] intArray); > > void methodToBeCalledFromNative() { > System.out.println("Hello from methodToBeCalledFromNative()"); > } > > public static void main(String[] args) { > int intArray[] = {2, 4, 6, 8}; > NativeTest instance = new NativeTest(); > instance.nativeMethod(intArray); > } > } > > javac NativeTest.java > xmlvm --in=NativeTest.class --out=out --target=posix > mv out/src/xmlvm.m out/src/xmlvm.c > xmlvm --in=NativeTest.class --out=native \ > --target=gen-c-wrappers --gen-native-skeletons > # Ignore the error that the last command will generate. This command > # will generate a skeleton file for nativeMethod(). > # In file native/native_xmlvm_NativeTest.c out/src/ inject the following > code: > > //XMLVM_BEGIN_NATIVE[xmlvm_NativeTest_nativeMethod___int_1ARRAY] > xmlvm_NativeTest* thiz = me; > printf("Hello from nativeMethod()\n"); > org_xmlvm_runtime_XMLVMArray* intArray = n1; > JAVA_ARRAY_INT* data = (JAVA_ARRAY_INT*) > intArray->fields.org_xmlvm_runtime_XMLVMArray.array_; > int length = intArray->fields.org_xmlvm_runtime_XMLVMArray.length_; > for (int i = 0; i < length; i++) { > printf("%d, ", data[i]); > } > printf("\n"); > #ifdef XMLVM_VTABLE_IDX_xmlvm_NativeTest_methodToBeCalledFromNative__ > VTABLE_PTR func = > thiz->tib->vtable[XMLVM_VTABLE_IDX_xmlvm_NativeTest_methodToBeCalledFromNative__]; > (*(void (*)(JAVA_OBJECT)) func)(me); > #else > xmlvm_NativeTest_methodToBeCalledFromNative__(me); > #endif > //XMLVM_END_NATIVE > > cp native/native_xmlvm_NativeTest.c out/src/ > cd out/dist/ > make > ./build/out > > A few comments: the purpose of the special comment markers > //XMLVM_BEGIN_* and //XMLVM_END_NATIVE is to clearly distinguish between > generated portions of the file (outside the special markers) and > injected code (inside the markers). When the skeleton is regenerated via > --gen-native-skeletons (e.g., because of new added native methods in > NativeTest), the injected code will be automatically migrated. > > Another comment regarding the ominous #ifdef: XMLVM performs various > optimizations on the generated C code. If a method is never overridden > in an application, XMLVM will not put it in the vtable of the class. The > #ifdef will be true iff the method in question was overridden. In this > case the method needs to be called via the vtable (the funky looking > function pointer). If the #ifdef is false, it means the method was never > overridden in the application and can therefore be called directly. > > Note that the application does not terminate. That is because the > garbage collection thread is not yet a daemon thread and therefore > blocks termination of the application. This will be fixed. > > Hope this helps, > Arno > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > <mailto:Xml...@li...> > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers > > > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos& much more. Register early& save! > http://p.sf.net/sfu/rim-blackberry-1 > > > > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers |
From: Shai <sha...@ya...> - 2011-08-03 16:01:56
|
Thanks Arno that explains allot. How do I add this to the build process at least for now (until there is a more official plugin architecture)? Do I just place the file in the native directory and recompile xmlvm? Do I need to list it somewhere in the build process? Thanks, Shai. ________________________________ From: Arno Puder <ar...@pu...> To: "Xml...@li..." <Xml...@li...> Sent: Wednesday, August 3, 2011 6:30 PM Subject: [xmlvm-dev] Native methods in the C backend there was a question on the mailing list regarding the native interface for the C backend. While XMLVM already makes extensive use of the native interface when cross-compiling Apache Harmony, we have not exposed this functionality in a proper way for applications. However, here a little how-to showing how this can be done. 'Proper' support would just do a better job at integrating the following steps into the XMLVM toolchain, but the basic principles would remain the same. Consider the following class NativeTest. The idea is to provide an implementation for nativeMethod() that prints out the array and then calls back to a Java method: package xmlvm; public class NativeTest { native void nativeMethod(int[] intArray); void methodToBeCalledFromNative() { System.out.println("Hello from methodToBeCalledFromNative()"); } public static void main(String[] args) { int intArray[] = {2, 4, 6, 8}; NativeTest instance = new NativeTest(); instance.nativeMethod(intArray); } } javac NativeTest.java xmlvm --in=NativeTest.class --out=out --target=posix mv out/src/xmlvm.m out/src/xmlvm.c xmlvm --in=NativeTest.class --out=native \ --target=gen-c-wrappers --gen-native-skeletons # Ignore the error that the last command will generate. This command # will generate a skeleton file for nativeMethod(). # In file native/native_xmlvm_NativeTest.c out/src/ inject the following code: //XMLVM_BEGIN_NATIVE[xmlvm_NativeTest_nativeMethod___int_1ARRAY] xmlvm_NativeTest* thiz = me; printf("Hello from nativeMethod()\n"); org_xmlvm_runtime_XMLVMArray* intArray = n1; JAVA_ARRAY_INT* data = (JAVA_ARRAY_INT*) intArray->fields.org_xmlvm_runtime_XMLVMArray.array_; int length = intArray->fields.org_xmlvm_runtime_XMLVMArray.length_; for (int i = 0; i < length; i++) { printf("%d, ", data[i]); } printf("\n"); #ifdef XMLVM_VTABLE_IDX_xmlvm_NativeTest_methodToBeCalledFromNative__ VTABLE_PTR func = thiz->tib->vtable[XMLVM_VTABLE_IDX_xmlvm_NativeTest_methodToBeCalledFromNative__]; (*(void (*)(JAVA_OBJECT)) func)(me); #else xmlvm_NativeTest_methodToBeCalledFromNative__(me); #endif //XMLVM_END_NATIVE cp native/native_xmlvm_NativeTest.c out/src/ cd out/dist/ make ./build/out A few comments: the purpose of the special comment markers //XMLVM_BEGIN_* and //XMLVM_END_NATIVE is to clearly distinguish between generated portions of the file (outside the special markers) and injected code (inside the markers). When the skeleton is regenerated via --gen-native-skeletons (e.g., because of new added native methods in NativeTest), the injected code will be automatically migrated. Another comment regarding the ominous #ifdef: XMLVM performs various optimizations on the generated C code. If a method is never overridden in an application, XMLVM will not put it in the vtable of the class. The #ifdef will be true iff the method in question was overridden. In this case the method needs to be called via the vtable (the funky looking function pointer). If the #ifdef is false, it means the method was never overridden in the application and can therefore be called directly. Note that the application does not terminate. That is because the garbage collection thread is not yet a daemon thread and therefore blocks termination of the application. This will be fixed. Hope this helps, Arno ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ Xmlvm-developers mailing list Xml...@li... https://lists.sourceforge.net/lists/listinfo/xmlvm-developers |
From: Arno P. <ar...@pu...> - 2011-08-03 15:40:30
|
looks good to me. Is there an alternative to what you have proposed? Arno On 8/3/11 7:22 AM, Panayotis Katsaloulis wrote: > Hello all > I am thinking of adding the following code to the NSError object, and I'd like to hear your comments first: > The values are right. > > > public class NSError extends NSObject { > > ..... The usual stuff ..... > > > > public static class Domain { > > public static final String NSCocoa = "NSCocoaErrorDomain"; > public static final String NSURL = "NSURLErrorDomain"; > public static final String NSPOSIX = "NSPOSIXErrorDomain"; > public static final String NSOSStatus = "NSOSStatusErrorDomain"; > public static final String NSMach = "NSMachErrorDomain"; > } > > public static class Key { > > public static final String NSLocalizedDescription = "NSLocalizedDescription"; > public static final String NSFilePathError = "NSFilePath"; > public static final String NSStringEncodingError = "NSStringEncoding"; > public static final String NSUnderlyingError = "NSUnderlyingError"; > public static final String NSURLError = "NSURL"; > public static final String NSLocalizedFailureReason = "NSLocalizedFailureReason"; > public static final String NSLocalizedRecoverySuggestion = "NSLocalizedRecoverySuggestion"; > public static final String NSLocalizedRecoveryOptions = "NSLocalizedRecoveryOptions"; > public static final String NSRecoveryAttempter = "NSRecoveryAttempter"; > public static final String NSHelpAnchor = "NSHelpAnchor"; > public static final String NSURLErrorFailingURL = "NSErrorFailingURLKey"; > public static final String NSURLErrorFailingURLString = "NSErrorFailingURLStringKey"; > public static final String NSURLErrorFailingURLPeerTrust = "NSURLErrorFailingURLPeerTrustErrorKey"; > } > > public static class ErrorCode { > > public static class NSCocoa { > > public static final int NSFileNoSuchFileError = 4; > public static final int NSFileLockingError = 255; > public static final int NSFileReadUnknownError = 256; > public static final int NSFileReadNoPermissionError = 257; > public static final int NSFileReadInvalidFileNameError = 258; > public static final int NSFileReadCorruptFileError = 259; > public static final int NSFileReadNoSuchFileError = 260; > public static final int NSFileReadInapplicableStringEncodingError = 261; > public static final int NSFileReadUnsupportedSchemeError = 262; > public static final int NSFileReadTooLargeError = 263; > public static final int NSFileReadUnknownStringEncodingError = 264; > public static final int NSFileWriteUnknownError = 512; > public static final int NSFileWriteNoPermissionError = 513; > public static final int NSFileWriteInvalidFileNameError = 514; > public static final int NSFileWriteInapplicableStringEncodingError = 517; > public static final int NSFileWriteUnsupportedSchemeError = 518; > public static final int NSFileWriteOutOfSpaceError = 640; > public static final int NSFileWriteVolumeReadOnlyError = 642; > public static final int NSKeyValueValidationError = 1024; > public static final int NSFormattingError = 2048; > public static final int NSUserCancelledError = 3072; > public static final int NSFileErrorMinimum = 0; > public static final int NSFileErrorMaximum = 1023; > public static final int NSValidationErrorMinimum = 1024; > public static final int NSValidationErrorMaximum = 2047; > public static final int NSFormattingErrorMinimum = 2048; > public static final int NSFormattingErrorMaximum = 2559; > public static final int NSPropertyListReadCorruptError = 3840; > public static final int NSPropertyListReadUnknownVersionError = 3841; > public static final int NSPropertyListReadStreamError = 3842; > public static final int NSPropertyListWriteStreamError = 3851; > public static final int NSPropertyListErrorMinimum = 3840; > public static final int NSPropertyListErrorMaximum = 4095; > public static final int NSExecutableErrorMinimum = 3584; > public static final int NSExecutableNotLoadableError = 3584; > public static final int NSExecutableArchitectureMismatchError = 3585; > public static final int NSExecutableRuntimeMismatchError = 3586; > public static final int NSExecutableLoadError = 3587; > public static final int NSExecutableLinkError = 3588; > public static final int NSExecutableErrorMaximum = 3839; > } > > public static class NSURL { > > public static final int Unknown = -1; > public static final int Cancelled = -999; > public static final int BadURL = -1000; > public static final int TimedOut = -1001; > public static final int UnsupportedURL = -1002; > public static final int CannotFindHost = -1003; > public static final int CannotConnectToHost = -1004; > public static final int DataLengthExceedsMaximum = -1103; > public static final int NetworkConnectionLost = -1005; > public static final int DNSLookupFailed = -1006; > public static final int HTTPTooManyRedirects = -1007; > public static final int ResourceUnavailable = -1008; > public static final int NotConnectedToInternet = -1009; > public static final int RedirectToNonExistentLocation = -1010; > public static final int BadServerResponse = -1011; > public static final int UserCancelledAuthentication = -1012; > public static final int UserAuthenticationRequired = -1013; > public static final int ZeroByteResource = -1014; > public static final int CannotDecodeRawData = -1015; > public static final int CannotDecodeContentData = -1016; > public static final int CannotParseResponse = -1017; > public static final int InternationalRoamingOff = -1018; > public static final int CallIsActive = -1019; > public static final int DataNotAllowed = -1020; > public static final int RequestBodyStreamExhausted = -1021; > public static final int FileDoesNotExist = -1100; > public static final int FileIsDirectory = -1101; > public static final int NoPermissionsToReadFile = -1102; > public static final int SecureConnectionFailed = -1200; > public static final int ServerCertificateHasBadDate = -1201; > public static final int ServerCertificateUntrusted = -1202; > public static final int ServerCertificateHasUnknownRoot = -1203; > public static final int ServerCertificateNotYetValid = -1204; > public static final int ClientCertificateRejected = -1205; > public static final int ClientCertificateRequired = -1206; > public static final int CannotLoadFromNetwork = -2000; > public static final int CannotCreateFile = -3000; > public static final int CannotOpenFile = -3001; > public static final int CannotCloseFile = -3002; > public static final int CannotWriteToFile = -3003; > public static final int CannotRemoveFile = -3004; > public static final int CannotMoveFile = -3005; > public static final int DownloadDecodingFailedMidStream = -3006; > public static final int DownloadDecodingFailedToComplete = -3007; > } > } > } > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos& much more. Register early& save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers |
From: Arno P. <ar...@pu...> - 2011-08-03 15:30:15
|
there was a question on the mailing list regarding the native interface for the C backend. While XMLVM already makes extensive use of the native interface when cross-compiling Apache Harmony, we have not exposed this functionality in a proper way for applications. However, here a little how-to showing how this can be done. 'Proper' support would just do a better job at integrating the following steps into the XMLVM toolchain, but the basic principles would remain the same. Consider the following class NativeTest. The idea is to provide an implementation for nativeMethod() that prints out the array and then calls back to a Java method: package xmlvm; public class NativeTest { native void nativeMethod(int[] intArray); void methodToBeCalledFromNative() { System.out.println("Hello from methodToBeCalledFromNative()"); } public static void main(String[] args) { int intArray[] = {2, 4, 6, 8}; NativeTest instance = new NativeTest(); instance.nativeMethod(intArray); } } javac NativeTest.java xmlvm --in=NativeTest.class --out=out --target=posix mv out/src/xmlvm.m out/src/xmlvm.c xmlvm --in=NativeTest.class --out=native \ --target=gen-c-wrappers --gen-native-skeletons # Ignore the error that the last command will generate. This command # will generate a skeleton file for nativeMethod(). # In file native/native_xmlvm_NativeTest.c out/src/ inject the following code: //XMLVM_BEGIN_NATIVE[xmlvm_NativeTest_nativeMethod___int_1ARRAY] xmlvm_NativeTest* thiz = me; printf("Hello from nativeMethod()\n"); org_xmlvm_runtime_XMLVMArray* intArray = n1; JAVA_ARRAY_INT* data = (JAVA_ARRAY_INT*) intArray->fields.org_xmlvm_runtime_XMLVMArray.array_; int length = intArray->fields.org_xmlvm_runtime_XMLVMArray.length_; for (int i = 0; i < length; i++) { printf("%d, ", data[i]); } printf("\n"); #ifdef XMLVM_VTABLE_IDX_xmlvm_NativeTest_methodToBeCalledFromNative__ VTABLE_PTR func = thiz->tib->vtable[XMLVM_VTABLE_IDX_xmlvm_NativeTest_methodToBeCalledFromNative__]; (*(void (*)(JAVA_OBJECT)) func)(me); #else xmlvm_NativeTest_methodToBeCalledFromNative__(me); #endif //XMLVM_END_NATIVE cp native/native_xmlvm_NativeTest.c out/src/ cd out/dist/ make ./build/out A few comments: the purpose of the special comment markers //XMLVM_BEGIN_* and //XMLVM_END_NATIVE is to clearly distinguish between generated portions of the file (outside the special markers) and injected code (inside the markers). When the skeleton is regenerated via --gen-native-skeletons (e.g., because of new added native methods in NativeTest), the injected code will be automatically migrated. Another comment regarding the ominous #ifdef: XMLVM performs various optimizations on the generated C code. If a method is never overridden in an application, XMLVM will not put it in the vtable of the class. The #ifdef will be true iff the method in question was overridden. In this case the method needs to be called via the vtable (the funky looking function pointer). If the #ifdef is false, it means the method was never overridden in the application and can therefore be called directly. Note that the application does not terminate. That is because the garbage collection thread is not yet a daemon thread and therefore blocks termination of the application. This will be fixed. Hope this helps, Arno |
From: Panayotis K. <pan...@pa...> - 2011-08-03 14:22:31
|
Hello all I am thinking of adding the following code to the NSError object, and I'd like to hear your comments first: The values are right. public class NSError extends NSObject { ..... The usual stuff ..... public static class Domain { public static final String NSCocoa = "NSCocoaErrorDomain"; public static final String NSURL = "NSURLErrorDomain"; public static final String NSPOSIX = "NSPOSIXErrorDomain"; public static final String NSOSStatus = "NSOSStatusErrorDomain"; public static final String NSMach = "NSMachErrorDomain"; } public static class Key { public static final String NSLocalizedDescription = "NSLocalizedDescription"; public static final String NSFilePathError = "NSFilePath"; public static final String NSStringEncodingError = "NSStringEncoding"; public static final String NSUnderlyingError = "NSUnderlyingError"; public static final String NSURLError = "NSURL"; public static final String NSLocalizedFailureReason = "NSLocalizedFailureReason"; public static final String NSLocalizedRecoverySuggestion = "NSLocalizedRecoverySuggestion"; public static final String NSLocalizedRecoveryOptions = "NSLocalizedRecoveryOptions"; public static final String NSRecoveryAttempter = "NSRecoveryAttempter"; public static final String NSHelpAnchor = "NSHelpAnchor"; public static final String NSURLErrorFailingURL = "NSErrorFailingURLKey"; public static final String NSURLErrorFailingURLString = "NSErrorFailingURLStringKey"; public static final String NSURLErrorFailingURLPeerTrust = "NSURLErrorFailingURLPeerTrustErrorKey"; } public static class ErrorCode { public static class NSCocoa { public static final int NSFileNoSuchFileError = 4; public static final int NSFileLockingError = 255; public static final int NSFileReadUnknownError = 256; public static final int NSFileReadNoPermissionError = 257; public static final int NSFileReadInvalidFileNameError = 258; public static final int NSFileReadCorruptFileError = 259; public static final int NSFileReadNoSuchFileError = 260; public static final int NSFileReadInapplicableStringEncodingError = 261; public static final int NSFileReadUnsupportedSchemeError = 262; public static final int NSFileReadTooLargeError = 263; public static final int NSFileReadUnknownStringEncodingError = 264; public static final int NSFileWriteUnknownError = 512; public static final int NSFileWriteNoPermissionError = 513; public static final int NSFileWriteInvalidFileNameError = 514; public static final int NSFileWriteInapplicableStringEncodingError = 517; public static final int NSFileWriteUnsupportedSchemeError = 518; public static final int NSFileWriteOutOfSpaceError = 640; public static final int NSFileWriteVolumeReadOnlyError = 642; public static final int NSKeyValueValidationError = 1024; public static final int NSFormattingError = 2048; public static final int NSUserCancelledError = 3072; public static final int NSFileErrorMinimum = 0; public static final int NSFileErrorMaximum = 1023; public static final int NSValidationErrorMinimum = 1024; public static final int NSValidationErrorMaximum = 2047; public static final int NSFormattingErrorMinimum = 2048; public static final int NSFormattingErrorMaximum = 2559; public static final int NSPropertyListReadCorruptError = 3840; public static final int NSPropertyListReadUnknownVersionError = 3841; public static final int NSPropertyListReadStreamError = 3842; public static final int NSPropertyListWriteStreamError = 3851; public static final int NSPropertyListErrorMinimum = 3840; public static final int NSPropertyListErrorMaximum = 4095; public static final int NSExecutableErrorMinimum = 3584; public static final int NSExecutableNotLoadableError = 3584; public static final int NSExecutableArchitectureMismatchError = 3585; public static final int NSExecutableRuntimeMismatchError = 3586; public static final int NSExecutableLoadError = 3587; public static final int NSExecutableLinkError = 3588; public static final int NSExecutableErrorMaximum = 3839; } public static class NSURL { public static final int Unknown = -1; public static final int Cancelled = -999; public static final int BadURL = -1000; public static final int TimedOut = -1001; public static final int UnsupportedURL = -1002; public static final int CannotFindHost = -1003; public static final int CannotConnectToHost = -1004; public static final int DataLengthExceedsMaximum = -1103; public static final int NetworkConnectionLost = -1005; public static final int DNSLookupFailed = -1006; public static final int HTTPTooManyRedirects = -1007; public static final int ResourceUnavailable = -1008; public static final int NotConnectedToInternet = -1009; public static final int RedirectToNonExistentLocation = -1010; public static final int BadServerResponse = -1011; public static final int UserCancelledAuthentication = -1012; public static final int UserAuthenticationRequired = -1013; public static final int ZeroByteResource = -1014; public static final int CannotDecodeRawData = -1015; public static final int CannotDecodeContentData = -1016; public static final int CannotParseResponse = -1017; public static final int InternationalRoamingOff = -1018; public static final int CallIsActive = -1019; public static final int DataNotAllowed = -1020; public static final int RequestBodyStreamExhausted = -1021; public static final int FileDoesNotExist = -1100; public static final int FileIsDirectory = -1101; public static final int NoPermissionsToReadFile = -1102; public static final int SecureConnectionFailed = -1200; public static final int ServerCertificateHasBadDate = -1201; public static final int ServerCertificateUntrusted = -1202; public static final int ServerCertificateHasUnknownRoot = -1203; public static final int ServerCertificateNotYetValid = -1204; public static final int ClientCertificateRejected = -1205; public static final int ClientCertificateRequired = -1206; public static final int CannotLoadFromNetwork = -2000; public static final int CannotCreateFile = -3000; public static final int CannotOpenFile = -3001; public static final int CannotCloseFile = -3002; public static final int CannotWriteToFile = -3003; public static final int CannotRemoveFile = -3004; public static final int CannotMoveFile = -3005; public static final int DownloadDecodingFailedMidStream = -3006; public static final int DownloadDecodingFailedToComplete = -3007; } } } |
From: <sha...@ya...> - 2011-08-03 04:17:57
|
Hi Guys, first let me thank you guys for the amazing work you did on this project. Its really moving along at an amazing pace, well done! I've been looking into moving some of our code to the iPhone, we have quite allot of native iPhone code which I would like to merge with the Java porting layer we have in place. The plugin approach recommended in the past seems to be deprecated (the objc backend was always a no-go for us due to its limitations) but I'm somewhat stuck with implementing native interfaces, I'm trying to do this by example but allot of things are unclear to me... 1. Where do I put the native code? Do I just stick a native_package_class.c file and it would get picked by the build or should I do additional work? 2. I'm looking at the native methods and they have special comments within them, is this used by your parsing or just for debugging purposes? What's important to know about implementing these methods? 3. Is there a tool for generating native method stubs? So far the best I could find was removing the native keyword and running through XML VM. 4. I used the method XMLVMUtil_convertFromByteArray but I'm not 100% clear on what it does and where I should use it (besides for the purpose of extracting a string). How do I access Java objects such as arrays/Strings etc.? How do I invoke a Java method from the native code? I can just type in the bytecode like the converter does or for simplification I can just call the function but would that be "correct"? 5. Are there plans to support JNI? It would be really nice since I have quite a bit of JNI code which should be pretty portable. On a completely unrelated matter, what is the status of the Windows Phone 7 code? I didn't see examples of that around here and I'd like to get a leg up on that port as well, here I will probably also need access to the underlying C# API if you have any tips. Thanks Again. Shai. |
From: Arno P. <ar...@pu...> - 2011-08-03 00:31:40
|
Guys, it is my pleasure to announce the availability of a tutorial that demonstrates the use of XMLVM: http://xmlvm.org/tutorial/ I want to thank the following people for helping to make this happen: Andrew, Sascha, Spoorthi, Panayotis, and Wolfgang. There are still a few rough edges and we also plan to add a few more demo apps, but I'm sure you'll find the current version already helpful to get you started with XMLVM. Please post questions/comments/feedback to the mailing list. Arno |
From: Panayotis K. <pan...@pa...> - 2011-07-14 12:50:02
|
When I compile xmlvm from another directory, the build script fails to compile the android compatibility library. It seems that the "java" command under cc-android-compat-lib.impl makes some assumptions that the directory this executable is called, is the same as the root XMLVM directory. Here is what I get (with some steps back to help you trace the problem) build-android-compat-lib: [mkdir] Created dir: /Users/teras/Works/Development/Mobile/SDK/CrossMobile/xmlvm/build/compat-lib/android/java [javac] /Users/teras/Works/Development/Mobile/SDK/CrossMobile/xmlvm/build.xml:91: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 231 source files to /Users/teras/Works/Development/Mobile/SDK/CrossMobile/xmlvm/build/compat-lib/android/java [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [jar] Building jar: /Users/teras/Works/Development/Mobile/SDK/CrossMobile/xmlvm/dist/lib/android-compat.jar cc-android-compat-lib: cc-android-compat-lib.impl: [echo] Building android compatibility lib [mkdir] Created dir: /Users/teras/Works/Development/Mobile/SDK/CrossMobile/xmlvm/build/compat-lib/android/objc [java] [07/14/11 15:47:18.065] DEBUG: Forcing --enable-ref-counting for target OBJC [java] [07/14/11 15:47:18.081] ERROR: InputProcessFactory: Could not find input resource: build/compat-lib/android/java/ [java] [07/14/11 15:47:18.087] ERROR: XmlvmProcessor: No inputs to process. [java] [07/14/11 15:47:18.087] ERROR: Something went wrong during processing. xmlvmjar: ... ... |
From: Sascha H. <sa...@gm...> - 2011-07-09 23:16:19
|
Agreed. On Jul 10, 2011 1:09 AM, "Panayotis Katsaloulis" <pan...@pa...> wrote: >> >> >> BUILD FAILED >> C:\dev\XMLVM\xmlvm\build.xml:336: The following error occurred while executing this line: >> C:\dev\XMLVM\xmlvm\demo\build.xml:46: The following error occurred while executing this line: >> C:\dev\XMLVM\xmlvm\demo\iphone\ifireworks\nbproject\xmlvm.xml:100: The following error occurred while executing this line: >> C:\dev\XMLVM\xmlvm\demo\iphone\ifireworks\nbproject\build-xcode.xml:52: java.io.IOException: > > > Probably we should put a big fat warning, that the demos can only be compiled under Mac OS X? |
From: Panayotis K. <pan...@pa...> - 2011-07-09 23:09:27
|
> > > BUILD FAILED > C:\dev\XMLVM\xmlvm\build.xml:336: The following error occurred while executing this line: > C:\dev\XMLVM\xmlvm\demo\build.xml:46: The following error occurred while executing this line: > C:\dev\XMLVM\xmlvm\demo\iphone\ifireworks\nbproject\xmlvm.xml:100: The following error occurred while executing this line: > C:\dev\XMLVM\xmlvm\demo\iphone\ifireworks\nbproject\build-xcode.xml:52: java.io.IOException: Probably we should put a big fat warning, that the demos can only be compiled under Mac OS X? |
From: Arno P. <ar...@pu...> - 2011-07-07 15:02:38
|
that would be a viable solution for the ObjC backend. Arno On 7/7/11 4:29 PM, Panayotis Katsaloulis wrote: > What do you think about the solution for this specific problem? > > Use the following code for the selector applicationDidFinishLaunching of > UIApplicationDelegate > > > - (void) applicationDidFinishLaunching: (UIApplication*) app > { > SELselector = > NSSelectorFromString([NSStringstringWithFormat:@"__init_%s__", > class_getName([selfclass])]); > [self performSelector:selector]; > > > [selfapplicationDidFinishLaunching___org_xmlvm_iphone_UIApplication: app]; > } > > As a side note, probably we should do the same for the UIApplication > object as well (if it is an instance of org_xmlvm_iphone_UIApplication) > > > > > On 11 Νοε 2010, at 6:56 μ.μ., Arno Puder wrote: > >> >> that is a known issue. The code that XMLVM generates is correct. The >> problem is that certain classes (such as UIAppication*) are instantiated >> by Cocoa and Cocoa doesn't know about the __init__*() constructors that >> were generated by XMLVM. The initialization of 'test' in your example >> will end up in the default constructor for class Main and since Cocoa >> doesn't call it, it won't get initialized. >> >> This will work perfectly fine for any other class (that is handled by >> XMLVM). It is just this special case when Cocoa instantiates a Java >> object. Back then I couldn't think of a solution for this. I'll revisit >> this with the C backend. Here we might have more hooks to solve this >> problem. >> >> Arno >> >> >> On 11/11/10 7:08 AM, Panayotis Katsaloulis wrote: >>> there is something missing when variables are initialized outsize the >>> constructor. >>> >>> As a minium program to display this error, have a look at this: >>> instead of printing "hello", it prints "null", since this is not >>> initialized. >>> >>> >>> >>> >>> package my.testmem; >>> >>> import org.xmlvm.iphone.UIApplication; >>> import org.xmlvm.iphone.UIApplicationDelegate; >>> >>> public class Main extends UIApplicationDelegate { >>> >>> String test = "hello"; >>> >>> @Override >>> public void applicationDidFinishLaunching(UIApplication app) { >>> System.out.println(test); >>> } >>> >>> public static void main(String[] args) { >>> UIApplication.main(args, null, Main.class); >>> } >>> } > > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > > > > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers |
From: Panayotis K. <pan...@pa...> - 2011-07-07 14:30:08
|
What do you think about the solution for this specific problem? Use the following code for the selector applicationDidFinishLaunching of UIApplicationDelegate - (void) applicationDidFinishLaunching: (UIApplication*) app { SEL selector = NSSelectorFromString([NSString stringWithFormat:@"__init_%s__", class_getName([self class])]); [self performSelector:selector]; [self applicationDidFinishLaunching___org_xmlvm_iphone_UIApplication: app]; } As a side note, probably we should do the same for the UIApplication object as well (if it is an instance of org_xmlvm_iphone_UIApplication) On 11 Νοε 2010, at 6:56 μ.μ., Arno Puder wrote: > > that is a known issue. The code that XMLVM generates is correct. The > problem is that certain classes (such as UIAppication*) are instantiated > by Cocoa and Cocoa doesn't know about the __init__*() constructors that > were generated by XMLVM. The initialization of 'test' in your example > will end up in the default constructor for class Main and since Cocoa > doesn't call it, it won't get initialized. > > This will work perfectly fine for any other class (that is handled by > XMLVM). It is just this special case when Cocoa instantiates a Java > object. Back then I couldn't think of a solution for this. I'll revisit > this with the C backend. Here we might have more hooks to solve this > problem. > > Arno > > > On 11/11/10 7:08 AM, Panayotis Katsaloulis wrote: >> there is something missing when variables are initialized outsize the constructor. >> >> As a minium program to display this error, have a look at this: instead of printing "hello", it prints "null", since this is not initialized. >> >> >> >> >> package my.testmem; >> >> import org.xmlvm.iphone.UIApplication; >> import org.xmlvm.iphone.UIApplicationDelegate; >> >> public class Main extends UIApplicationDelegate { >> >> String test = "hello"; >> >> @Override >> public void applicationDidFinishLaunching(UIApplication app) { >> System.out.println(test); >> } >> >> public static void main(String[] args) { >> UIApplication.main(args, null, Main.class); >> } >> } |
From: Panayotis K. <pan...@pa...> - 2011-07-02 08:44:48
|
On Jul 2, 2011, at 8:02 AM, Kit wrote: > I was able to download your stuff following the instructions in the manual.pdf file on your site I was always wondering, why first time users keep on using the "hard" way and not the user friendly scripts. Now I know :) It is the PDF instructions these people are following. I'd suggest to update the PDF from the HTML page (even if it is not pretty), or at minimum remove this obsolete file. What do you think? |
From: Panayotis K. <pan...@pa...> - 2011-06-28 17:24:31
|
On Jun 28, 2011, at 6:14 PM, Markus Neubrand wrote: > Hi, > > If you want to I can commit the changes with your name in the log from my Linux box. > > Markus Thank you, this is what I just did. I installed xmlvm in a linux box, applied the patch there and committed the changes. Hopefully there are no issues any more. |
From: Markus N. <mar...@gm...> - 2011-06-28 15:14:19
|
Hi, If you want to I can commit the changes with your name in the log from my Linux box. Markus On Sun, Jun 26, 2011 at 6:08 AM, Panayotis Katsaloulis < pan...@pa...> wrote: > > On Jun 23, 2011, at 7:13 AM, Markus Neubrand wrote: > > > Hi, > > > > Didn't get around to test it yesterday. Sorry. Creation of template > project as well as compiling and running the demos works for me again. > > > > I think you can commit it to the trunk. > > I am not sure that the commit would be successful, since I am in a case > insensitive filesystem, and I don't want to break the current xmlvm trunk. > Any idea how I can be safe with this? > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers > |
From: Arno P. <ar...@pu...> - 2011-06-28 10:29:34
|
that shouldn't be a problem because it should be a red-class. As long as the execution paths through Constructor do not come across where this red class is used, nothing bad will happen. The notion of red classes is used with the C backend to prune dependencies. Arno On 6/28/11 12:23 PM, Panayotis Katsaloulis wrote: > Hello all! > > I've seen that in some locations the xmlvm uses some "internal" packages, like > sun.reflect.generics.repository.ConstructorRepository > in file > xmlvm2c/lib/proxies/java/lang/reflect/Constructor.java > > I found that when I tried to compile xmlvm in a new setup in a Linux box. > > Probably it is a good idea to get rid of these references? > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers |
From: Panayotis K. <pan...@pa...> - 2011-06-28 10:24:00
|
Hello all! I've seen that in some locations the xmlvm uses some "internal" packages, like sun.reflect.generics.repository.ConstructorRepository in file xmlvm2c/lib/proxies/java/lang/reflect/Constructor.java I found that when I tried to compile xmlvm in a new setup in a Linux box. Probably it is a good idea to get rid of these references? |
From: Panayotis K. <pan...@pa...> - 2011-06-26 13:08:46
|
On Jun 23, 2011, at 7:13 AM, Markus Neubrand wrote: > Hi, > > Didn't get around to test it yesterday. Sorry. Creation of template project as well as compiling and running the demos works for me again. > > I think you can commit it to the trunk. I am not sure that the commit would be successful, since I am in a case insensitive filesystem, and I don't want to break the current xmlvm trunk. Any idea how I can be safe with this? |
From: Panayotis K. <pan...@pa...> - 2011-06-20 09:15:25
|
On 18 Ιουν 2011, at 4:09 π.μ., Markus Neubrand wrote: > Hi, > > Since the recent update I can't build the android demos anymore on my Linux machine. Depending on the config used ant tries to include this build files: build-Android.xml, build-Java.xml or build-Xcode.xml. > The actual file names though are build-android.xml, build-java.xml and build-xcode.xml. Because of this upper-/lowercase issue the build fails. > > @Panayotis: Afair you did the changes to the build files a few commits ago. Can you please verify that you didn't break the build for everyone who uses a casesensitive file system. > > Thanks, > Markus Please have a look at patch http://xmlvm-reviews.appspot.com/129002 I can't properly3 test it since I am on a regular (case insensitive) HFS+ Please, also test the creation of a template project! |
From: Panayotis K. <pan...@pa...> - 2011-06-18 07:18:42
|
On Jun 18, 2011, at 4:09 AM, Markus Neubrand wrote: > Hi, > > Since the recent update I can't build the android demos anymore on my Linux machine. Depending on the config used ant tries to include this build files: build-Android.xml, build-Java.xml or build-Xcode.xml. > The actual file names though are build-android.xml, build-java.xml and build-xcode.xml. Because of this upper-/lowercase issue the build fails. > > @Panayotis: Afair you did the changes to the build files a few commits ago. Can you please verify that you didn't break the build for everyone who uses a casesensitive file system. Indeed the build should break in a case sensitive filesystem (which OSX has not). The solution of course is to rename the files to upper case. Right now I am away from my computer and I can not create a patch though :( |
From: Markus N. <mar...@gm...> - 2011-06-18 01:09:47
|
Hi, Since the recent update I can't build the android demos anymore on my Linux machine. Depending on the config used ant tries to include this build files: build-Android.xml, build-Java.xml or build-Xcode.xml. The actual file names though are build-*a*ndroid.xml, build-*j*ava.xml and build-*x*code.xml. Because of this upper-/lowercase issue the build fails. @Panayotis: Afair you did the changes to the build files a few commits ago. Can you please verify that you didn't break the build for everyone who uses a casesensitive file system. Thanks, Markus |