Compilers and universal flag

vincent habchi vince at macports.org
Sun May 13 06:51:27 PDT 2012


Josh,

On 13 mai 2012, at 15:38, Joshua Root <jmr at macports.org> wrote:

> nobody bothered making gcc4x build truly universal. The universal variant just enables multilib.
> 
> What you suggest amounts to distinguishing between host and target archs, and thus also distinguishing between ports that even have target archs (i.e. compilers and toolchains) and those that don't.

Precisely. For those ports, + universal would just mean “build a tool that can produce universal apps”, whereas we would use another flag to specify “build a universal tool”. Is that so complex?

> Then you'd have to be able to specify whether each dependent wants the compiler to build it or to use the compiler to build something else, and match up host->target or target->target as appropriate.

What do you mean?

Vincent




More information about the macports-dev mailing list