• 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: static lib gets wrong path
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: static lib gets wrong path


  • Subject: Re: static lib gets wrong path
  • From: Daniel Jalkut <email@hidden>
  • Date: Thu, 24 Nov 2005 10:19:09 -0500

Hi Stefan - I have observed at various times that Xcode is a bit "stingy" with its "library search paths" settings. I have seen problems like you're describing when there is some stale valule in the library search paths build setting, that seems to override the built-in logic Xcode brings with the subproject dependency.

If you see any useless values in the library search paths setting for your project or targets, try removing them, cleaning, and building again.

If that doesn't address the problem I recommend examining the verbose (text) output of the build to see what the linker line looks like. Here you will be able to see exactly what search paths are being passed. The problem here is that linking against "libfoo.a" file always (?) involves passing a "-lfoo" option to the linker as well as a variety of parameters indicating where it should search for said library.

Daniel

On Nov 24, 2005, at 6:21 AM, Stefan Werner wrote:

Hi,

I'm still not quite understanding how Xcode handles paths to subprojects:

I created a new static library project that works just fine by itself. Then I added that as a subproject to my main project and checked the little checkmark next to the .a file to make my main project link against it - just as I did with all the subprojects I added previously. However, Xcode now insists on looking for my new library in the build directory of the main project instead of the subproject, whereas it finds all the other libraries in their respective build directories. I can't find anything I did differently with this library than all the others - is it because I am using Xcode 2.2 now? Is there a way to make Xcode deal properly with subprojects without having to use shared build directories?

Thanks,
Stefan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
sweater.com


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: static lib gets wrong path
      • From: Stefan Werner <email@hidden>
References: 
 >static lib gets wrong path (From: Stefan Werner <email@hidden>)

  • Prev by Date: Re: xcode 2.2 problems
  • Next by Date: Re: No such file error?
  • Previous by thread: static lib gets wrong path
  • Next by thread: Re: static lib gets wrong path
  • Index(es):
    • Date
    • Thread