Re: Autoconf & gnat Help Needed

[Warren <ve3wwg@gmail.com>]

Warren expounded in news:Xns9D6274A3FCC0CWarrensBlatherings@
188.40.43.245:

> Stephen Leake expounded in news:82sk6nn4vn.fsf@stephe-leake.org:
> 
>> Warren <ve3wwg@gmail.com> writes:
>> 
>>> Has anyone here had experience using GNAT with autoconf/automake?
...

Ok, I got this thang working together now, including
autoconf, automake and libtool. For anyone interested,
this is one way you can do it.

My executable is named z9. So in Makefile.am specify:

bin_PROGRAMS = z9

as per usual. I also build a static library containing 
all the related C/C++ modules (mine included a C++ main
program, thanks to ncurses).  So for the final target
specify something like:

z9$(EXEEXT): libz9.la 
   gnatmake $(AFLAGS) z9.adb
   gnatbind -n z9.ali
   libtool --mode=link --tag=CC gnatlink z9.ali --GCC=g++ \
       --LINK=g++ -L. -lz9 -lncurses -lpanel -o z9

The $(EXEEXT) is necessary for Cygwin builds.

File libz9.la is the surrogate for the static library of
C/C++ programs, which is listed as a dependency to
cause it to be created by libtool first. The
AFLAGS is just GNAT compile options, of the form:

DEBUG  = -g -O0
AFLAGS = $(DEBUG) -gnat05 -Wall -gnatwl ...

z9.adb was the starting point for my Ada code. It gets
invoked by the C++ main program. Specifying that, causes
all dependant Ada units to be compiled as usual by
gnatmake.

The libtool --mode=link is the tricky part:

You have to lie to libtool with --tag=CC (for C++) for 
a C++ build. 

I didn't try it, but presumably if you only have C 
modules, --tag=C will work (also remove "--GCC=g++" 
and "--LINK=g++" as well from the libtool command).

Then specify the entire rest of the gnatlink command line. 
libtool does however require that you explicitly specify 
the output file with the -o option ("-o z9", in this case).

Life is good, albeit a bit complex.

Warren