From: Arno P. <ar...@pu...> - 2012-12-29 10:55:23
|
On 12/25/12 7:15 AM, Kurayami Tenshi wrote: > I've been reading around and I'm confused as to which backend setting I > should use. The goal is to migrate to the C backend. The Objective-C backend is kept for backward compatibility reasons. The problem is that there is still work to do for the C backend (see my last message regarding crossmobile amongst others) but not enough volunteers. > So here are my questions > 1 - Backend: Can I use objc? If so, how do I fix the slew of warnings > about missing files? I would suggest you use the C backend. It is a lot more powerful than the aging ObjC backend. > 2 - If I have to use c, can anyone advice me on how I can call xmlvm > generated code in an Xcode objc project? Even the C backend still uses the ObjC compiler when you compile your project with Xcode (note that ObjC is a superset of C). I guess your question is about having manually written ObjC code that makes calls to generated C code. This can be tricky because you will have to understand the internals of the C backend. I would suggest you write some Java code that makes the calls to the Java API you plan to call from ObjC and take a look at the cross-compiled code. Arno |