• 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: Miscellaneous XCode Questions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Miscellaneous XCode Questions


  • Subject: Re: Miscellaneous XCode Questions
  • From: Ben Weiss <email@hidden>
  • Date: Mon, 15 May 2006 03:23:50 -0700


On May 12, 2006, at 11:03 AM, Rush Manbert wrote:

Ben Weiss wrote:
On May 11, 2006, at 10:44 PM, Chris Espinosa wrote:
On May 11, 2006, at 10:28 PM, Ben Weiss wrote:

1. My app links to separate static libraries for debug and release versions, using linker flags -lMyLibrary and - lMyLibrary_d for the respective targets. This works fine, but when I recompile the library, the application project doesn't recognize that the libraries have changed; I have to clean and rebuild the application every time to make sure it incorporates the changed library. Is there a way to get this to happen automatically? (In other words, for the application project to recognize that the library is changed, and force a re-link on build?)


If you just add the libraries to the target they'll get linked for you, and dependency checking will work. If you enter file names as values in build flags, dependency checking doesn't know about them.
The problem is that my two targets link to two different versions of my library (debug to debug; release to release). I'm not aware of a way to add a library to one target but not another, other than by using the linker flags. Do you know a way? We spent quite a while last WWDC trying to find a better approach with no success... but maybe XCode has new options now? Short of adding new features to do this sort of linking, it would be great if XCode could recognize this situation from the linker flags and handle the dependency properly, unless there's some specific reason why it shouldn't...

Hi Ben,

Assuming that your static libraries are being built with Xcode, then you should read these:

http://lists.apple.com/archives/xcode-users/2006/Mar/msg00455.html
http://lists.apple.com/archives/xcode-users/2006/Mar/msg00491.html

They describe my similar problem and the successful workaround.

Thanks for the workaround. I'll try implementing it, once I wrap my head around exactly what you did... it's kinda sad that we have to resort to such measures for such a simple operation (and then hope that the workaround doesn't break in the future)... XCode guys, please make this easier! I'll file an enhancement request, though I'm sure it'll be a duplicate.


Ben

_______________________________________________
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: 
 >(no subject) (From: AurĂ©lien Ammeloot <email@hidden>)
 >Miscellaneous XCode Questions (From: Ben Weiss <email@hidden>)
 >Re: Miscellaneous XCode Questions (From: Chris Espinosa <email@hidden>)
 >Re: Miscellaneous XCode Questions (From: Ben Weiss <email@hidden>)
 >Re: Miscellaneous XCode Questions (From: Rush Manbert <email@hidden>)

  • Prev by Date: Re: MOVQ Intrinsic?
  • Next by Date: Re: MOVQ Intrinsic?
  • Previous by thread: Re: Miscellaneous XCode Questions
  • Next by thread: Bundling bundles in framework
  • Index(es):
    • Date
    • Thread