From: Panayotis K. <pan...@pa...> - 2010-09-23 08:17:37
|
On 23 Σεπ 2010, at 4:22 π.μ., Arno Puder wrote: > > you will have to explain that a little more in detail. The demos that > are shipped with XMLVM are proper Android projects. They were created > with the Android plugin for Eclipse (which is officially released by > Google). In Eclipse, you can import xmlvm/demo/android/xokoban and you > will see a proper Android project in your workspace. The location of the > Android SDK is configured with the Eclipse plugin. > > XMLVM needs to compile .class files (not .dex files) to do its thing. > So, the build.xml for that can be independent of the Android SDK. > > What exactly is the problem? > > Arno Exactly that is the problem, it is only usable under Eclipse and not on the command line. The problem with the command line is that the Android SDK should be defined somewhere. If we want to use the exact build options as with Android projects (as discussed in a previous email with android libraries), the Android SDK should be present. I have thought of this problem and I think I found an alternative approach. The first time the user requests the Android based demos to be compiled - and the location of the Android SDK was not provided to the XMLVM system - an error will appear and the compilation will abort. When the user will define the location, the compilation could go on as usual. Again, this has to do with the demo XMLVM Android projects. This will not alter in any case the regular xmlvm usage from the command line. |