[wx-dev] Creating a MacOS X Framework

[Stefan Csomor]

Hi

>  I agree that people _using_ the framework would use Xcode. But
> normal
> users like this won't need to build the framework if we distribute
> the
> official version of it. And for us it's more convenient to be able to
> build
> it remotely and so using command line tools is more convenient (as
> usual ;-)

xcodebuild would be the command line tool to build a target in a xcode
project from the command line

> AFB> It would be a good thing if both the Xcode projects and the
> AFB> autoconf/make built the same libraries
> 
>  This is absolutely required, indeed. Isn't it the case already?

the xcode projects are using an include file to get predefined
"configure" values (xcode_config.h) to make sure that we can always make
sure that the binary runs on the lowest supported platform, wherever you
build it.

> AFB> Even nicer would be if the Xcode projects could be generated
> AFB> automatically, but that would first require a major new feature
> for
> AFB> Bakefile - though  great.
> 
>  Yes, Xcode backend is sorely lacking. But it's another topic.

+100

>  In any case, this framework-ization of wx should be done in cvs
> HEAD, at
> least initially, and not for 2.8.2.

definitely yes, we also have to make sure that the boundaries against
things like wxPython are properly set up, including versioning

Thanks,

Stefan