[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gnustep-make experiment

From: Alex Perez
Subject: Re: gnustep-make experiment
Date: Wed, 07 Feb 2007 13:15:15 -0800
User-agent: Thunderbird 2.0pre (Windows/20070126)

Matt Rice wrote:
On 2007-01-24 22:05:26 -0800 Nicola Pero <address@hidden> wrote:

but my main problem with isn't actually technical at all,
its the very first thing potential developers are going to see, so will be the first impression, and imho gives the impression of being strange because it is uncommon for a build system to depend on environment variables to function.

I looked at your patch and I understand what you're trying to do ... it's good stuff and it's good to have this discussion, but let me first insist in claryfying something ... ;-)

The build system does not depend on at all.  We spent years
working on removing that dependency, and it's no longer there! :-)

It's not advertised much yet, but it will be clearly advertised in the release note of the forthcoming gnustep-make release. is obsolete in the default

You only need to set GNUSTEP_MAKEFILES and everything will work (assuming you have your tools in your path, and libs in your linker paths). This is all already implemented on trunk! :-)

Yes, but you still need to do something before running make, which is what this patch is
mostly about.

You only need to set GNUSTEP_MAKEFILES.  This is already on trunk!

Once that's clear, we can discuss the patch ;-)

I see two good ideas in the patch ...

1. I guess you are suggesting to put a makefile somewhere in the make search path and change all makefiles to include it so that you can compile without even setting GNUSTEP_MAKEFILES. I like the idea of not having to set any variable to compile,
but I also see a couple of obvious cons --

it would be more difficult
to switch between different gnustep-make installations (at the moment, you can easily
switch by just changing GNUSTEP_MAKEFILES!),

Not really, the patch allows you to switch installations by setting PKG_CONFIG_PATH and specifying --with-pkgconfig-path to configure to tell it where to put gnustep.pc.

The difference being instead of always having to configure it, configuration is made to
be something only people who need that behaviour have to do.

Sorry for being late to the party, but I've been busy...

Right, and also, frankly, there's a very important non-technical aspect to this as well; Way more developers know what the heck .pc files and pkg-config are, as well as how they work, than a funky GNUstep.conf file, which, while somewhat self-explanatory, definitely is proprietary. pkg-config is commonly used and makes things easier for us.

As we move towards a totally FHS-capable GNUstep, this is something which should be taken into account, IMHO.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]