On Jan 22, 2013, at 11:40 PM, Steffen Gutmann <muib...@yahoo.com> wrote:
>> For glib, write a bug in bugzilla.gnome.org and attach your patch, after >> fixing > >> it up to conform to Gnome's patch standard [1]. For libffi, the author uses >> Github [2], so he probably wants you to fork and make a pull request. > > Ok, I will try that after resolving the issue below. > >> However, what bothers me about this is that both packages compile just fine >> when >> building a one-off on the processor in question, so the issue should be >> cross-compilation (usually done by querying the "build" configure >> parameter). I don't see that in your changes, so what am I missing? > > Well, probably I am not doing the right thing as I don't know, really, how to > use the "build" parameter. Any pointers I could look into? And would that > mean that a module is build twice (once for each architecture) and the sort > of merged into one universal binary? I kinda like the way it works now with > the -arch keyword twice on the command line and the compiler going over the > source files twice, and the result automatically being assembled in a single > binary, Sorry, I don't have time today for a proper answer, but http://www.sourceware.org/autobook/autobook/autobook_258.html#SEC258 will get you started. The universal module runs those packages which need it twice and lipos them together. I think https://developer.apple.com/library/mac/#documentation/Porting/Conceptual/PortingUnix/compiling/compiling.html talks about the process, but you can also look at setup_universal() in .jhbuild and read the man page for lipo. Regards, John Ralls _______________________________________________ Gtk-osx-users-list mailing list Gtk-osx-users-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-osx-users-list
