Hi Stefan - I have observed at various times that Xcode is a bit
"stingy" with its "library search paths" settings. I have seen
problems like you're describing when there is some stale valule in
the library search paths build setting, that seems to override the
built-in logic Xcode brings with the subproject dependency.
Is that black magic that Xocde uses to construct the gcc calls from
documented anywhere? I'm often seeing things happening in my Xcode
projects that I cannot explain at all. I have projects that rename
files by themselves and projects that rebuild certain source files
every time I hit build, even when I haven't touched then in ages. And
I have no idea how to fix these.
If that doesn't address the problem I recommend examining the
verbose (text) output of the build to see what the linker line
looks like. Here you will be able to see exactly what search paths
are being passed. The problem here is that linking against
"libfoo.a" file always (?) involves passing a "-lfoo" option to the
linker as well as a variety of parameters indicating where it
should search for said library.
That is what I would have expected, but is precisely what didn't happen:
Where as all my other libraries are referenced as -lwx_mac, -lBase,
etc with their appropriate locations in $LD_PATH, that one library is
being passed to the linker as /Users/stew/dev/longisland/poser/poser/
build/Debug/libEFImage.a. And I can't see anything that would be
different about this subproject from all the others.
Stefan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
