[wx-dev] Creating a MacOS X Framework

Vadim Zeitlin vadim at wxwindows.org
Sun Mar 4 11:32:33 PST 2007


On Wed, 28 Feb 2007 11:51:50 +0100 Etienne Samson <samson.etienne at gmail.com> wrote:

ES> I'm still tinkering with this idea in order to have a less annoying  
ES> way of using wx for MacOS X developers ;-)
ES> What do you think of this approach :
ES> - Select from a list of Targets :
ES> 	- Framework Debug Unicode
ES> 	- Framework Release Unicode
ES> 	- Framework Debug ANSI
ES> 	- Framework Release ANSI
ES> - Make Xcode project run configure to create setup.h files and wx- 
ES> config files (by passing configure correct arguments).

 Maybe this is a stupid question but what's the point of using Xcode for
something like that? Wouldn't it be more convenient (and, importantly, much
more amenable to automation) to use a simple makefile?

ES> 	What I use currently is configure --enable-mac --enable-monolitic- 
ES> with-expat=builtin --with-regex=builtin --with-zlib=builtin

 Why --enable-monolithic?

ES> - Bundle all this in a framework like this :
ES> wx.framework/
ES> 	Commands -> Versions/Current/Commands
ES> 	Headers -> Versions/Current/Headers
ES> 	Home -> Versions/Current/Home
ES> 	Resources -> Versions/Current/Resources
ES> 	wx -> Versions/Current/wx
ES> 	Versions/
ES> 		Current -> 2.8
ES> 		2.8/
ES> 			Commands/
ES> 				(Here files would be copied depending on the target chosen)
ES> 				wx-config -> (eg.) ./inplace-mac-ansi-debug-2.8
ES> 				inplace-mac-ansi-debug-2.8
ES> 				mac-ansi-debug-2.8
ES> 				OR
ES> 				inplace-mac-unicode-debug-2.8
ES> 				mac-unicode-debug-2.8
ES> 				OR
ES> 				inplace-mac-ansi-release-2.8
ES> 				mac-ansi-release-2.8
ES> 				OR
ES> 				inplace-mac-unicode-release-2.8
ES> 				mac-unicode-release-2.8
ES> 			Headers
ES> 				(all wx headers, including the generated setup.h)
ES> 				wx -> ../Headers
ES> 			Home/

 Why is this called "Home"??

ES> 				bin -> ../Commands
ES> 				include -> ../Headers
ES> 				lib -> ..
ES> 				share/aclocal/
ES> 					wxwin.m4
ES> 			Resources
ES> 				Info.plist
ES> 				wxmac.icns
ES> 			wx*
ES> 
ES> I could then make an installer putting the wx.framework in /Library/ 
ES> Framework and symlinking /usr/local/bin/wx-config to /Library/ 
ES> Frameworks/wx.framework/Commands/wx-config.

 You'd also probably need to symlink some other things, e.g. wxstd.mo and
wxwin.m4.

ES> I would like to know if this fits everybody...

 I think this is exactly what needs to be done.

 Thanks,
VZ





More information about the wx-dev mailing list