On Sun, 30 Jun 2002 19:19:18 +0200 (CEST) Thomas Finneid <[EMAIL PROTECTED]> wrote:
TF> The problem I am having is that M comes with miscellaneous .in files and TF> such and it does'nt create Makefiles when run, it just creates the links to TF> the make files. I've never understood why this has been done like this and the configure code author (Greg Noel) never explained it to me, unfortunately. But this doesn't have anything to do with the question at hand: it's just a way of "emulating" VPATH support. TF> So how does any options given in the command line to configure affect TF> its compilation. The only thing I can see that can perhaps make a TF> difference is makeopts.in. That's it. It is included by the Makefiles and contains all configure definitions. This is, actually, a good idea, i.e. it's IMHO much better than the usual approach of generating the Makefiles because like this Makefiles are fully static and all detected stuff is in one place. TF> Any pointers would be appreciated. Look at the various Names.mk files, they're fundamental for this build system. Regards, VZ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
