Re: [xmlvm-dev] Android tutorials/demo compilation problem under Xcode target from the command line

[Arno P. <ar...@pu...>]

On 6/24/12 4:31 AM, Panayotis Katsaloulis wrote:
> Dear all,
>
> I think there is a problem with some android tutorials/demos.
> I spotted two of such problems when updating the build scripts to support unicode property files.
> The problems were also in the 2290 version of the repository, before committing any changes.
>
> -- 1 --
>
> The project tutorial/android/widget fails to compile under target Xcode, while others like tutorial/android/helloworld/prog compiles (and runs) just fine.

Some time ago we began to add tutorials for both iOS and Android. For 
the Android tutorials we didn't want to constrain ourselves with 
limitations in XMLVM. For that reason several Android tutorials cannot 
be cross-compiled to iOS at the moment. Look at 
xmlvm/tutorial/doc/overview.xml and check tag <xmlvm-status> to see if 
an Android tutorial app can be cross-compiled or not.

>
> -- 2 --
>
>
> Another case is also for the project demo/android/afireworks
> Here the procedure fails with this error (which has nothing to do with the previous error):
>
> -xproject-create:
>       [echo] Creating Xcode project with the Objective C backend.
>       [java] [06/24/12 05:21:37.271]    ERROR: InputProcessFactory: Could not find input resource: /Users/teras/Works/Development/Mobile/SDK/CrossMobile/xmlvm.new/demo/android/afireworks/bin-android2iphone
>       [java] [06/24/12 05:21:37.272]    ERROR: XmlvmProcessor: No inputs to process.
>       [java] [06/24/12 05:21:37.272]    ERROR: Sub-Process for processing android iphone compat lib has failed.
>       [java] [06/24/12 05:21:37.272]    ERROR: Processing Phase 2 not successful. See error messages above for details.
>       [java] [06/24/12 05:21:37.272]    ERROR: Something went wrong during processing.
>
> Here it seems that the pipeline has changed somehow.

You may have noticed that the ACL (Android Compat Lib) has been 
refactored to differentiate between device-independent parts 
(xmlvm/src/acl/android) and device-dependent implementations 
(xmlvm/src/acl/ios and xmlvm/src/acl/wp7). We updated build.xml but I 
guess we didn't do this for the templates. Another note: I'm not sure if 
aFireworks still works with the Objective-C backend.

Arno