• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Odd linker behaviour
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Odd linker behaviour

  • Subject: Odd linker behaviour
  • From: Andrew Cunningham <email@hidden>
  • Date: Tue, 8 May 2007 17:05:34 -0700
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)

Andrew

 

 _______________________________________________
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
  • Prev by Date: FYI: Pre-WWDC MacDev Montreal reunion
  • Next by Date: Strip symbols from framework (dumb?)
  • Previous by thread: FYI: Pre-WWDC MacDev Montreal reunion
  • Next by thread: Strip symbols from framework (dumb?)
  • Index(es):
    • Date
    • Thread