Re: Upgrading GNAT GPS 5.0 -> 5.3

[Simon Wright <simon@pushface.org>]

Victor Porton <porton@narod.ru> writes:

> Dmitry A. Kazakov wrote:
>
>> On Thu, 14 Aug 2014 18:59:48 +0300, Victor Porton wrote:

>>> But if I wanted to add linker option -lraptor2 to a non-library project,
>>> what I would need to do?
>> 
>> You never need that for a library. However, you were already answered in
>> this thread how to do this:
>> 
>> project Messy_Client is
>>    ...
>>    package Linker is
>>       for Default_Switches ("ada") use ("-L<some-path>", "-lraptor2");
>>    end Linker;
>> 
>> end Messy_Client;
>
> In GNAT GPS 5.3 this works only if Messy_Client is a library project (and 
> with Linker_Options instead of Default_Switches).
>
> IN GNAT 5.0 it worked for non-library projects also.
>
> It looks like a bug in GNAT GPS 5.3.

Could you please run
   gprbuild --version
on the command line and tell us the version it reports.

For example, here I get

   $ gprbuild --version
   GPRBUILD GPL 2014 (20140331) (x86_64-apple-darwin13) 

and I added

   package Linker is
      for Default_Switches ("ada") use ("-lraptor2");
   end Linker;

to an existing non-library project. I don't have libraptor2, so this
failed to link, but the switch was copied through correctly:

   gcc test-main.o -lraptor2 -L/usr/lib -ltk8.5 -ltcl8.5 -o test-main
   ld: library not found for -lraptor2
 
>>> Many non-library projects need to link to libraries.
>> 
>> They should *always* use library projects instead of linking directly to
>> external libraries.
>
> Why?!
>
> It is completely legit for a non-library project to link to a C
> library directly to obtain some functionality from a C library.

I think Dmitry means that you will find things easier if you use library
projects for external libraries.