[wx-dev] Creating a MacOS X Framework

Vadim Zeitlin vadim at wxwindows.org
Mon Mar 5 09:34:55 PST 2007


On Mon, 5 Mar 2007 10:11:25 +0100 Anders F Björklund <afb at algonet.se> wrote:

AFB> >  Maybe this is a stupid question but what's the point of using Xcode  
AFB> > for something like that? Wouldn't it be more convenient (and,
AFB> > importantly,  much more amenable to automation) to use a simple
AFB> > makefile?
AFB> 
AFB> I think that most people on Mac use Xcode rather than Make, and those  
AFB> that use autoconf/make probably want the UNIX libraries rather than  
AFB> frameworks.

 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 ;-)

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?

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.

AFB> >  You'd also probably need to symlink some other things, e.g. wxstd.mo  
AFB> > and wxwin.m4.
AFB> 
AFB> Then again, if you want to support those you probably want UNIX install  

 I could be wrong but I thought that we'd distribute *only* the framework
for OS X. And so it should include everything necessary for both Xcode
builds using framework as such and for command line builds. Maybe this is
impossible for some reason but if it is indeed possible then I'd really
prefer to do it like this. Having one distribution is always better than 2.

AFB> And it would probably require the build scripts and Xcode templates
AFB> and other things to be written first, before it being considered ?

 Well, what do you mean by "being considered"? We consider it right now, by
discussing it, but to be useful it would indeed have to be written... I'm
afraid I might be missing the real point of this question.

AFB> But maybe 2.8.2 should have a /usr/local Installer, rather than a
AFB> /Library/Frameworks/wx.framework ? Either way "works", your call...

 Sorry again but this is unclear to me as well.

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

 Regards,
VZ





More information about the wx-dev mailing list