Re: Shared library project

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

On Thu, 10 Jun 2010 05:50:17 -0700 (PDT), Andrei Krivoshei wrote:

> 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.
> 
> Ok, if "A library project can only import library projects.", then why
> I cannot import the static library project into dynamic library
> project?

That depends on the linker and loader capacities of the given OS. In the
worst case you have to distinguish the library build project and the
library import project. (These can be physically one gpr file, though) The
former can import anything. The latter describes a library which is already
linked and can only be loaded, but not re-linked. In this case it may not
depend on a static library.

> 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', 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?

No, you can build a library as you wish. It can incorporate other projects,
i.e. became one big lump, or else refer to other projects in the form of
dynamic libraries. The choice is up to you.

When your library is to be used by in other projects you describe it
appropriately for them (using Externally_Built set to true).

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