• 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
Re: Linker woes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Linker woes


  • Subject: Re: Linker woes
  • From: Tim Murison <email@hidden>
  • Date: Wed, 13 May 2009 16:02:35 -0400
  • Thread-topic: Linker woes

> I believe Xcode uses the CONFIGURATION_BUILD_DIR to find dependent
> libraries for linking. When you build a "Test" into the "Tests"
> directory, Xcode will still look in the "Build/Debug/Tests" for
> library linking. It appears that your libraries are not in the
> CONFIGURATION_BUILD_DIR that you use when building an test (i.e. Build/
> Debug/Tests), but are rather in the CONFIGURATION_BUILD_DIR that are
> used when building libraries (i.e. Build/Debug/Libraries).

I found a workaround. I do need to change CONFIGURATION_BUILD_DIR in order
to get the kind of output I like, but my linker troubles were easily
circumvented by naming my dylibs properly. Quite a few of them had names
like "mylib.dylib" instead of "libmylib.dylib". When the "lib" prefix is
missing gcc requries a full path to the file instead of just "-lmylib".

 _______________________________________________
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

References: 
 >Re: Linker woes (From: Preston Jackson <email@hidden>)

  • Prev by Date: Re: Linker woes
  • Next by Date: Groups vs. Folder Refs
  • Previous by thread: Re: Linker woes
  • Next by thread: Re: Linker woes
  • Index(es):
    • Date
    • Thread