instead of trying to 'glue' things together manually on the C side, I
would suggest you create a .jar file with your business logic and then
reference it via --in wherever you need it.
I'm not sure what you mean with "Android library which has the business
logic". If that business logic is dependent on Android API, it becomes
effectively an Android project. In XMLVM, the entry point is
AndroidAppLauncher that does Android specific initializations and then
launches the main activity.
Long in short: make sure that your business logic is not dependent on
Android API. In the future it might make sense to allow a top-level
iPhone window in a cross-compiled Android application to write a native
iOS application, but we don't support that yet.
Arno
On 5/6/11 3:55 AM, Marko Žmak wrote:
> This is the scenario I would like to have:
>
> - have an Android library project which has all the business logic
> for an app
> - have a separate Android project for the gui and whole app
> - cross compile the Android library project to xcode library project
> - have an xcode project for iPhone gui and whole app, which uses
> the crosscompiled xcode library
>
> Is it possible?
> What are the possible problems with this approach?
> Have anyone tried it?
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today. Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
|
