[Gtkradiant] Re: Patch work for FreeBSD native build
Fri, 20 Sep 2002 09:40:03 +0200
The scons build is scheduled for 1.3 afaik? You have worked on BSD
compatibility on the 1.2 tree.
Configuration with scons is one of the hot items, it has not been
written/standardized in scons at this point, but the scons developers
agree that we have a strong need for it. When we reach the configuration
issue in scons, I will probably want to be involved in the design, since I
worked on the scons config design already (see scons-devel mailing list).
As for 1.2 + BSD + cons build, we can get away with some simple perl and
config checks. I'd suggest you produce a patch with #define __nix__ and
globals for the config- stuff. You don't need to write the code to decide
between glib-config and glib12-config at this point, it can be done later
on while I integrate your patch.
On Thu, 19 Sep 2002 23:58:35 -0400
"Lyndon Griffin" <firstname.lastname@example.org> wrote:
> TTimo squawked:
> > I just started looking at the patch.
> > The first problem I have right now is the glib12-config
> > my system is using glib-config and doesn't have a glib12-config
> This can easily be addressed in the work I'm doing with scons. Between
> scons and python, it is trivial to search for an executable in the search
> path, and only marginally more difficult to guess - I can setup the
> SConstruct to search for a few key executables and locations. This piece I
> have prototyped with a shell script, which will locate the correct
> (glib|gtk|xml)-config executables, and furthermore pull version information
> from them to determine if the installed version meets the build
> If I get a solid hour or two this weekend, I will post an initial scons
> build system as an attachment to bug 531
> (http://zerowing.idsoftware.com/bugzilla/show_bug.cgi?id=531), predicated on
> me doing the above work first.
> If anyone's interested, I have a great deal of this work already done and
> available at http://bsd4us.org/GtkRadiant/SConstruct.html - note that this
> work is being done on the trunk only.
> As for the FreeBSD stuff, Timothee and I had a brief chat today about
> genericizing (is that a word?) all the #defines for Linux, MacOS X, FreeBSD,
> and potential future ports into something along the lines of #define __nix__
> or something similar. This should be a pretty quick hit, as I already have
> 1.2 and 1.3 devel trees set up on both Linux and FreeBSD, and I've
> "prettied" the existing #define stuff as part of my FreeBSD changes. I
> believe this proposed work dovetails nicely into this bug, though it may
> make more sense to do this in the trunk (and create a new bug er um
> <:) Lyndon
> Gtkradiant mailing list