From: <Zor...@gm...> - 2010-03-25 17:22:24
|
Hello there! I am an Android Developer who was just about to dig into Objective-C and iPhone development because the need arose to also target iPhones as well as Android phones. Because of that I was extremely excited when I found Xmlvm just a few days ago! But, unfortunately, even though I tried to stick exactly to what the short documentation says about the demo projects, I got stuck pretty quickly. Maybe I am not alone with this and maybe there's only a tiny little thing I missed that screws everthing up right now. Here's what I wanted to do: Take one of my Android Apps and simply port it right away. Okay, nice attempt - I got stuck with about a hundred error messages in the Xcode envirnment. So, I stepped back one step: try to get SayHello working out of the box... As there's no description of what is needed to try out the demos I'll give you my environment specs quickly: Macbook Pro with Xcode 3.2.1 and Eclipse 3.5 running the latest Android SDK r05. The rest is out of the box. Xmlvm compiled fine using the ant script. Now, my first question: I understood that using Xmlvm for Android apps, it will take the Dalvik Code - but the command line interface for xmlvm only gets the SayHello's project folder (that's what I understood I'd have to do) So I call: xmlvm --in=../workspace/xmlvm/demo/android/sayhello/ --target=android-on-iphone --app-name="SayHello" With this command I get a lot of Warnings of the type: WARNING: Unable to create InputProcesses for input: [...] both for helper files like *.svn AND my *.java source files. Where should xmlvm get the Dalvik machine code from? Isn't that only within the apk file? I got no clue... Now: my first attempt was to get it working in the iPhone Simulator as that should be done by calling make and using the generated makefile. The simulator starts and there's the SayHello app - but it crashes right away. When I start it, it closes immediately. Second attempt: get into Xcode (which I really don't know yet...). I created a project, deleted main and xib File plus app delegates and the entry in the pList file. Next question arose when trying to add files to the project: I don't have a MakeVars file (but I should not include it - where is it?) An Info.pList file is missing, too... Okay, added all the files and pressed Build&Run... This gives me 39 linker errors which I add at the end of this post. Now - what could be wrong here? Maybe I am not the only one who has a problem getting the first program to run? Maybe it is possible to add a little bit more to the documentation so that these first steps don't get so hard to do? That would be great; as the whole idea behind xmlvm is just great and perfect! I would really LOVE not to end up learning the "latin language" or moving to the Vatikan... :-) Thanks a lot out there!! Cheers, Olaf Here are my linker errors: Undefined symbols: "_glTranslatef", referenced from: +[org_xmlvm_iphone_gl_GL glTranslatef___float_float_float:::] in org_xmlvm_iphone_gl_GL.o "_glDisableClientState", referenced from: +[org_xmlvm_iphone_gl_GL glDisableClientState___int:] in org_xmlvm_iphone_gl_GL.o ".objc_class_name_EAGLContext", referenced from: literal-pointer@__OBJC@__cls_refs@EAGLContext in org_xmlvm_iphone_gl_EAGLContext.o literal-pointer@__OBJC@__cls_refs@EAGLContext in org_xmlvm_iphone_gl_GLView.o "_glBindRenderbufferOES", referenced from: +[org_xmlvm_iphone_gl_GL glBindRenderbufferOES___int_int::] in org_xmlvm_iphone_gl_GL.o -[org_xmlvm_iphone_gl_GLView createFramebuffer__] in org_xmlvm_iphone_gl_GLView.o -[org_xmlvm_iphone_gl_GLView drawView__] in org_xmlvm_iphone_gl_GLView.o "_glLineWidth", referenced from: +[org_xmlvm_iphone_gl_GL glLineWidth___float:] in org_xmlvm_iphone_gl_GL.o "_glClearColor", referenced from: +[org_xmlvm_iphone_gl_GL glClearColor___float_float_float_float::::] in org_xmlvm_iphone_gl_GL.o -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o "_glFrustumf", referenced from: +[org_xmlvm_iphone_gl_GL glFrustumf___float_float_float_float_float_float::::::] in org_xmlvm_iphone_gl_GL.o "_glClear", referenced from: +[org_xmlvm_iphone_gl_GL glClear___int:] in org_xmlvm_iphone_gl_GL.o -[org_xmlvm_iphone_gl_GLView drawView__] in org_xmlvm_iphone_gl_GLView.o "_glTexParameteri", referenced from: +[org_xmlvm_iphone_gl_GL glTexParameteri___int_int_int:::] in org_xmlvm_iphone_gl_GL.o "_glOrthof", referenced from: +[org_xmlvm_iphone_gl_GL glOrthof___float_float_float_float_float_float::::::] in org_xmlvm_iphone_gl_GL.o -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o "_glEnable", referenced from: +[org_xmlvm_iphone_gl_GL glEnable___int:] in org_xmlvm_iphone_gl_GL.o -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o "_glScalef", referenced from: +[org_xmlvm_iphone_gl_GL glScalef___float_float_float:::] in org_xmlvm_iphone_gl_GL.o "_glDrawArrays", referenced from: +[org_xmlvm_iphone_gl_GL glDrawArrays___int_int_int:::] in org_xmlvm_iphone_gl_GL.o "_glGenFramebuffersOES", referenced from: +[org_xmlvm_iphone_gl_GL glGenFramebuffersOES___int:] in org_xmlvm_iphone_gl_GL.o -[org_xmlvm_iphone_gl_GLView createFramebuffer__] in org_xmlvm_iphone_gl_GLView.o ".objc_class_name_AVAudioPlayer", referenced from: literal-pointer@__OBJC@__cls_refs@AVAudioPlayer in android_media_MediaPlayer.o literal-pointer@__OBJC@__cls_refs@AVAudioPlayer in org_xmlvm_iphone_AVAudioPlayer.o "_glVertexPointer", referenced from: +[org_xmlvm_iphone_gl_GL glVertexPointer___int_int_int_java_nio_FloatBuffer::::] in org_xmlvm_iphone_gl_GL.o "_glBindTexture", referenced from: +[org_xmlvm_iphone_gl_GL glBindTexture___int_int::] in org_xmlvm_iphone_gl_GL.o "_glLoadIdentity", referenced from: +[org_xmlvm_iphone_gl_GL glLoadIdentity__] in org_xmlvm_iphone_gl_GL.o -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o "_kEAGLDrawablePropertyColorFormat", referenced from: _kEAGLDrawablePropertyColorFormat$non_lazy_ptr in org_xmlvm_iphone_gl_CAEAGLLayer.o _kEAGLDrawablePropertyColorFormat$non_lazy_ptr in org_xmlvm_iphone_gl_GLView.o "_kEAGLDrawablePropertyRetainedBacking", referenced from: _kEAGLDrawablePropertyRetainedBacking$non_lazy_ptr in org_xmlvm_iphone_gl_CAEAGLLayer.o _kEAGLDrawablePropertyRetainedBacking$non_lazy_ptr in org_xmlvm_iphone_gl_GLView.o "_glGenTextures", referenced from: +[org_xmlvm_iphone_gl_GL glGenTextures___int_java_nio_IntBuffer::] in org_xmlvm_iphone_gl_GL.o "_glDisable", referenced from: +[org_xmlvm_iphone_gl_GL glDisable___int:] in org_xmlvm_iphone_gl_GL.o "_glBlendFunc", referenced from: +[org_xmlvm_iphone_gl_GL glBlendFunc___int_int::] in org_xmlvm_iphone_gl_GL.o -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o "_glViewport", referenced from: +[org_xmlvm_iphone_gl_GL glViewport___int_int_int_int::::] in org_xmlvm_iphone_gl_GL.o -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o ".objc_class_name_CAEAGLLayer", referenced from: literal-pointer@__OBJC@__cls_refs@CAEAGLLayer in org_xmlvm_iphone_gl_GLView.o "_glColor4f", referenced from: +[org_xmlvm_iphone_gl_GL glColor4f___float_float_float_float::::] in org_xmlvm_iphone_gl_GL.o "_glGenRenderbuffersOES", referenced from: +[org_xmlvm_iphone_gl_GL glGenRenderbuffersOES___int:] in org_xmlvm_iphone_gl_GL.o -[org_xmlvm_iphone_gl_GLView createFramebuffer__] in org_xmlvm_iphone_gl_GLView.o "_glBindFramebufferOES", referenced from: +[org_xmlvm_iphone_gl_GL glBindFramebufferOES___int_int::] in org_xmlvm_iphone_gl_GL.o -[org_xmlvm_iphone_gl_GLView createFramebuffer__] in org_xmlvm_iphone_gl_GLView.o -[org_xmlvm_iphone_gl_GLView drawView__] in org_xmlvm_iphone_gl_GLView.o "_glDeleteRenderbuffersOES", referenced from: +[org_xmlvm_iphone_gl_GL glDeleteRenderbuffersOES___int_int::] in org_xmlvm_iphone_gl_GL.o -[org_xmlvm_iphone_gl_GLView destroyFramebuffer__] in org_xmlvm_iphone_gl_GLView.o -[org_xmlvm_iphone_gl_GLView destroyFramebuffer__] in org_xmlvm_iphone_gl_GLView.o "_glDeleteFramebuffersOES", referenced from: +[org_xmlvm_iphone_gl_GL glDeleteFramebuffersOES___int_int::] in org_xmlvm_iphone_gl_GL.o -[org_xmlvm_iphone_gl_GLView destroyFramebuffer__] in org_xmlvm_iphone_gl_GLView.o "_glTexCoordPointer", referenced from: +[org_xmlvm_iphone_gl_GL glTexCoordPointer___int_int_int_java_nio_FloatBuffer::::] in org_xmlvm_iphone_gl_GL.o "_glEnableClientState", referenced from: +[org_xmlvm_iphone_gl_GL glEnableClientState___int:] in org_xmlvm_iphone_gl_GL.o "_glMatrixMode", referenced from: +[org_xmlvm_iphone_gl_GL glMatrixMode___int:] in org_xmlvm_iphone_gl_GL.o -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o "_glFramebufferRenderbufferOES", referenced from: +[org_xmlvm_iphone_gl_GL glFramebufferRenderbufferOES___int_int_int_int::::] in org_xmlvm_iphone_gl_GL.o -[org_xmlvm_iphone_gl_GLView createFramebuffer__] in org_xmlvm_iphone_gl_GLView.o "_glTexImage2D", referenced from: +[org_xmlvm_iphone_gl_GL glTexImage2D___int_int_int_int_int_int_int_int_java_nio_ByteBuffer:::::::::] in org_xmlvm_iphone_gl_GL.o "_glRotatef", referenced from: +[org_xmlvm_iphone_gl_GL glRotatef___float_float_float_float::::] in org_xmlvm_iphone_gl_GL.o "_glCheckFramebufferStatusOES", referenced from: +[org_xmlvm_iphone_gl_GL glCheckFramebufferStatusOES___int:] in org_xmlvm_iphone_gl_GL.o -[org_xmlvm_iphone_gl_GLView createFramebuffer__] in org_xmlvm_iphone_gl_GLView.o -[org_xmlvm_iphone_gl_GLView createFramebuffer__] in org_xmlvm_iphone_gl_GLView.o -[org_xmlvm_iphone_gl_GLView createFramebuffer__] in org_xmlvm_iphone_gl_GLView.o "_glColorPointer", referenced from: +[org_xmlvm_iphone_gl_GL glColorPointer___int_int_int_java_nio_FloatBuffer::::] in org_xmlvm_iphone_gl_GL.o "_kEAGLColorFormatRGBA8", referenced from: _kEAGLColorFormatRGBA8$non_lazy_ptr in org_xmlvm_iphone_gl_CAEAGLLayer.o _kEAGLColorFormatRGBA8$non_lazy_ptr in org_xmlvm_iphone_gl_GLView.o ld: symbol(s) not found collect2: ld returned 1 exit status |
From: <Zor...@gm...> - 2010-03-26 12:29:23
|
Hello again community! Isn't there somebody who could tell me how to get started? It reads like the people discussing here are actually using xmlvm - and I would like to do this,too. But why can't I get the simple SayHello demo cross compiled and running? Where's the missing clue? I did everything as described in the short documentation; but xmlvm throws lots of WARNINGS ("InputProcesses couldn't be created") and the result simply crashes on the iPhone simulator. Xcode shows me a bunch of linker errors with the SayHello demo and with one of my Android programs it even shows hundreds of compiler errors (header files missing). Can somebody please give me a short step-by-step description what has to be done to get SayHello cross-compile? Am I using the wrong versions of Xcode (3.2.1) or Java (1.6) or where could be the problem??? Thanks a lot!!!!!!! Regards, Olaf |
From: Arno P. <ar...@pu...> - 2010-03-26 12:36:08
|
Olaf, there is sadly not much documentation and the little bit we do have is outdated. It seems that you managed to check out XMLVM and to compile it. If there is no error when invoking 'ant', you will have compiled XMLVM as well as all the demos. If you would like to see how to cross-compile SayHello, I would suggest you take a look at build.xml. XMLVM generates a ready-to-use Xcode project file. All the steps mentioned in the documentation are not needed anymore. After you run ant, simply do 'open dist/demo/android/sayhello/iphone/SayHello.xcodeproj'. That's it! Arno On 3/25/10 10:22 AM, Zor...@gm... wrote: > Hello there! > I am an Android Developer who was just about to dig into Objective-C and iPhone development because the need arose to also target iPhones as well as Android phones. > Because of that I was extremely excited when I found Xmlvm just a few days ago! > > But, unfortunately, even though I tried to stick exactly to what the short documentation says about the demo projects, I got stuck pretty quickly. > Maybe I am not alone with this and maybe there's only a tiny little thing I missed that screws everthing up right now. > > Here's what I wanted to do: Take one of my Android Apps and simply port it right away. Okay, nice attempt - I got stuck with about a hundred error messages in the Xcode envirnment. > > So, I stepped back one step: try to get SayHello working out of the box... > > As there's no description of what is needed to try out the demos I'll give you my environment specs quickly: Macbook Pro with Xcode 3.2.1 and Eclipse 3.5 running the latest Android SDK r05. The rest is out of the box. > Xmlvm compiled fine using the ant script. > > Now, my first question: I understood that using Xmlvm for Android apps, it will take the Dalvik Code - but the command line interface for xmlvm only gets the SayHello's project folder (that's what I understood I'd have to do) > > So I call: > > xmlvm --in=../workspace/xmlvm/demo/android/sayhello/ --target=android-on-iphone --app-name="SayHello" > > With this command I get a lot of Warnings of the type: WARNING: Unable to create InputProcesses for input: [...] both for helper files like *.svn AND my *.java source files. Where should xmlvm get the Dalvik machine code from? Isn't that only within the apk file? I got no clue... > > Now: my first attempt was to get it working in the iPhone Simulator as that should be done by calling make and using the generated makefile. The simulator starts and there's the SayHello app - but it crashes right away. When I start it, it closes immediately. > > Second attempt: get into Xcode (which I really don't know yet...). I created a project, deleted main and xib File plus app delegates and the entry in the pList file. > Next question arose when trying to add files to the project: I don't have a MakeVars file (but I should not include it - where is it?) An Info.pList file is missing, too... > Okay, added all the files and pressed Build&Run... > > This gives me 39 linker errors which I add at the end of this post. > > > Now - what could be wrong here? Maybe I am not the only one who has a problem getting the first program to run? > Maybe it is possible to add a little bit more to the documentation so that these first steps don't get so hard to do? > > That would be great; as the whole idea behind xmlvm is just great and perfect! I would really LOVE not to end up learning the "latin language" or moving to the Vatikan... :-) > > Thanks a lot out there!! > Cheers, > Olaf > > > Here are my linker errors: > Undefined symbols: > "_glTranslatef", referenced from: > +[org_xmlvm_iphone_gl_GL glTranslatef___float_float_float:::] in org_xmlvm_iphone_gl_GL.o > "_glDisableClientState", referenced from: > +[org_xmlvm_iphone_gl_GL glDisableClientState___int:] in org_xmlvm_iphone_gl_GL.o > ".objc_class_name_EAGLContext", referenced from: > literal-pointer@__OBJC@__cls_refs@EAGLContext in org_xmlvm_iphone_gl_EAGLContext.o > literal-pointer@__OBJC@__cls_refs@EAGLContext in org_xmlvm_iphone_gl_GLView.o > "_glBindRenderbufferOES", referenced from: > +[org_xmlvm_iphone_gl_GL glBindRenderbufferOES___int_int::] in org_xmlvm_iphone_gl_GL.o > -[org_xmlvm_iphone_gl_GLView createFramebuffer__] in org_xmlvm_iphone_gl_GLView.o > -[org_xmlvm_iphone_gl_GLView drawView__] in org_xmlvm_iphone_gl_GLView.o > "_glLineWidth", referenced from: > +[org_xmlvm_iphone_gl_GL glLineWidth___float:] in org_xmlvm_iphone_gl_GL.o > "_glClearColor", referenced from: > +[org_xmlvm_iphone_gl_GL glClearColor___float_float_float_float::::] in org_xmlvm_iphone_gl_GL.o > -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o > "_glFrustumf", referenced from: > +[org_xmlvm_iphone_gl_GL glFrustumf___float_float_float_float_float_float::::::] in org_xmlvm_iphone_gl_GL.o > "_glClear", referenced from: > +[org_xmlvm_iphone_gl_GL glClear___int:] in org_xmlvm_iphone_gl_GL.o > -[org_xmlvm_iphone_gl_GLView drawView__] in org_xmlvm_iphone_gl_GLView.o > "_glTexParameteri", referenced from: > +[org_xmlvm_iphone_gl_GL glTexParameteri___int_int_int:::] in org_xmlvm_iphone_gl_GL.o > "_glOrthof", referenced from: > +[org_xmlvm_iphone_gl_GL glOrthof___float_float_float_float_float_float::::::] in org_xmlvm_iphone_gl_GL.o > -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o > "_glEnable", referenced from: > +[org_xmlvm_iphone_gl_GL glEnable___int:] in org_xmlvm_iphone_gl_GL.o > -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o > -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o > "_glScalef", referenced from: > +[org_xmlvm_iphone_gl_GL glScalef___float_float_float:::] in org_xmlvm_iphone_gl_GL.o > "_glDrawArrays", referenced from: > +[org_xmlvm_iphone_gl_GL glDrawArrays___int_int_int:::] in org_xmlvm_iphone_gl_GL.o > "_glGenFramebuffersOES", referenced from: > +[org_xmlvm_iphone_gl_GL glGenFramebuffersOES___int:] in org_xmlvm_iphone_gl_GL.o > -[org_xmlvm_iphone_gl_GLView createFramebuffer__] in org_xmlvm_iphone_gl_GLView.o > ".objc_class_name_AVAudioPlayer", referenced from: > literal-pointer@__OBJC@__cls_refs@AVAudioPlayer in android_media_MediaPlayer.o > literal-pointer@__OBJC@__cls_refs@AVAudioPlayer in org_xmlvm_iphone_AVAudioPlayer.o > "_glVertexPointer", referenced from: > +[org_xmlvm_iphone_gl_GL glVertexPointer___int_int_int_java_nio_FloatBuffer::::] in org_xmlvm_iphone_gl_GL.o > "_glBindTexture", referenced from: > +[org_xmlvm_iphone_gl_GL glBindTexture___int_int::] in org_xmlvm_iphone_gl_GL.o > "_glLoadIdentity", referenced from: > +[org_xmlvm_iphone_gl_GL glLoadIdentity__] in org_xmlvm_iphone_gl_GL.o > -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o > "_kEAGLDrawablePropertyColorFormat", referenced from: > _kEAGLDrawablePropertyColorFormat$non_lazy_ptr in org_xmlvm_iphone_gl_CAEAGLLayer.o > _kEAGLDrawablePropertyColorFormat$non_lazy_ptr in org_xmlvm_iphone_gl_GLView.o > "_kEAGLDrawablePropertyRetainedBacking", referenced from: > _kEAGLDrawablePropertyRetainedBacking$non_lazy_ptr in org_xmlvm_iphone_gl_CAEAGLLayer.o > _kEAGLDrawablePropertyRetainedBacking$non_lazy_ptr in org_xmlvm_iphone_gl_GLView.o > "_glGenTextures", referenced from: > +[org_xmlvm_iphone_gl_GL glGenTextures___int_java_nio_IntBuffer::] in org_xmlvm_iphone_gl_GL.o > "_glDisable", referenced from: > +[org_xmlvm_iphone_gl_GL glDisable___int:] in org_xmlvm_iphone_gl_GL.o > "_glBlendFunc", referenced from: > +[org_xmlvm_iphone_gl_GL glBlendFunc___int_int::] in org_xmlvm_iphone_gl_GL.o > -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o > "_glViewport", referenced from: > +[org_xmlvm_iphone_gl_GL glViewport___int_int_int_int::::] in org_xmlvm_iphone_gl_GL.o > -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o > ".objc_class_name_CAEAGLLayer", referenced from: > literal-pointer@__OBJC@__cls_refs@CAEAGLLayer in org_xmlvm_iphone_gl_GLView.o > "_glColor4f", referenced from: > +[org_xmlvm_iphone_gl_GL glColor4f___float_float_float_float::::] in org_xmlvm_iphone_gl_GL.o > "_glGenRenderbuffersOES", referenced from: > +[org_xmlvm_iphone_gl_GL glGenRenderbuffersOES___int:] in org_xmlvm_iphone_gl_GL.o > -[org_xmlvm_iphone_gl_GLView createFramebuffer__] in org_xmlvm_iphone_gl_GLView.o > "_glBindFramebufferOES", referenced from: > +[org_xmlvm_iphone_gl_GL glBindFramebufferOES___int_int::] in org_xmlvm_iphone_gl_GL.o > -[org_xmlvm_iphone_gl_GLView createFramebuffer__] in org_xmlvm_iphone_gl_GLView.o > -[org_xmlvm_iphone_gl_GLView drawView__] in org_xmlvm_iphone_gl_GLView.o > "_glDeleteRenderbuffersOES", referenced from: > +[org_xmlvm_iphone_gl_GL glDeleteRenderbuffersOES___int_int::] in org_xmlvm_iphone_gl_GL.o > -[org_xmlvm_iphone_gl_GLView destroyFramebuffer__] in org_xmlvm_iphone_gl_GLView.o > -[org_xmlvm_iphone_gl_GLView destroyFramebuffer__] in org_xmlvm_iphone_gl_GLView.o > "_glDeleteFramebuffersOES", referenced from: > +[org_xmlvm_iphone_gl_GL glDeleteFramebuffersOES___int_int::] in org_xmlvm_iphone_gl_GL.o > -[org_xmlvm_iphone_gl_GLView destroyFramebuffer__] in org_xmlvm_iphone_gl_GLView.o > "_glTexCoordPointer", referenced from: > +[org_xmlvm_iphone_gl_GL glTexCoordPointer___int_int_int_java_nio_FloatBuffer::::] in org_xmlvm_iphone_gl_GL.o > "_glEnableClientState", referenced from: > +[org_xmlvm_iphone_gl_GL glEnableClientState___int:] in org_xmlvm_iphone_gl_GL.o > "_glMatrixMode", referenced from: > +[org_xmlvm_iphone_gl_GL glMatrixMode___int:] in org_xmlvm_iphone_gl_GL.o > -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o > -[org_xmlvm_iphone_gl_GLView setupView__] in org_xmlvm_iphone_gl_GLView.o > "_glFramebufferRenderbufferOES", referenced from: > +[org_xmlvm_iphone_gl_GL glFramebufferRenderbufferOES___int_int_int_int::::] in org_xmlvm_iphone_gl_GL.o > -[org_xmlvm_iphone_gl_GLView createFramebuffer__] in org_xmlvm_iphone_gl_GLView.o > "_glTexImage2D", referenced from: > +[org_xmlvm_iphone_gl_GL glTexImage2D___int_int_int_int_int_int_int_int_java_nio_ByteBuffer:::::::::] in org_xmlvm_iphone_gl_GL.o > "_glRotatef", referenced from: > +[org_xmlvm_iphone_gl_GL glRotatef___float_float_float_float::::] in org_xmlvm_iphone_gl_GL.o > "_glCheckFramebufferStatusOES", referenced from: > +[org_xmlvm_iphone_gl_GL glCheckFramebufferStatusOES___int:] in org_xmlvm_iphone_gl_GL.o > -[org_xmlvm_iphone_gl_GLView createFramebuffer__] in org_xmlvm_iphone_gl_GLView.o > -[org_xmlvm_iphone_gl_GLView createFramebuffer__] in org_xmlvm_iphone_gl_GLView.o > -[org_xmlvm_iphone_gl_GLView createFramebuffer__] in org_xmlvm_iphone_gl_GLView.o > "_glColorPointer", referenced from: > +[org_xmlvm_iphone_gl_GL glColorPointer___int_int_int_java_nio_FloatBuffer::::] in org_xmlvm_iphone_gl_GL.o > "_kEAGLColorFormatRGBA8", referenced from: > _kEAGLColorFormatRGBA8$non_lazy_ptr in org_xmlvm_iphone_gl_CAEAGLLayer.o > _kEAGLColorFormatRGBA8$non_lazy_ptr in org_xmlvm_iphone_gl_GLView.o > ld: symbol(s) not found > collect2: ld returned 1 exit status > > > > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users |
From: <Zor...@gm...> - 2010-03-26 12:50:50
|
Arno, thanks a lot! Now, that helped a little bit already: knowing that opening the project in Xcode directly, without doing the steps mentioned in the documentation is good! Sadly, the result I get is identical to what I got when running "make" yesterday: the application starts (within the iPhone simulator), but closes immediately before displaying anything. I assume this is the behavior of a crashing application...? Now, in your talk you mention that whenever something goes wrong with a cross-compiled application after successfull cross-compilation, it must be a bug in xmlvm, not generating the correct code. But could it be that a simple app SayHello cannot be correctly ported? I did not want to go into tracing the resulting Xcode program and as I am not familiar with ObjC (yet) that does not sound like a good option. I checked out the trunk of xmlvm's svn repository - is that correct? Or is that a not-so-stable version? Thanks so far!!! Helped a little bit already! :-) Regards, Olaf > > Olaf, > > there is sadly not much documentation and the little bit we do have is > outdated. It seems that you managed to check out XMLVM and to compile > it. If there is no error when invoking 'ant', you will have compiled > XMLVM as well as all the demos. If you would like to see how to > cross-compile SayHello, I would suggest you take a look at build.xml. > > XMLVM generates a ready-to-use Xcode project file. All the steps > mentioned in the documentation are not needed anymore. After you run > ant, simply do 'open > dist/demo/android/sayhello/iphone/SayHello.xcodeproj'. That's it! > > Arno |
From: Panayotis K. <pan...@pa...> - 2010-03-26 12:52:16
|
On 26 Μαρ 2010, at 2:50 ΜΜ, Zor...@gm... wrote: > Arno, > > thanks a lot! Now, that helped a little bit already: knowing that > opening the project in Xcode directly, without doing the steps > mentioned in the documentation is good! > > Sadly, the result I get is identical to what I got when running > "make" yesterday: the application starts (within the iPhone > simulator), but closes immediately before displaying anything. I > assume this is the behavior of a crashing application...? > > Now, in your talk you mention that whenever something goes wrong > with a cross-compiled application after successfull cross- > compilation, it must be a bug in xmlvm, not generating the correct > code. But could it be that a simple app SayHello cannot be correctly > ported? > > I did not want to go into tracing the resulting Xcode program and as > I am not familiar with ObjC (yet) that does not sound like a good > option. > > I checked out the trunk of xmlvm's svn repository - is that correct? > Or is that a not-so-stable version? > > Thanks so far!!! Helped a little bit already! :-) > Regards, > Olaf Which OS are you using? Which version of Java? |
From: Arno P. <ar...@pu...> - 2010-03-26 13:05:28
|
I just tried SayHello and it works fine on my system. Which version of Xcode are you using? Arno On 3/26/10 5:50 AM, Zor...@gm... wrote: > Arno, > > thanks a lot! Now, that helped a little bit already: knowing that opening the project in Xcode directly, without doing the steps mentioned in the documentation is good! > > Sadly, the result I get is identical to what I got when running "make" yesterday: the application starts (within the iPhone simulator), but closes immediately before displaying anything. I assume this is the behavior of a crashing application...? > > Now, in your talk you mention that whenever something goes wrong with a cross-compiled application after successfull cross-compilation, it must be a bug in xmlvm, not generating the correct code. But could it be that a simple app SayHello cannot be correctly ported? > > I did not want to go into tracing the resulting Xcode program and as I am not familiar with ObjC (yet) that does not sound like a good option. > > I checked out the trunk of xmlvm's svn repository - is that correct? Or is that a not-so-stable version? > > Thanks so far!!! Helped a little bit already! :-) > Regards, > Olaf > > > >> >> Olaf, >> >> there is sadly not much documentation and the little bit we do have is >> outdated. It seems that you managed to check out XMLVM and to compile >> it. If there is no error when invoking 'ant', you will have compiled >> XMLVM as well as all the demos. If you would like to see how to >> cross-compile SayHello, I would suggest you take a look at build.xml. >> >> XMLVM generates a ready-to-use Xcode project file. All the steps >> mentioned in the documentation are not needed anymore. After you run >> ant, simply do 'open >> dist/demo/android/sayhello/iphone/SayHello.xcodeproj'. That's it! >> >> Arno |
From: Olaf G. <Zor...@gm...> - 2010-03-26 13:08:39
|
Versions in use here: Mac OS 10.6.2 Xcode 3.2.1 Java 1.6.0_15 Olaf -------- Original-Nachricht -------- > Datum: Fri, 26 Mar 2010 06:05:17 -0700 > Von: Arno Puder <ar...@pu...> > An: xml...@li... > Betreff: Re: [xmlvm-users] Help needed: problems getting started with android-on-iphone > > I just tried SayHello and it works fine on my system. Which version of > Xcode are you using? > > Arno |
From: Wolfgang K. <wol...@xm...> - 2010-03-26 13:16:50
|
I just tried SayHello and it worked fine. Are sure to have the most recent version of XMLVM? I remember having that kind of problem after applying patch 19001. I had to update the Android compat lib to make use of the now supported folder structures for resources. -- Wolfgang Olaf Gottschalk wrote: > Versions in use here: > > Mac OS 10.6.2 > Xcode 3.2.1 > Java 1.6.0_15 > > Olaf > > -------- Original-Nachricht -------- > >> Datum: Fri, 26 Mar 2010 06:05:17 -0700 >> Von: Arno Puder <ar...@pu...> >> An: xml...@li... >> Betreff: Re: [xmlvm-users] Help needed: problems getting started with android-on-iphone >> > > >> I just tried SayHello and it works fine on my system. Which version of >> Xcode are you using? >> >> Arno >> > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users > |
From: Olaf G. <Zor...@gm...> - 2010-03-26 13:22:46
|
I checked out the trunk just yesterday. Do I have to do anything special then? The only file that changed since then is ReferenceCounting.java... Olaf -------- Original-Nachricht -------- > Datum: Fri, 26 Mar 2010 14:16:37 +0100 > Von: Wolfgang Korn <wol...@xm...> > An: Olaf Gottschalk <Zor...@gm...> > CC: Arno Puder <ar...@pu...>, xml...@li... > Betreff: Re: [xmlvm-users] Help needed: problems getting started with android-on-iphone > I just tried SayHello and it worked fine. Are sure to have the most > recent version of XMLVM? I remember having that kind of problem after > applying patch 19001. I had to update the Android compat lib to make use > of the now supported folder structures for resources. > > -- Wolfgang |
From: Olaf G. <Zor...@gm...> - 2010-03-26 14:19:15
|
yes! That works! But tell me, where's the difference? I thought that the ant command prepares xmlvm itself - not the demos. Thus, after building xmlvm, I created a new, empty directory and ran: xmlvm --in=<path-to-xmlvm>/demo/iphone/ifireworks --target=iphone --app-name=ifireworks. make => which leads directly to the linker error described. Even SayHello works fine using the dist/demo/android/sayhello pre-build Xcode project!! But what on earth is different when I try to cross-compile it myself??? Again, all I do in an empty directory is xmlvm --in=<path-to-xmlvm>/demo/android/sayhello --target=android-on-iphone --app-name=sayhello make Can you try it that way, too? Or did you do it like that? My problem is: I want to port my own program, not SayHello... :-) Thus, I need to get it running "myself", not through the dist. :-( Thanks again!!! Olaf -------- Original-Nachricht -------- > Datum: Fri, 26 Mar 2010 07:08:24 -0700 > Von: Arno Puder <ar...@pu...> > An: Olaf Gottschalk <Zor...@gm...> > CC: xml...@li... > Betreff: Re: [xmlvm-users] Help needed: problems getting started with android-on-iphone > > after running 'ant', try: > > open dist/demo/iphone/ifireworks/iphone/iFireworks.xcodeproj/ > > this works flawlessly for me. If this does not work for you, I'm running > out of ideas what might be the problem with your configuration. > > Arno |
From: Arno P. <ar...@pu...> - 2010-03-26 14:22:31
|
ok, I think I know what you do wrong. You first have to compile the Java sources with javac, *then* run xmlvm over the generated class files. Your --in argument points to the *source* directory, not the directory where the .class files should reside. Since there are no .class files in the --in directory you specified, you get the errors you observed. Arno On 3/26/10 7:19 AM, Olaf Gottschalk wrote: > yes! > That works! > > But tell me, where's the difference? I thought that the ant command prepares xmlvm itself - not the demos. Thus, after building xmlvm, I created a new, empty directory and ran: > > xmlvm --in=<path-to-xmlvm>/demo/iphone/ifireworks --target=iphone --app-name=ifireworks. > make > > => which leads directly to the linker error described. > > Even SayHello works fine using the dist/demo/android/sayhello pre-build Xcode project!! > > But what on earth is different when I try to cross-compile it myself??? > Again, all I do in an empty directory is > > xmlvm --in=<path-to-xmlvm>/demo/android/sayhello --target=android-on-iphone --app-name=sayhello > make > > Can you try it that way, too? Or did you do it like that? > > My problem is: I want to port my own program, not SayHello... :-) Thus, I need to get it running "myself", not through the dist. :-( > > Thanks again!!! > Olaf > > > -------- Original-Nachricht -------- >> Datum: Fri, 26 Mar 2010 07:08:24 -0700 >> Von: Arno Puder<ar...@pu...> >> An: Olaf Gottschalk<Zor...@gm...> >> CC: xml...@li... >> Betreff: Re: [xmlvm-users] Help needed: problems getting started with android-on-iphone > >> >> after running 'ant', try: >> >> open dist/demo/iphone/ifireworks/iphone/iFireworks.xcodeproj/ >> >> this works flawlessly for me. If this does not work for you, I'm running >> out of ideas what might be the problem with your configuration. >> >> Arno > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users |
From: Olaf G. <Zor...@gm...> - 2010-03-26 14:04:01
|
No, iFireworks does not work. I get a linker error... But I am not sure. For ifireworks I used xmlvm --in=.... --target=iphone -app-name=ifireworks and in running the resulting makefile or using Xcode gives the mentioned linker error. :-( Olaf Here it is: Ld build/Debug-iphonesimulator/ifireworks.app/ifireworks normal i386 cd /Users/q163557/ifireworks setenv MACOSX_DEPLOYMENT_TARGET 10.5 setenv PATH "/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin" /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/gcc-4.2 -arch i386 -isysroot /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.1.sdk -L/Users/q163557/ifireworks/build/Debug-iphonesimulator -F/Users/q163557/ifireworks/build/Debug-iphonesimulator -filelist /Users/q163557/ifireworks/build/ifireworks.build/Debug-iphonesimulator/ifireworks.build/Objects-normal/i386/ifireworks.LinkFileList -mmacosx-version-min=10.5 -framework OpenGLES -framework Foundation -framework AVFoundation -framework UIKit -framework QuartzCore -framework CoreGraphics -o /Users/q163557/ifireworks/build/Debug-iphonesimulator/ifireworks.app/ifireworks Undefined symbols: "_main", referenced from: start in crt1.10.5.o ld: symbol(s) not found collect2: ld returned 1 exit status |
From: <Zor...@gm...> - 2010-03-26 12:54:43
|
Sorry for writing again, but here's the stack trace of the iPhone simulator when running SayHello: [Session started at 2010-03-26 13:45:07 +0100.] 2010-03-26 13:45:17.508 SayHello[2522:207] *** -[NSNull getFileSystemRepresentation:maxLength:]: unrecognized selector sent to instance 0x1f9a5a0 2010-03-26 13:45:17.509 SayHello[2522:207] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSNull getFileSystemRepresentation:maxLength:]: unrecognized selector sent to instance 0x1f9a5a0' 2010-03-26 13:45:17.516 SayHello[2522:207] Stack: ( 32539739, 2449900809, 32921659, 32491126, 32343746, 2360353, 2360262, 2435603, 2643944, 63419, 395505, 393244, 394289, 394457 ) > Olaf, > > there is sadly not much documentation and the little bit we do have is > outdated. It seems that you managed to check out XMLVM and to compile > it. If there is no error when invoking 'ant', you will have compiled > XMLVM as well as all the demos. If you would like to see how to > cross-compile SayHello, I would suggest you take a look at build.xml. > > XMLVM generates a ready-to-use Xcode project file. All the steps > mentioned in the documentation are not needed anymore. After you run > ant, simply do 'open > dist/demo/android/sayhello/iphone/SayHello.xcodeproj'. That's it! > > Arno |
From: Arno P. <ar...@pu...> - 2010-03-26 13:39:15
|
very difficult to figure out what is different on your machine. Can you try one of the iPhone demos (e.g., iFireworks)? Arno On 3/26/10 6:22 AM, Olaf Gottschalk wrote: > I checked out the trunk just yesterday. Do I have to do anything special then? The only file that changed since then is ReferenceCounting.java... > > Olaf > > > -------- Original-Nachricht -------- >> Datum: Fri, 26 Mar 2010 14:16:37 +0100 >> Von: Wolfgang Korn<wol...@xm...> >> An: Olaf Gottschalk<Zor...@gm...> >> CC: Arno Puder<ar...@pu...>, xml...@li... >> Betreff: Re: [xmlvm-users] Help needed: problems getting started with android-on-iphone > >> I just tried SayHello and it worked fine. Are sure to have the most >> recent version of XMLVM? I remember having that kind of problem after >> applying patch 19001. I had to update the Android compat lib to make use >> of the now supported folder structures for resources. >> >> -- Wolfgang |
From: Arno P. <ar...@pu...> - 2010-03-26 14:08:35
|
after running 'ant', try: open dist/demo/iphone/ifireworks/iphone/iFireworks.xcodeproj/ this works flawlessly for me. If this does not work for you, I'm running out of ideas what might be the problem with your configuration. Arno On 3/26/10 7:03 AM, Olaf Gottschalk wrote: > No, iFireworks does not work. I get a linker error... > But I am not sure. For ifireworks I used xmlvm --in=.... --target=iphone -app-name=ifireworks and in running the resulting makefile or using Xcode gives the mentioned linker error. > :-( > Olaf > > > > Here it is: > > Ld build/Debug-iphonesimulator/ifireworks.app/ifireworks normal i386 > cd /Users/q163557/ifireworks > setenv MACOSX_DEPLOYMENT_TARGET 10.5 > setenv PATH "/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin" > /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/gcc-4.2 -arch i386 -isysroot /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator3.1.sdk -L/Users/q163557/ifireworks/build/Debug-iphonesimulator -F/Users/q163557/ifireworks/build/Debug-iphonesimulator -filelist /Users/q163557/ifireworks/build/ifireworks.build/Debug-iphonesimulator/ifireworks.build/Objects-normal/i386/ifireworks.LinkFileList -mmacosx-version-min=10.5 -framework OpenGLES -framework Foundation -framework AVFoundation -framework UIKit -framework QuartzCore -framework CoreGraphics -o /Users/q163557/ifireworks/build/Debug-iphonesimulator/ifireworks.app/ifireworks > > Undefined symbols: > "_main", referenced from: > start in crt1.10.5.o > ld: symbol(s) not found > collect2: ld returned 1 exit status > |
From: Wolfgang K. <wol...@xm...> - 2010-03-26 14:22:57
|
Looking at the command you use to cross-compile SayHello, I see that the resources are missing. The same is true for iFireworks. Have a look at the xmlvm commands which are used in build.xml. This will probably give you the hint you need to understand what is going wrong. -- Wolfgang Olaf Gottschalk wrote: > yes! > That works! > > But tell me, where's the difference? I thought that the ant command prepares xmlvm itself - not the demos. Thus, after building xmlvm, I created a new, empty directory and ran: > > xmlvm --in=<path-to-xmlvm>/demo/iphone/ifireworks --target=iphone --app-name=ifireworks. > make > > => which leads directly to the linker error described. > > Even SayHello works fine using the dist/demo/android/sayhello pre-build Xcode project!! > > But what on earth is different when I try to cross-compile it myself??? > Again, all I do in an empty directory is > > xmlvm --in=<path-to-xmlvm>/demo/android/sayhello --target=android-on-iphone --app-name=sayhello > make > > Can you try it that way, too? Or did you do it like that? > > My problem is: I want to port my own program, not SayHello... :-) Thus, I need to get it running "myself", not through the dist. :-( > > Thanks again!!! > Olaf > > > -------- Original-Nachricht -------- > >> Datum: Fri, 26 Mar 2010 07:08:24 -0700 >> Von: Arno Puder <ar...@pu...> >> An: Olaf Gottschalk <Zor...@gm...> >> CC: xml...@li... >> Betreff: Re: [xmlvm-users] Help needed: problems getting started with android-on-iphone >> > > >> after running 'ant', try: >> >> open dist/demo/iphone/ifireworks/iphone/iFireworks.xcodeproj/ >> >> this works flawlessly for me. If this does not work for you, I'm running >> out of ideas what might be the problem with your configuration. >> >> Arno >> > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users > |
From: Olaf G. <Zor...@gm...> - 2010-03-26 14:37:39
|
Thanks Arno, thanks Wolfgang! Your last two posts gave me the missing link - but still, I am a little bit confused. In my first post, I already had those questions: how do the ressources get into the Xcode project and why does the cross compilation not make use of class/dex files!! The answer: the in-parameter should point to the classes, not the sources? And: there is a resource parameter (which is not described in the documentation... :-( ) I am now trying to understand the build.xml, but it's rather painful. Could someone give me a short example how you cross compile... I have never (manually) used javac - I always do everything in Eclipse... So, having ANY Android program in Eclipse. 1) run it in the Android emulator - this will compile it to .class files (and also to an .apk - but is that also used by xmlvm??) 2) the correct command line arguemts for xmlvm: -in=pointing to which directory?? the project? the apk? -target=android-on-iphone -out=(i never used it, always cross compiled to the current dir) -resource=the res directory of the Android project? plus the Manifest? what else? 3) opening the Xcodeproject file in Xcode, press Build & Run That's it? Am I right?? Thanks a lot!! Olaf |