Re: GCC, DLLs are accumulated ?
Re: GCC, DLLs are accumulated ?
- Subject: Re: GCC, DLLs are accumulated ?
- From: Shawn Erickson <email@hidden>
- Date: Thu, 21 Sep 2006 08:56:07 -0700
On Sep 21, 2006, at 6:35 AM, Ruslan Zasukhin wrote:
Hi guys,
** We have project A which produce A.DLL that depends on
few dlls 1.dll and 2.dll
** Also we have project that produce B.dll and it should depend on
A.dll.
It is strange that xcode/gcc want to see in this project also 1.dll
and
2.dll
in MS or CodeWarrior it was enough include into project B
single A.dll
** If next I have project C that produce C.dll which depend on B.dll
I again need include here all above dlls. Nightmare.
-----------
So why GCC works in this way? This break e.g. Encapsulation idea.
May be exists way to force work it in normal/smart way ?
Kinda of confused... are you really producing dynamically linked
libraries that end in DLL for Mac OS X? That may be your problem... I
am not sure if dyld knows how to look those up (it works with .dylib).
If you are dynamically linking against a library and that library was
built to dynamically link against another set of libraries you should
only need to specify that you link against the first library. If that
is not working it sounds like either the secondary dylibs are not
installed in the location that the library expects it or the location
information in the library is wrong.
You can use otool to understand what a binary dynamically links
against (including expected install location).
QuadG5:/usr/lib shawnce$ otool -L libxml2.dylib
libxml2.dylib:
/usr/lib/libxml2.2.dylib (compatibility version 9.0.0,
current version 9.16.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
current version 88.0.81)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current
version 1.2.2)
/usr/lib/libiconv.2.dylib (compatibility version 5.0.0,
current version 5.0.0)
Note you can play around with library resolve paths and/or a shared
build output directory ... that may correct this issue if you cannot
install the libraries in the location that is expected at the time
you build. Review the Xcode documentation for more information.
-Shawn
_______________________________________________
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