Re: Shared library project

["Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr>]

Le Thu, 10 Jun 2010 14:50:17 +0200, Andrei Krivoshei  
<andrei.krivoshei@gmail.com> a écrit:

> My original intent:
>
> The dinamic library project, say A project, (the final product)
> shoould import some another project, say B project, (collection of
> functions and objects- tagged records and etc).
> I am myself the author of the both projects, therefore for me doesn't
> matter what kind of project I select for B. But the final library
> project must be compiled correctly.
So B has to be a library... which seems OK after what follows.

> Ok, if "A library project can only import library projects.", then why
> I cannot import the static library project into dynamic library
> project?
> If I try do this, the gnatmake gives: [mlcb_fe_dll.gpr:3:09: shared
> library project "mlcb_fe_dll" cannot import static library project
> "sp_lib"]
Did you try to make all library dynamic ? Are there some reason which  
disallows this ?

> Thus, if I want to build the dynamic library project, which uses
> another projects, then I need to change the type of those projects to
> 'dynamic',
So you may have a DLL depending on another DLL, which is legal on Windows.

> and consequently, the resulting library, A.dll (for the
> Windows) MUST be supplyed by whole complect of others libraries
> (B.dll, C.dll, ...), which were imported into project A?
I am not sure I have understood. If A.dll depends on B.dll and C.dll, this  
should be OK. Whar kind of dependencies do you have ? Are they like the  
ones I give ?

I am bit surprised, as it should be possible to build a DLL using static  
library. Unfortunately, I have never experimented this with GNAT. Anyway,  
feel free to give more details.

-- 
There is even better than a pragma Assert: a SPARK --# check.
--# check C and WhoKnowWhat and YouKnowWho;
--# assert Ada;
--  i.e. forget about previous premises which leads to conclusion
--  and start with new conclusion as premise.