Re: How to nicely distribute a simple Ada library?

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

On Mon, 05 Dec 2011 16:51:55 +0100, Yannick Duchêne (Hibou57) wrote:

> Le Mon, 05 Dec 2011 16:22:19 +0100, Georg Bauhaus  
> <rm.dash-bauhaus@futureapps.de> a écrit:
>> Another reason is obfuscation. Where do you find the build
>> settings for this software?  Somewhere in the sources.
>> […]
> I see three advantages for this: first this is  
> clearly visible from body source (especially if specified at the top of  
> the source) and then,

Which body? The option is seen in the gnatmake/gprbuild string. If an
inappropriate option appears there, your actions? If a desired option does
not, how do you find the body missing it?

> this applies localization principle (lack of  
> localization does not help understanding), and then again, if this package  
> is not used, then the linker option is automatically dropped (avoid  
> unneeded dependencies).

Normally, linker options do not apply to the bodies, they do to the program
as a whole.

> If multiple package links to the same library,  
> there is no troubles anyway.

That depends on the option. If conflicting options appear, good luck in
resolving the problem.

> The only one issue I know is linker dependency. The pragma Linker_Options  
> arguments syntax is not specified by the standard.

Yes, the compiler has all rights to ignore it. So you would definitely
enjoy gathering linker options spread across all *used* bodies guessing
what was ignored and what was taken...

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