[wx-dev] wxMac: PMSetDuplex not in 10.3
David Elliott
dfe at cox.net
Mon Sep 17 09:24:22 PDT 2007
On Sep 17, 2007, at 12:05 PM, Julian Smart wrote:
> Hi David,
>
> Thanks for the explanations - unfortunately I'm failing to build a
> mental model of all this even after reading your message several
> times. But it seems the end result is that Apple has made it
> impossible for us to use --enable-universal_binary without jumping
> through a lot of hoops. How the average cross-platform developer
> will navigate this I don't know, but I hope it's eventually possible
> to have configure/your scripts take care of it (but what about
> people's apps? They'll have to rewrite their makefiles.)
>
Apparently not...
I can successfully specify --with-macosx-version-min=10.3 --enable-
universal_binary=/Developer/SDKs/MacOSX10.4u.sdk
Therefore, I think perhaps the best thing to do is to by default go
with 10.3 whenever an SDK is specified either with --enable-
universal_binary or --with-macosx-sdk. That makes the code simpler
anyway as I don't need to check the SDK for its suggested version I
can just use the minimum version we support.
Does anyone have a problem with this?
> Very very depressing. Fortunately for me I'm not going to upgrade to
> Leopard any time soon and I can only hope the situation will
> improve... somehow... It seems Apple are twisting the knife and
> making a complicated situation worse.
>
Not really, it seems that I was simply wrong about not being able to
use 10.3 on x86 builds. The only downside is that I suspect it will
cause certain symbols to be weak linked when it is not necessary since
there are no x86 10.3 libraries that anyone could possibly run them
against. But that's probably not a major problem.
-Dave
More information about the wx-dev
mailing list