Re: <library> (Was: I'm back!)

From: Markus Schöpflin (markus.schoepflin_at_[hidden])
Date: 2002-10-17 03:30:02

Vladimir Prus wrote:> Markus Schöpflin wrote:

> I don't find it confusing yet. Most linux application have
> "--enable-shared" or "--disable-shared" switch to configure, which
> controls how libraries internal to application are build -- either
> as static or as shared. I think it's quite reasonable: most
> libraries can be build and used in either way, so it's just another
> features.

So shared=true will map to --enable-shared and shared=false to 
--disable-shared. Did I get it right?

> Regarding <lib>my / <dll>my. In V2 we don't use those prefixes that
> identify type, we just don't need them. And further, as I say
> above, most of the time I don't want the request specifically
> static or shared library.

Well, yes, during development I don't care either. Especially on unix 
platforms. For windows it's more complicated, anyway. For a build that 
ships to a customer it's not that easy. :-)

>>> For a more general case, we might try <find-library-static> and
>>> <find-library-shared>.
>>
>> I think we absolutely need this. In the use case I mentioned
>> above the system libs are libm and libc and the libs I have to
>> link to statically are libs like openssl or libz which aren't
>> build by boost.build either.
>
> Okay, noted.

Thanks.

>> There is another use case I have: Linking to oracle libs. On most
>> platforms, you _have_ to specify very exactly what get's linked
>> and how. Currenty I'm using the fact that a rule name can appear
>> as the prerequisite of a target. For example:
>>
>> exe hello : hello.cpp : link_to_oracle_libs ;
>>
>> and link_to_oracle_libs is a rule which inserts the right things
>> in the linker command line depending on the current build
>> settings and platform. It would be great if something like this
>> would be supported in v2 as well.
>
> I think a minimal form of this is already supported. You can
> declare new target type ORACLE_EXE, and specify that it should be
> building in the same way as EXE, but with certain additional
> properties. Those properties can be computed dynamically.

This will do in my special use case. But a more general solution to 
this would be nice.

Markus