mike burrell wrote: > > - first, why on earth are the source files named instead of the object > names? make is dependency-based and it would seem much more logical to give GNUmakefiles will eventually tend to be generated automatically from a ProjectBuilder-like program. Here the user would just enter in the source files he was using, then ProjectBuilder would manage them as well as creating makefiles, etc. It's also the way Apple does it, so we wan't to be at least somewhat compatible. > - what would be an easy way to extend the rules and variables set? e.g. > right now i have something like this: You can add any additional rules you like either in the GNUmakefile or in a Makefile.postamble (which you would include in GNUmakefile) > > - which variables should i be using for CFLAGS and whatnot? there seems to > be a myriad of _CFLAGS variables defined in the GNUstep makefiles and i'm > not sure which ones i should or should not append in order to add special > flags (such as profiling flags) For personal CFLAGS (or other variables), prepend 'ADDITIONAL_' to the name: ADDITIONAL_CPPFLAGS ADDITIONAL_OBJCFLAGS ADDITIONAL_CFLAGS ADDITIONAL_INCLUDE_DIRS ( for profiling, try just "make profile=yes") See some of the examples in the Testing directory, for instance. Also look at the docs at http://www.gnustep.org/resources/documentation.html
