Run the "ant native", and watch the output of the configure process.
The rules for configuring and building libffi and the other native
code is in native/Makefile, which gets run by ant in the "native"
target. I'd suggest *only* running it from the ant target, since
otherwise you might wind up with subtle differences in the build.
I'm moving this thread to the dev list. Post future questions there.
On Dec 21, 2007, at 6:10 AM, Carlos MacLeod wrote:
I successfully set up the mingwce on my linux box. I generated my
first program for wince. There are special tips to compile libfi ?
Will libfi be the win32-ARM.dll ?
2007/12/19, Timothy Wall <twal...@dev.java.net>:
That's probably your best option. Getting libffi to build under
anything other than GCC if you have an appropriate version of GCC
available would be wasted effort.
On Dec 19, 2007, at 8:16 AM, Carlos MacLeod wrote:
Is CeGCC a good option ?
2007/12/14, Timothy Wall <twal...@dev.java.net>:
The wince-arm target is supported by the underlying ffi library
(using mingw-ce as the compiler).
"Java is like violence: if it doesn's solve your problem, you aren't
using enough of it"
10 messages in net.java.dev.jna.usersRe: [jna-users] JNA at Win Mobile
