Re: Upgrading GNAT GPS 5.0 -> 5.3

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Thu, 14 Aug 2014 18:59:48 +0300, Victor Porton wrote:

> Dmitry A. Kazakov wrote:
> 
>> On Thu, 14 Aug 2014 15:18:49 +0300, Victor Porton wrote:
>> 
>>> Egil H H wrote:
>>> 
>>>> On Wednesday, August 13, 2014 10:10:31 PM UTC+2, Victor Porton wrote:
>>>>  
>>>>>    package Linker is
>>>>> 
>>>>>       for Linker_Options use ("-lraptor2");
>>>>> 
>>>>>    end Linker;
>>>>>
>>>> 
>>>> From the GPRbuild User's Guide (emphasis mine):
>>>> Linker.Linker_Options:
>>>> This attribute specifies additional switches to be given to the linker
>>>> when linking an executable.
>>>> *It*is*ignored*when*defined*in*the*main*project* and taken into account
>>>> in all other projects that are imported directly or indirectly. These
>>>> switches complement the Linker.Switches defined in the main project.
>>>> This is useful when a particular subsystem depends on an external
>>>> library: adding this dependency as a Linker_Options in the project of
>>>> the subsystem is more convenient than adding it to all the
>>>> Linker.Switches of the main projects that depend upon this subsystem.
>>> 
>>> I don't understand.
>>> 
>>> Does this mean that it's impossible to link a library to the main
>>> project?!
>> 
>> It means that the option is intended for library projects not for the
>> client projects.
> 
> 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;

> Many non-library projects need to link to libraries.

They should *always* use library projects instead of linking directly to
external libraries.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de