how to cross compile?
domiman at gmail.com
Fri Apr 1 02:45:14 PDT 2011
I don't quite follow anyway. What do you want to compile for which target?
If you want to compile for ppc and are on intel (or other way round) you need all the needed stuff in the target arch as well. When you are on Snow Leopard and you want ppc, I don't think this works easily with macports anymore.
But there are other steps you can take, for example build all necessary things WITHOUT macports in another prefix with the desired arch. And then when you compile the software you have to make sure that you apply some magic to build it static.
Because doing it the macports way would mean you'd need to build it static anyway (or need to install macports+xcode on the target).
Pure xcode 3.x without ios support is < 1GB, btw. And that is for Snow Leopard only anyway.
For former OSX the xcode download is even smaller.
Am 01.04.2011 um 11:04 schrieb Chris Murphy <bugzilla at colorremedies.com>:
> On Apr 1, 2011, at 2:59 AM, Ryan Schmidt wrote:
>> Why don't you install Xcode and MacPorts on the machine you actually want to use this software on, and compile it there? That would be much simpler and more likely to succeed. MacPorts might be able to cross-compile, but that's not its primary purpose and that's not well-tested.
> I don't have regular access to the target machine. And I really don't want to download and install 4+GB of XCode to compile this dinky program, and then blow away XCode and Macports. It's pretty much not worth it. It's beyond irritating that there isn't already a binary for this somewhere. Bad enough Apple doesn't just include it.
> Chris Murphy
> macports-users mailing list
> macports-users at lists.macosforge.org
More information about the macports-users