Not sure if this is a bug or not..
- I have a external makefile based .dylib which I added to my XCode project - the absolute and relative paths are correct. - For my own silly reasons I manually made a copy of this dylib directly into the build/debug subdirectory of my XCode project ( I had some DYLD_LIBRARY_PATH issues) - I should NOT have left it there, but I did. - I added some functions to the development .dylib, and calls to it from my main project, but the link in XCode kept failing (symbols not defined). - It appears XCode was ignoring the .dylib in the project and using the 'old' .dylib left behind in the build directory. - Once the old .dylib was removed from the build/debug directory, the link succeeded.
Is there an implicit -L path that points to the build directory that overrides other -L paths? (XCode 2.4.1)
|