• 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: linking to debug vs. deploy versions of lib
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: linking to debug vs. deploy versions of lib


  • Subject: Re: linking to debug vs. deploy versions of lib
  • From: Rob Dye <email@hidden>
  • Date: Mon, 16 Aug 2004 14:04:20 -0500

I think I figured this out.

It boils down to:
modify the BUILD STYLE option "Library Search Paths" in each of the Debug and Deploy styles to be "foolibs/debug $(value)" and "foolibs/release $(value)", respectively.


I went through several confusing stages to get to this point, though.

1) When adding the debug and release version of a library to the same location in the files list, only the last one actually ends up in the list. (I guess Xcode doesn't like to show the same name twice in the same group.) However, both paths ended up in the _target_ Library Search Paths. Also, the paths as recorded in the project file were absolute, not relative to my project.

2) I created a pair of subgroups under my "Frameworks and Libraries" group and successfully got both files to show up in the files list. However, after doing so, both the debug and release versions of the libs were in both builds.

3) After locating the "Library Search Paths" option in the build styles and modifying them to refer to the appropriate directory, I was disturbed by the fact that the _target_ "Library Search Paths" option still had both paths ("foolibs/debug" and "foolibs/release") listed. I manually deleted these paths from this option, even though it may not have been necessary (Xcode did give me the feedback of strikethrough text for the target option name).


We went through a phase in our usage of Project Builder some time ago where we did not use Build Styles for our release vs. debug versions. We instead used two separate targets for this purpose. This duplicates more build info, but made it easy to tell PB/Xcode to which build a file contributes.


I'm still not sure how I would add a file to my Xcode project that should ONLY contribute to the debug style. I don't yet have to do this, but I can't guarantee it won't.

Rob



On Aug 16, 2004, at 10:02 AM, Rob Dye wrote:

I've got a set of libraries that are distributed in the form of debug and release versions that are named identically and located in different directories called "debug" and "release".

I need a way to change which lib I link to depending on whether I am doing a Debug or Deploy build. I can't find a place in the Xcode UI that allows me to specify this. Help?

Thanks,
Rob Dye
National Instruments
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.


  • Follow-Ups:
    • Re: linking to debug vs. deploy versions of lib
      • From: Dave Camp <email@hidden>
References: 
 >linking to debug vs. deploy versions of lib (From: Rob Dye <email@hidden>)

  • Prev by Date: Re: Subversion SCM status not showing up on most files (Xcode 1.5)
  • Next by Date: Re: linking to debug vs. deploy versions of lib
  • Previous by thread: linking to debug vs. deploy versions of lib
  • Next by thread: Re: linking to debug vs. deploy versions of lib
  • Index(es):
    • Date
    • Thread