2013/5/16, Ludovic Courtès <[email protected]>: > > 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 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. The rest of packages is other history. Many of them only use: make & make install. Here "make" is "gnustep-make", And with the apps made with gnustep, as far as I remember, only GWorkspace uses ./configure. > > If that is the case, a good way to help with GNUstep packaging would be > to implement a ‘gnustep-build-system’ embodying GNUstep’s build system > idioms. That is a bit more involved, but I (or others here) can help. > > Thanks, > Ludo’. > Germán.
