Re: Linking with GNAT on Windows

[Maciej Sobczak <see.my.homepage@gmail.com>]

On 25 Lis, 10:46, "Dmitry A. Kazakov" <mail...@dmitry-kazakov.de>
wrote:

> Usually debug/release versions have different names like mylibraryd.lib or
> else placed into different subdirectory like .\Debug vs. .\Release. What
> about the "-L" switch?

If the file was not found, the linker would say so. Every -lmylibrary
option must have a corresponding library file.

> I think you should:
>
> 1. Remove all instances of mylibrary.lib.
> 2. Build it anew.
> 3. Ensure that GNAT links the library you have built.
> 4. If error persists, view the lib file. Compare names there and the
> unresolved references reported by GNAT.

Well, no. :-)
As already said, this is the interaction between Visual Studio and
MinGW, so can be completely reproduced outside of GNAT.

The problem proved to be related to the Visual optimization option
that is used to enable so-called whole-program optimization (Enable
link-time code generation). On command-line this is /GL option.

This option must be switched off. I hope this observation will help
other programmers.

--
Maciej Sobczak * www.msobczak.com * www.inspirel.com

Database Access Library for Ada: www.inspirel.com/soci-ada