Martin Kalbfuß a écrit :
Thanks,
unit path is the option I was looking for. I have a C background. But I forgot to mention that this is a library. So there's no main file. And the C part is needed to make some C macros and defines visible. It's a wrapper for the brand new allegro library. The keytypes are a long list of key names needed in two places. I decided to separate and include it. .I'm aware of --automake, and It makes the process much easier. But it's far to weak to replace a Makefile.
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)
Indeed, automake is used only to compile pascal programs, taking care of dependencies (including those to C functions and libraries). This is possible because all needed information is contained in the sources, if properly written (except some directory information, whence the --unit-path= ...) Notice that the gp utility takes care of cleaning via the two options --clean (cleans all) and --clean-objects (all except the executable), so that you do not have to bother to gather dependencies both in compiling and in cleaning.
Maurice