Hi Daniel,
> For most platforms and builds we can't tell which builds that use GNU
> make,
> thus we must avoid all GNU extensions except for the rare case wheres we
> know
> GNU make is used (and I can't name even name one such right now).
I can for sure name these: mingw32, netware, djp; and probably also risos from what it looks in the makefile;
so non-gnu are the minority: borland and vc;

> I'm a bit old school on this. I don't consider this suggestion much of an
> improvement. Instead of explicitly mention all the source files, this
> hides
> what files that are used and makes it impossible to add local test files
> with
> .c extensions (without having them built and included in libcurl).
ok, that convinces me.

so then another approach which would at least eleminate further maintainance with the those platforms I mentioned above:

I've copied the part from Makefile.am containing the HHEADERS and CSOURCES section into a separate file 'files.inc', and then do a 'include files.inc' from my Makefile; I've also tried to directly include the whole Makefile.am, but unfortunately there broke something with a line, have not tracked that down yet....
so this would be usable with mingw32, netware, djp for sure, and perhaps riscos.

the question is then if we check files.inc into CVS, and you generate only a new one out of Makefile.am when something changed? I think that would be simplest...

Guenter.
Received on 2004-07-02