Martin Kalbfuà wrote:
I'm aware of --automake, and It makes the process much easier. But it's far to weak to replace a Makefile.
--automake and the gp utility are not meant to replace a Makefile. (gp is meant to replace --automake, though.)
Maybe some of the following things are wrong(hopefully):
- no install target
- no clean target
- no support for building documentation
- no dependency checking. (In my case allegro-4.9 for the examples)
Except for clean with gp, as Maurice mentioned, that's right.
Indeed, it may be useful to call gp from a Makefile, while the Makefile does the rest (dependencies, documentation, install). That's what I do in some of my projects where I, e.g., need to build documentation.
What's the way to go, when you like to release a library? For C I would use autotools and pkg-config. And I think It would be nice if there are going to be some macros for the use with autotools like an AC_PROG_CC equivalent AC_PROG_GPC which checks for the gpc compiler.
I'm not aware of such macros, but if you're familiar with autoconf, it should not be too difficult to write them. (I've worked on the autoconf for the GPC Run Time System, but I've never really liked it too much, and it was some years ago, so I'm not actually that familiar with it at the moment, I'm afraid ...)
Frank