Independence from (g)make

[Adriaan de Groot]

On Wednesday 17 April 2002 18:17, Michael Matz wrote:
> On Wed, 17 Apr 2002, Adriaan de Groot wrote:
> > The shell-commands used in Makefile.common are *huge* and complicated.
> Of course this will not change by moving them to other files (except the
> final ";\" and the $$'s, but a coloring editor does wonders).

Agreed, but the ability to put comments in the scripts might make them a 
little more palatable.

> I'm not that sure I want to have 10 more files in admin/.  Probably you
> can put them all into one script (POSIX knows shell functions!), and
> delegate the work depending on an argument.  This OTOH is something I
> would like.

I kinda like that idea. It may allow a little code to get factored out, though 
I suppose the targets are sufficiently different as to share little code. 
I'll get on it and see what happens on my home system.

> > For example, the cvs target has a shell command that is 96 lines long.
> Incorrect.  It has _multiple_ shell commands, the longest (the second last

I *knew* someone understood this thing. I looks to me as though 
kde_module_name is set unnecessarily at the beginning, among other 
weirdnesses. Anyway, that'll come out in the wash.


> > With that done, very little is needed to make the whole KDE build system
> > work with BSD make: a configure check to output the correct include
> > directive in Makefiles,
>
> You mean for depfiles, right?  Which automake version are you using?
> automake 2.5x supports GNU and BSD make already.

I've been ignoring the "automake 2.13 is deprecated" message for a few weeks 
now, I guess it's really time to change.


Patches forthcoming.

[ade]