On Feb 26, 2007, at 18:58, Ryan Schmidt wrote:
You are right. This will not work on 10.3 simply because 10.3
installations are not capable of building universal binaries. I
have just added a warning (we could transform it into an error)
when the +universal variant is selected on machines where the
Universal SDK is not installed. This will cover machines running
10.3 and incomplete 10.4 installs.
What is the difference between a warning and an error? Are you
saying it just prints a message, then tries to continue? How could
it succeed if the universal SDK is not present?
Yes, it will try to continue. If the port is tailored in some way,
this may work even if the SDK isn't present, hence the warning. I
agree that it could have been made an error.
I realize that this code should be modified when Leopard will be
out, for example, we should not specify 10.4 universal SDK on
Leopard if all the libraries there are universal. But I can only
speculate for now.
I do not believe that any such changes would need to be made when
Leopard is out. Leopard should be able to run 10.4 universal
binaries. And we should continue to make 10.4 universal binaries
even when on Leopard, so that any universal binaries that were made
there will still run on 10.4. Are we setting
MACOSX_DEPLOYMENT_TARGET=10.4? If not, we should be.
Well, on Leopard we might accept to build universal binaries even if
the user did not install the universal binary SDK.
Paul
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-dev