iOS cross compiling support

James Gregurich bayoubengal at
Fri Jan 28 18:28:57 PST 2011

oh. you're right about that. I'm just adding it to be thorough and consistent. I have a symmetry with respect to my variables set up between "target" and "host" that I preserve if it makes sense to do so....whether or not it might actually be needed in practical terms. I think that is a useful policy when designing APIs.

At any rate, I have it coded to manually use "apple" since compatibility with other systems isn't a requirement. 

Right now, I'm trying to figure out why configure_main is suddenly not being invoked. I broke something in the bowels I suppose. Once I get that fixed, I can submit this work for review....unless some other bug pops up.


On Jan 28, 2011, at 6:06 PM, Joshua Root wrote:

> On 2011-1-29 11:52 , James Gregurich wrote:
>>> Looking back through the thread, I don't see an explanation of why you
>>> need to figure out the build system's triplet yourself. Configure
>>> scripts will typically come with a copy of config.guess and figure it
>>> out on their own.
>> How would config.guess know what the target hardware/os is for an iOS device given it doesn't run on the iOS device? building icu for iOS requires that you pass --host=arm-apple-darwin to the configure script.
> Of course it can't guess what the host machine is going to be, you have
> to set that explicitly. But you seemed to be wanting to do that for the
> build machine (at least that seemed to be what all that talk of using
> base's config.guess and/or the os.* variables was about), which is
> unnecessary.
> - Josh

More information about the macports-dev mailing list