[wx-dev] wxMac: Universal Binary question

Anders F Björklund afb at algonet.se
Wed Nov 15 03:01:32 PST 2006


jtgxbass wrote:

> Personally, I am having to do two builds:
> 1) PPC against 10.2 SDK
> 2) x86 against 10.4u SDK
> and then lipo.
>
> This is the only way I can see of creating wx lib that can be used by 
> my apps to run on plenty of OS X versions and architectures. So I have 
> never bothered with configures --enable-universal_binary switch.

Right, I instead did two different builds of my own application as 
well...
1) PPC against 10.1 SDK (probably need 10.2 for wxWidgets?), using GCC 
3.3
2) Fat against 10.4u SDK (requiring Mac OS X 10.4 to run), using GCC 
4.0.1

But if we want one single Universal Binary version of the wxWidgets 
library
that will run on earlier OS versions (not just on 10.4), that could 
probably
be built using two different SDKs and lipo'd together into one 
wx.framework ?

That is: not use --enable-universal_binary at all, as suggested 
earlier...

Not sure if mixing SDKs would lead to problems on Mac OS X 10.4, with 
the
PowerPC and Intel versions of one program now working differently, 
though ?
Or how one would separate two versions of the wx library, if that is 
needed.

i.e. have one version of wxWidgets that would be used to run the 
programs
using earlier SDKs, and one new version of wxWidgets that would be used 
to
run programs using the Universal SDK. And both of them installed at 
once.

For a system-wide installation that was, private installs will still 
work...


These are the issues that need to be adressed, before an "official" 
wxMac.
(and that will be done later, after the 2.8.0 release, if I understood 
it)
But for now, I am treating 10.1-10.3 and 10.4 as two different 
"platforms".

I'll upload some "unofficial" wxWidgets builds, when I build 
Code::Blocks...
--anders





More information about the wx-dev mailing list