Independence from (g)make

[Stephan Kulow]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mittwoch, 17. April 2002 17:23, Adriaan de Groot wrote:
> We FreeBSD studs^Wweenies^Wpeople have BSD make (make) as opposed to GNU
> make (gmake);  while it is possible to install and use gmake, some of us
> would prefer to use the original BSD make. There's several steps involved
> in getting that far. The first thing I'd like to do is clean up
> Makefile.common in admin/. What's that mean?
>
> The shell-commands used in Makefile.common are *huge* and complicated.
> Some variables need to be set and passed on through a number of shell
> commands, there are complicated statements, and some perl code as well.
> I'd like to move those shell commands to separate shell scripts in admin/
> For example, the cvs target has a shell command that is 96 lines long. As
> a shell script we could lose all the ;\, add comments explaining what is
> going on, and in general make it more maintainable. Oh, and support BSD
> make better because BSD make doesn't like these really long commands.
>
> The shell-command for the cvs target in Makefile.common could then be:
>
> 	MAKE=$(MAKE) $(SHELL) admin/cvs.sh
>
> 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, (Lauri already has one) and some fixes to
> Makefile.am's which have backslash-continued comments. And a similar fix
> for the DEP_FILES comment which shows up everywhere, which also has a
> backslash-continued comment.
>
Hmm, what are the correct include directives? The cvs.sh thing is no big 
problem to me. But I'd like to see patches first.

Greetings, Stephan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8va3twFSBhlBjoJYRAt4DAKDiEjmpSYsud5nX5BL8NGBvro9VkACgig/+
se6VbwgN/z6O+KSeGfpmT10=
=Mog9
-----END PGP SIGNATURE-----