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

["Nasser M. Abbasi" <nma@12000.org>]

On 7/29/2012 10:01 PM, Nasser M. Abbasi wrote:

> I can just write
>
>              gnatmake -I ...  *.adb
>
> from inside Makefile and that is all. It knows what files to compile
> as needed.
>

For completion's sake, and for future generations :), I thought
to show how I ended up doing a simple Makefile that uses gnatmake
to build a project.

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).

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
----------------------------

The FORCE trick above forces Make to invoke gnatmake each time. That is
OK, since gnatmake then decided if it needs to actually compile things
or not.

In the above example, `-I` just points to other folders that have Ada sources
that have packages with'ed by these files. (this is all normal gnatmake
stuff here).

So, all what one needs to do is

make

In the above, all output (exeutables and ali files and .o files are
generated in the same folder).

make clean

will clean everything. Now one can add more target to the Makefile
to do other things, like run a specific test, etc... i.e.
Normal Makefile things.

--Nasser