[wx-dev] Creating a MacOS X Framework

[Anders F Björklund]

Etienne Samson wrote:

>> And it's a main reason why we are porting Code::Blocks IDE to Mac OS 
>> X.
>> Sure, Xcode is a lot nicer. But it's not cross-platform, and not Free.
> Porting Code::Blocks was also a thing I tried, but they didn't have at 
> least a Xcode project file, so I started by creating a wx.framework...

Code::Blocks is either built using autoconf/make, or bootstrapped using 
CB.
Haven't felt the need to build one open IDE using another proprietary 
IDE... :-)

Binaries at 
http://developer.berlios.de/project/showfiles.php?group_id=5358

> That's the way I had done it, before I was told that wx-config was 
> needed...

I think it was me that told you that, but I meant it more like "nice to 
have".
Just like wx-config is nice to have on the Windows platform. But not 
"needed".

<off-topic>
SDL uses sdl-config like that. Either you build it UNIX-style, and then 
you
get a sdl-config in bin. Or you use the SDL.framework, and Xcode 
templates:
Then you don't get any sdl-config program, and you don't get a 
libSDLmain.a
Instead you copy the settings and source code over to each and every 
project.

I thought that supplying a "sdl-config" with the SDL.framework would 
have
been nice, but apparently no-one uses Terminal and Framework 
simultaneously.
i.e. either you have a UNIX install and then you use configure scripts,
or you have a Framework install and then you use the Xcode IDE 
templates.
</off-topic>

Again, if it makes your life complicated then just ignore wx-config etc.
in the framework - and just include the Headers and the shared library ?
Rather have two distributions available, than none because of arguments.
Mac binary distribution is getting delayed for wx 2.10 anyway, it seems.

Originally I thought it was a good idea to combine the two into one,
since it's the same compiler anyway. But now I am not so sure anymore.
Seems like everyone is linking wxWidgets statically on Mac, anyway...
(or just including their own custom shared libraries with their program)

>> Usually this is done by providing Xcode template projects, to start 
>> from.
>> (or you can use wx-config and copy-and-paste, which also sort of 
>> works...)
> But if done in setup.h, you don't even need a template ;-)

But you'd still have to add the wx.framework and set up matching 
compilers ?
Anyway, changing "setup.h" is a bigger change than just doing a 
framework...
All I know is that if you use e.g. Visual Studio I think you have to 
add the
__WXMSW__ macro manually, so I figured the same would apply to using 
Xcode.

The real interesting things happen when we start getting *two* different
wx.framework, one using wxMac and Carbon and one using wxCocoa and 
Cocoa.
Or when you want to include the wx add-ons from "contrib" or from 
wxCode,
like wxSTC or wxStEdit. Should those be separate frameworks ? Or 
included ?

--anders