Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Ooops, I thought this (ppc/x86 JNI cross compile) was working

I was premature when I said my JNI lib was building on both platforms and running on both platforms. Turns out I can build it on the IntelMini and it will run on both the PPCPowerbook and IntelMini, but the build on the PPC only works on the PPC. Here is the makefile stuff (again):

$(TARGET): $(OBJECTS)
g++ -arch i386 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk - o $@ -dynamiclib -install_name $(DESTDIR)/$@ $^
strip -x $@

%.o: %.cpp
g++ -arch i386 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk - c -O2 -o $@ $^ -I /System/Library/Frameworks/JavaVM.framework/Headers


Does anyone know if there is some way to dump the default compiler options during the build, so I can see what the compilers on each platform are doing? Like a -verbose option or something? I assume that when you invoke g++ with some options, there are a bunch more options that are used by default. I think I need to put all the options in my option list to force both compilers to produce exactly the same binary. I think some unseen default option is hanging me up.

BTW, the failure is a SIGSEGV that happens when I make a call into the JNI. It loads okay, but can't be called into.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden

This email sent to email@hidden


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.