Re: How to supply O/S linker arguments with gprbuild?

[Simon Wright <simon@pushface.org>]

"Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:

> On 22/06/2020 22:43, Simon Wright wrote:
>> "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:
>>
>>> Another idea to consider would be to ditch makefiles. gprbuild does
>>> everything makefiles do and better and more.
>>
>> Almost everything! except determining which OS you're running under, or
>> building project documentation, or ...
>
> Are you sure that make has OS macro defined? [It would be great to
> have host OS/architecture + target OS/architecture attributes in
> gpr. I do not understand why gpruild still does not have them.]

The first page of Gnoga's Makefile has

   ifeq ($(strip $(findstring darwin, $(TARGET))),darwin)
           PRJ_TARGET=OSX
   else
   ifeq ($(strip $(findstring mingw32, $(TARGET))),mingw32)
           PRJ_TARGET=Windows
   else
   etc etc etc

but I agree it'd be much better to have something built-in. The internal
mechanisms of gprconfig would support this kind of thing, in fact they
already do because of knowing hw to build .so/.dll/.dylib depending in
OS, I wonder whether we could surface that?

> Isn't there the package Documentation in grpbuild? [I must admit I
> never used it because I believe documentation must be written, not
> built.]

I just had a look at this, it works on @param-style comments (and, in
the CE 2019 version anyway, goes away and builds "documentation" for all
the withed units from eg GNATCOLL unless you tell it
--no-subprojects. I'd have expected that to be the default.)

> If you rather mean project cross reference GPS does the job to me.

I use Emacs ada-mode, but yes.