• 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: Can't tell build configurations to use different libraries
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Can't tell build configurations to use different libraries


  • Subject: Re: Can't tell build configurations to use different libraries
  • From: Scott Tooker <email@hidden>
  • Date: Thu, 18 Aug 2005 19:12:25 -0700

Right now the only way to workaround the problem is to pass in the library in via "Other Linker Flags" to have the appropriate library linked in.

We are aware of the limitation that configurations cannot use different sets of files when building, and want to fix it in a future release.

Scott

On Aug 18, 2005, at 9:58 AM, Dave Thorup wrote:

On Aug 18, 2005, at 11:37 AM, Rush Manbert wrote:

I believe you can do this by putting the debug and release library versions in different directories, then specifying different library load paths for each configuration. Of course, installing the libraries in different places is another headache to deal with... :-)

Except that this doesn't work when your Release and Debug libraries are named differently (ex: foo.dylib & foo_debug.dylib). We've run into this problem as well and I haven't been able to find a good solution for it. Right now what I do is for any project that needs to link with our libraries I create separate targets for each build and a single build configuration. That way when I need to create a Debug build I change to the Debug target and I never need to change the build configuration (because there's only one).


Of course when you do it this way you run into the other problems that you described when you need to manage multiple targets. I'd really like for Apple to address this problem, it's really the only major shortcoming that I have with the build configurations.
_____________________________


Dave Thorup
Software Engineer
email@hidden

http://www.kuwan.net
Defaults Manager - The premier editor for Mac OS X's User Defaults / Preferences database.



_______________________________________________ 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

_______________________________________________ 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
  • Follow-Ups:
    • Re: Can't tell build configurations to use different libraries
      • From: Dix Lorenz <email@hidden>
References: 
 >Can't tell build configurations to use different libraries (From: "Starman" <email@hidden>)
 >Re: Can't tell build configurations to use different libraries (From: Rush Manbert <email@hidden>)
 >Re: Can't tell build configurations to use different libraries (From: Dave Thorup <email@hidden>)

  • Prev by Date: Re: warning prebinding disabled because dependent library /usr/lib/libobjc.A.dylib
  • Next by Date: Re: Cleaning with a shell script build phase
  • Previous by thread: Re: Can't tell build configurations to use different libraries
  • Next by thread: Re: Can't tell build configurations to use different libraries
  • Index(es):
    • Date
    • Thread