[wx-dev] Creating a MacOS X Framework
Anders F Björklund
afb at algonet.se
Tue Mar 6 03:18:30 PST 2007
Etienne Samson wrote:
> It differs because configure regenerate a setup.h file, while Xcode
> use the old setup0.h file, which include a config_xcode.h file, which
> dates back from 2.7.1 (still in HEAD)...
> So thought it would be better to use configure to generate the setup.h
> file and use Xcode's bundling capabilities to get what I want...
Might as well not use Xcode at all, in that case... Bundling isn't hard
?
That is: why not use configure / make to build the wx.framework as well
?
Mixing and matching and running ./configure automagically seems even
more
awkward than requiring the users to learn about configure and wx-config
?
> Right, this is not unreasonable, but currently, the Xcode project
> feels wrong (I'm talking about this strange 2.7.1 config_xcode.h
> file). Anyway, until Bakefile support .xcodeproj generation, I think
> Xcode is a necessary step to provide binaries for OSX.
I think wxWidgets should continue to support both Xcode & autoconf+make.
Frameworks and Application bundles don't change this, just complicate
it.
I had more thought of it as adding a new "framework" target to Make,
and a
"framework" target to Xcode than changing the old ones or any
requirements.
--anders
More information about the wx-dev
mailing list