• 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 static libraries
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Linking static libraries


  • Subject: Re: Linking static libraries
  • From: Dieter Oberkofler <email@hidden>
  • Date: Fri, 3 Mar 2006 17:24:04 +0100


On Mar 3, 2006, at 4:52 PM, Rush Manbert wrote:

Andrew Taylor wrote:
hi,
I am trying to use Xcode 2.2 to link several static libraries into an application. No they can't be dynamic libraries or frameworks, so lets not go there.
Initially I created the bunch of needed Xcode projects, one target each, and with the standard "release" and "debug" build configurations and built everything with the debug build configuration. There are no linkages between projects in the project files themselves.
The application project that uses the static libraries includes the static libraries from the debug folder, because that is what I had - debug builds of libraries.
Now I want to build a release version. So I went and built the release build configuration of everything.
The application won't link because it can't find any static libraries. That seems obvious since when the static libraries are included in the project you have to specify them down to the file. But I don't see a way to specify a static library based on the build configuration.
What is the magic part of the application project build configuration that controls where it looks for a static library based on the build configuration?
(Right now my work around is to put the static libraries in one place, independent of build configuration and link to that. So I can't keep a "debug" static library around for the "debug" version of the application and a "release" static library for the "release" version of the application.)

Take a look at your "Library Search Paths" settings. You probably need to tweak them to point to the Release library locations in the Release build configuration. From what you describe, you will have different paths in the Debug and Release build configurations.


- Rush
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40qualiant.at


This email sent to email@hidden

I'm dealing with a similar problem and have understood that the only way to go is to add the needed static libraries in the "Other Linker Flags".
- Dieter


_______________________________________________
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: Linking static libraries
      • From: Rush Manbert <email@hidden>
    • Re: Linking static libraries
      • From: Paul Russell <email@hidden>
References: 
 >Linking static libraries (From: Andrew Taylor <email@hidden>)
 >Re: Linking static libraries (From: Rush Manbert <email@hidden>)

  • Prev by Date: XCode 2.1 vs. 2.2
  • Next by Date: Re: Linking static libraries
  • Previous by thread: Re: Linking static libraries
  • Next by thread: Re: Linking static libraries
  • Index(es):
    • Date
    • Thread