[VDPAU] [PATCH 1/4] trace: use intermediate static library in the build

[Emil Velikov]

On 19 March 2015 at 11:57, Rémi Denis-Courmont <remi at remlab.net> wrote:
> Le 2015-03-19 14:17, Emil Velikov a écrit :
>>
>> On 19 March 2015 at 07:45, Rémi Denis-Courmont <remi at remlab.net> wrote:
>>>
>>> Le 2015-03-19 02:50, Emil Velikov a écrit :
>>>>
>>>>
>>>> Compile the source into a static library, to prevent C++ linkage. The
>>>> latter of which unnesseserally pulls libm, libgcc_s and libstdc++ as
>>>> dependencies.
>>>
>>>
>>>
>>> I think that's wrong. If a library has C++ code, it depends on libsdtc++
>>> and
>>> that's the end of the story. The rest is an implementation detail of the
>>> compiler.
>>>
>> Just because something is written in C++ that does not have to mean
>> that it depends on the C++ runtime.
>
>
> Yes - it *does* mean it.
>
Hmm... do you have some references/recommendations that I can read through ?
If you can kindly point out to a section number, rather than throwing
the whole thing (200 page document or similar) at me that'll be
greatly appreciated.

>> This is one good example of such a
>> case. Afaict the reason behind using C++ (over C) here is to make use
>> of the additional type safety (possibly others).
>
> What causes a symbol to be imported from libstdc++ is an implementation
> detail of the C++ compiler. As a programmer, you cannot assume anything
> about it. In fact, the very existence of libstdc++ is an implementation
> detail of GCC.
>
As a programmer you're absolutely correct. Although the engineer
within tends to disagree - need to find a way to shut him up :-P

Thanks
Emil