Re: [xmlvm-users] XMLVM android-compat.jar vs. android.target.classpath

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

+1 from my side as well.

Arno


On 9/19/10 9:01 AM, Wolfgang Korn wrote:
> I go for the third option - because it is the safest one.
>
> -- Wolfgang
>
> Am 19.09.2010 17:56 schrieb "Panayotis Katsaloulis"
> <pan...@pa... <mailto:pan...@pa...>>:
>  > Hello all!
>  >
>  > I am in the process of automating the integration of XMLVM into an
> Android project.
>  > But I found a problem and I would like to discuss with you the
> possible solutions.
>  >
>  > The problem is with the android libraries, which come from two
> sources: one from the XMLVM project (which will emulate Android on an
> iPhone) and second, the actual bootstrap libraries of a genuine Android
> device.
>  > Although they are more or less the same, they are not "exactly" the same.
>  >
>  > The source code of a project could be compiled perfectly with both
> libraries. The produced class files though will (probably) be a bit
> different. This can be demonstrated even in the case of the "aFireworks"
> project.
>  > So, in order to work perfectly with both environments, I can see
> these scenarios and I'd like you to say your opinion, on what to implement:
>  >
>  > a) Use only android bootstrap libraries. That means that the xmlvm
> android library should be API-perfect, or else compilation on the ObjC
> part will fail.
>  >
>  > b) Compile with XMLVM libraries and use these classes for both ObjC
> project *and* Android emulation. As long as the XMLVM library is more or
> less compatible with the official android bootstrap, this will work.
> But, in the case that something is binary incompatible, the application
> on the Android device will crash for no obvious reason.
>  >
>  > c) Compile the ObjC code with the xmlvm libraries, and the Android
> emulator project with the Android bootstrap files. So every time the
> project is rebuilt, the produced classes should be cleaned and re-generated.
>  >
>  >
>  > I am more in favor of the third approach, although it is not the most
> optimized, but because it is the safest. There will be a penalty for
> compilation, but I think it is not so important, compared with the benefits.
>  >
>  >
>  > Before implementing anything though, I'd love to hear your thoughts...
>  >
> ------------------------------------------------------------------------------
>  > Start uncovering the many advantages of virtual appliances
>  > and start using them to simplify application deployment and
>  > accelerate your shift to cloud computing.
>  > http://p.sf.net/sfu/novell-sfdev2dev
>  > _______________________________________________
>  > xmlvm-users mailing list
>  > xml...@li...
> <mailto:xml...@li...>
>  > https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
>
>
>
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users