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

Re: linking problem


  • Subject: Re: linking problem
  • From: Daniel Jalkut <email@hidden>
  • Date: Fri, 1 Dec 2006 18:06:26 -0500

When you say "PB" I hope you mean Xcode. If you're just getting acquainted with Cocoa or Mac development then it's worth noting that to get help in these forums you'll generally need to be running a recent-ish version of Xcode.

The -L line is provided by a build setting "Library Search Paths" defined somewhere in your project. Look in the Project build settings and in the Target build settings.

Xcode is pretty good about adding these build settings when you add libraries, etc., but in my experience it's terrible about taking them away.

Daniel

On Dec 1, 2006, at 5:20 PM, Jaime Magiera wrote:

Hi,

I inherited a Cocoa project from another developer. While updating the project, I moved some resources and frameworks from one folder to another, more appropriately named folder. I reset the paths on the all the libraries, frameworks, and header files I could find in the project. However, on build, the linker continues to look in that old directory and an error is thrown due to this. Here is the error...

----------------

-L/Users/jaimelm/applicationmaster/application/../source/EWS\ Public \ Beta/eSellerate\

<snip>

/usr/bin/ld: warning -L: directory name (/Users/jaimelm/ applicationmaster/application/../source/EWS Public Beta/eSellerate Libs) does not exist
/usr/bin/ld: can't locate file for: -lEWS
------------------


I deleted the old folder. However, no items in the project appear to have lost their path (turned red) and the linker continues to look in that directory.

Any thoughts on how I can get PB to be more specific about where in the build this link is? Or is that info in the error message and I'm just not seeing it. Any help appreciated.

Jaime Magiera
Sensory Research Network
http://www.sensoryresearch.net




_______________________________________________
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: linking problem - flashback
      • From: Jaime Magiera <email@hidden>
References: 
 >linking problem (From: Jaime Magiera <email@hidden>)

  • Prev by Date: linking problem
  • Next by Date: Re: linking problem
  • Previous by thread: linking problem
  • Next by thread: Re: linking problem - flashback
  • Index(es):
    • Date
    • Thread