Re: gcc vs. stdc++ dylib usage
Re: gcc vs. stdc++ dylib usage
- Subject: Re: gcc vs. stdc++ dylib usage
- From: Eric Albert <email@hidden>
- Date: Mon, 17 Apr 2006 07:55:03 +0100
On Apr 17, 2006, at 6:06 AM, smack supersonic wrote:
I have noticed that when building with XCode and/or directly via
command line the following two dylib's are linked with my binary:
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
version 7.4.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current
version 1.0.0)
Although everything works just fine, i am little bit worried that
two almost identical dll's are used!?
Is there something which makes you think those libraries are almost
identical? They do different things.
So my question is:
Is there a way to force either of this dll's to be mutualy exclusive?
The compiler links in the dylibs your code needs so, no, you wouldn't
want that.
Shouldnt this cause problems if in more complex example (host with
plug-in components) is dynamically loading plug-in modules that may
use either of these libraries?
Not at all. That's one reason why they're dylibs rather than static
libraries -- you don't get duplicate copies of them in your process
if you have multiple components which use them.
-Eric
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden