Will binaries built in 10.6 still run in 10.5?
domiman at gmail.com
Mon Oct 4 11:37:46 PDT 2010
I do distribute a snapshot for our project. With the help of macports I ironed out the problems in building the snapshot.
THEN I made three prefixes in /opt for each arch (ppc, 386, x86_64), building all necessary things WITHOUT macports for each arch (autoconf, libtool, sdl, ogg, vorbis, zlib...).
Then I build our project as well for each arch, making necessary changes for the path etc... After it is built I lipo the different arches into one binary and then make the app and dmg file. All this, concerning building our project, is done via a script. If you want I can attach this in a follow up (once our blackout is over).
This way you avoid problems and you don't need to include xorg stuff for example (which default macports installs of sdl pull in, for example).
Am 04.10.2010 um 20:26 schrieb Michael_google gmail_Gersten <keybounce at gmail.com>:
>> Distributing binaries built via MacPorts tends to be a bad idea: not only
>> do you need to make sure to distribute the files from any dependencies as
>> well as your binary, but the result will likely interfere with an installed
>> MacPorts or Fink on the installer's machine.
> What is a good way to build stuff for distribution?
> More specifically, lets say my goal is to build something universal,
> package it up, including any frameworks or libraries needed, and make
> it something that can be safely distributed?
> Right now, there's one package I'm trying to work on that does this,
> and it uses a very non-trivial script to do a lot of otool
> modifications to library and framework paths as it builds the dmg.
> Political and economic blog of a strict constitutionalist
> macports-users mailing list
> macports-users at lists.macosforge.org
More information about the macports-users