Re: [XaraXtreme-dev] Building resources udner xcode

[Phil Martin <Phil@xxxxxxxx>]

It sounds good in principle - no trouble using gnu make, perl and  
shell script. The trouble is that, so far at least, the xcode  
projects (wxWidgets and XaraLX) do not need or use the auto-tools in  
any way. They use the raw source code and their build configuration  
settings are bound into the project files.

So, while a build stage that simply issues a make command is very  
attractive, it's less so if the makefile has to be created by  
autoconf. Would the resources makefile need to be reconfigured for  
different platforms?

I want to make the xcode project as simple as possible to set up and  
use. I realise this may not be possible but in an ideal world I'd  
like to be able to deliver a single package containing source code  
and xcode project file(s) onto a vanilla Mac and have it build simply  
by loading the project and clicking "Build". (Admittedly there are  
various things that foil that ideal already, not least bound-in file  
locations - I need autoconf! ARGHHH...)

Phil

On 25 Apr 2006, at 10:40, Alex Bligh wrote:

> Phil,
>
> --On 25 April 2006 08:31 +0100 Phil Martin <phil@xxxxxxxx> wrote:
>
> > The xcode project I'm pulling together initially links using
> > winresources.cpp but I'd rather it used the "proper" resources  
> > system.
> > I'm looking at the makefile targets below "#RESOURCES MAKE SYSTEM" in
> > wxOil/makefile.am and considering converting that makefile code  
> > into a
> > "Run Script" build phase in xcode (i.e. a shell script). I've already
> > done this kind of thing in a smaller way with the svnversion.h  
> > target but
> > this is a much more complex beastie.
> >
> > Got any comments/suggestions before I start?
> >
> > For any macdevs reading this, I propose to create a separate  
> > target just
> > to perform the resources build phase and then make the LX target  
> > depend
> > on it.
>
> Well one approach which might suit all concerned would be to strip
> it out from wxOil/Makefile.am completely, and put it in
> wxOil/xrc/Makefile.am. We could even put resources.cpp there as well.
> Then (assuming you do have gnu make and perl installed) your script
> could simply do something like "make -C wxOil/xrc" and (if you like)
> copy wxOil/xrc/resources.cpp (it would have moved, remember) to
> wxOil/winresources.cpp.
>
> This would simply the makefiles rather, and leave the resources
> stuff in their own place. It would also make moving to bakefile etc.
> rather easier if we ever wanted to do that.
>
> WDYT?
>
> Alex