Cornelis Hoeflake wrote:

Thanks for your reply. Building a x64 build would be nice. But in the near future every user has a certain version (x64 or i386) on it's mac. Our client software runs on Java. So, our software runs sometimes on x64 and sometimes on i386. At the moment that OpenOffice and the JVM are build for a different architecture, bootstrapping fromout the JVM is not possible. I'm not sure, but this cannot be solved by compiling (for example) libjpipe.dylib to x86 AND i386 in one file. Is this correct?

It is possible to build universal JNI libraries on Mac OS X. Here's a link to an Apple article about building them in Xcode:

http://developer.apple.com/java/jniuniversal.html

The instructions there would have to be converted to work with command line utilities, but it should be possible. Notice also that it doesn't mention building for i386 and x86_64 at the same time, but I do think this should be possible. (Actually, I just thought of something that may prevent an i386 and x86_64 JNI binary, at least that supports Mac OS X 10.4.)

I must admit that I have been working on some other, personal projects for the past couple of weeks and not looking at OpenOffice.org. However, the personal projects and OOo are related in the sense that both involve mucking around command line programming options and managing projects with makefiles instead of Xcode.

So, long story short, what you want sounds do-able. I've been interested in creating universal binaries for OOo as well as 64-bit OOo binaries. I'll take a look at this, and since I just wrapped up one phase of these personal projects, I'll put some effort into this using DEV300_m13.

Part of the issue in this taking so long, is having to learn the OOo build system and all of its dependencies. It gets very complicated on Mac OS X, particularly if you have things installed from MacPorts, as I do.

Cheers,
Jason

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to