[Top][All Lists]

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

Re: GNU Guix 0.2 released

From: Ludovic Courtès
Subject: Re: GNU Guix 0.2 released
Date: Fri, 17 May 2013 15:27:10 +0200
User-agent: Gnus/5.130005 (Ma Gnus v0.5) Emacs/24.3 (gnu/linux)

German Arias <address@hidden> skribis:

> 2013/5/16, Ludovic Courtès <address@hidden>:
>> IIRC GNUstep packages don’t use the GNU build system (./configure &&
>> make), but rather gnustep-make, right?
> The installation of gnustep packages (make, base, gui and back) is in the 
> normal
> way: ./configure, make & make install. The difference is that the last three
> packages use gnustep-make instead of GNU make. But depending of the
> configuration of gnustep's enviroment, the end user doesn't notice any
> difference.


> Because the name of gnustep-make tool is also "make". I don't know how the
> system can deal two tools named "make". But I think the trick is in
> the fact that
> gnustep's packages use GNUmakefiles instead of makefiles.

The two ‘make’ programs shouldn’t be a problem.  ‘gnustep-make’ just
needs to be added as an input, and it will appear before GNU make in

> The only difference is that if the system don't know about the gnustep
> tools. The
> user will need run the gnustep script, something like ".
> /usr/.../GNUstep.sh", to set
> up the variables of gnustep environment.

What do you mean with “doesn’t know about the GNUstep tools”?  When is
it necessary to source that script?  What are the variables to be

Guix has a mechanism to automatically define search path variables:


Would that be of any help?

> The rest of packages is other history. Many of them only use: make &
> make install.
> Here "make" is "gnustep-make",

For those, it may make sense to implement a specific build system that
automatically adds ‘gnustep-make’ as an input and runs the right


reply via email to

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