Re: [jamboost] gcc libraries order

From: Rene Rivera (grafik666_at_[hidden])
Date: 2003-03-25 18:19:18

[2003-03-25] David Abrahams wrote:

>Ali Azarbayejani <ali_at_[hidden]> writes:
>
>> David Abrahams wrote:
>>> 
>>> Ali Azarbayejani <ali_at_[hidden]> writes:
>> I don't know about other properties like <include> or <depend> (I hope
>> they are not, because that would lead to a lot of unexpected
>> behavior).
>>
>>
>>> > If "a" is built <link>shared, it will statically link to "b" (I
>>> > don't think this is possible with GCC)
>>> 
>>> Sure it is, as long as "b" is built with <shared-linkable>true
>>> (i.e. -fPIC). A GCC static library is just an archive of object
>>> files; you can link them into anything that can link with .o files.
>>
>>
>> That's good to know. Can GCC restrict symbol exports like MSVC can?
>
>Cygwin/MinGW can. I'm not sure that ELF GCC can.

ELF GCC can... one option is very painfull, the other very convoluted. The
painfull one is to write your own LD linker script that does it on a per
symbol basis or such. The convoluted one is what I do in my SOs for my
project: using a custom double link step and with the help of
cat+sed+grep+objdump+objcopy (obj* versions have to be recent) you can use
the GCC [ __attribute__ ((section (".text.dll"))) ] feature to mark exported
symbols.

I can post the BBV1 code to do the latter if anyone is interested.

-- grafik - Don't Assume Anything
-- rrivera_at_[hidden] - grafik_at_[hidden]
-- 102708583_at_icq