While I personally don't have any experience using either... automake and autoconf would be the best possible solution here.
(Edwin commented in this as well) -----Original Message----- From: Michael Gerner Andreasen [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 31, 2002 6:22 AM To: rom list Subject: Re: Combined Makefiles Yep you are right about the depend stuff, but i havent finished the makefile at all lotsa nice stuff gona be in it, includeing dep. you dont like my *.c why the hell not? you include all wierd stuff in your src directory? i tend to use a few directorys /cooker -> cooker includes 3 directorys for each of my co. coders, it is out playground. /testing -> here we test the completed work from the different coders. /stable -> the actual mud running, no src only exe and what not. /backup -> well here we keep all oldere stable code. and i never put blabla.c in my src unless i knows it should be there, i almost never compiles, unless i think what i made is finished, if it breaks, so what, i leave the shell get on it again a few hours or days latere, and then finishes it up put the changes in the testing directory for the others to playwith, find bugs i dident, and optimize it if thay want to. i just tested the make my self on a few boxes: solaris, freebsd, openbsd, redhat 7.3, redhat 7.2, redhat 5.0, slackware 3.4, slackware 8.0, debian 2.2r6 and r7 3.0r0 as soon as isos are down, so to me it looks like it work, it saved me 4 files from my directory, and i know it is annoying to type make +little more but it works, and i dont have to play with my makefiles thatmuch anymore. everytime i include a file i have to play with all of em, so i like this way bettere. -- ROM mailing list [email protected] http://www.rom.org/cgi-bin/mailman/listinfo/rom
