Re: how to tell gnatmake to send executables to a different directory when compiling multi source?

[Robert A Duff <bobduff@shell01.TheWorld.com>]

"Nasser M. Abbasi" <nma@12000.org> writes:

> Make is only used here as a 'wrapper' around gnatmake. gnatmake is
> the one doing the real work. Only reason to use Make is really just
> so that to avoid using bash scripts and to also allow recusrive make
> to work (so that I can write make from the top of the tree and
> have things build).

The make file you show below looks perfectly reasonable to me.
It's simple, and is not recursive.  If you don't want to waste
time learning gnatmake/gprbuild/project files, and you don't
need that functionality, this is a reasonable approach.

But I don't understand your reference to "recursive make" above.
You don't need recursive make in order to do "make" from the top
of the tree and build everything.  If your Ada files are scattered
all over a bunch of subdirectories, you can just mention those
directories with the -I switch.  If you have C files mixed in,
that doesn't change things -- you still don't need recursive
make.

This make file doesn't put the executables where you wanted them,
but it's not hard to write some rules that will copy or move them,
or create links.

But I advise you to not let your make files get complicated,
and try to avoid recursive make.  The paper somebody mentioned
explains why recursive make causes trouble, and why you don't
need it.

> Here is a simple example. Assume you have a folder with 2 main files
> (main1.adb and main2.adb) and want to build them, and they depend on
> other ada packages in another folder(s).
>
> Then put this Makefile in the folder with the main ada files
>
> --------------------------------------
> EXECUTABLE=main1 main2
>
> .PHONY: all
> all: ${EXECUTABLE}
>
> .PHONY: FORCE
>
> ${EXECUTABLE}: FORCE
> 	gnatmake  -I../binding $@.adb -largs -L/usr/lib -lblas -llapack
>
> FORCE:
>
> clean:
> 	-rm ${EXECUTABLE}
> 	-rm *.ali
> 	-rm *.o
> ----------------------------

- Bob