Re: Programs' following -F not found
Re: Programs' following -F not found
- Subject: Re: Programs' following -F not found
- From: Keith Blount <email@hidden>
- Date: Mon, 8 Feb 2010 06:03:46 -0800 (PST)
Many thanks for the replies, much appreciated.
Ken - that makes sense, thank you. And John is right that it would resolve to the ~/Programs directory on my disk. Looking in there, I think it may be that I used to keep the Sparkle framework in the ~/Programs directory, although I moved it some time ago (I guess the recent Xcode/gcc update got more strict with its warnings again). The only problem is that I just checked the Build pane of Project settings, and "Framework Search Paths" under "Search Paths" is completely blank (for all configurations), as are the other search path settings. I've also been through and done a "Reveal in Finder" on all linked frameworks just to check everything is pointing where I expect, and I've tried deleting the Sparkle framework and Copy Files build phase for it and recreating them, just in case they were the culprits - but still no joy, I'm still seeing the warning.
Is there anywhere else in Xcode where this could be set?
Thanks again and all the best,
Keith
P.S. David - I'm not sure what the full transcript will reveal (there are other warnings in there that are the result of stuff I'm working on at the moment, for instance), but here are the relevant sections:
Build MyApp of project MyApp with configuration Release
Ld build/MyApp.build/Release/MyApp.build/Objects-normal/i386/MyApp normal i386
cd /Users/username/MyApp/Development/Code/MyApp
setenv MACOSX_DEPLOYMENT_TARGET 10.4
/Developer/usr/bin/gcc-4.2 -arch i386 -L/Users/username/MyApp/Development/Code/MyApp/build/Release -L/Users/username/MyApp/Development/Code/MyApp -L/Users/username/MyApp/Development/Code/MyApp -L/Users/username/MyApp/Development/Code/MyApp -L/Users/username/MyApp/Development/Code/MyApp -F/Users/username/MyApp/Development/Code/MyApp/build/Release -F/Users/username/MyApp/Development/Code/MyApp -F/Users/username/MyApp/Development/Code/MyApp -F/Users/username/MyApp/Development/Code/MyApp/../../../Programs -F/Users/username/MyApp/Development/Code/MyApp/../../../../Programming -F/Users/username/MyApp/Development/Code/MyApp -filelist /Users/username/MyApp/Development/Code/MyApp/build/MyApp.build/Release/MyApp.build/Objects-normal/i386/MyApp.LinkFileList -mmacosx-version-min=10.4 -weak_framework QuickLook -framework Cocoa -framework Carbon -framework ScrAppKit -framework QTKit -framework Quartz -framework WebKit -framework QuickTime -framework AddressBook
-framework QuickLook -framework QuartzCore -framework Sparkle -lEWS -lValidateUniversal -framework Growl -framework SystemConfiguration -o /Users/username/MyApp/Development/Code/MyApp/build/MyApp.build/Release/MyApp.build/Objects-normal/i386/MyApp
ld: warning: directory '/Users/username/MyApp/Development/Code/MyApp/../../../Programs' following -F not found
Ld build/MyApp.build/Release/MyApp.build/Objects-normal/ppc/MyApp normal ppc
cd /Users/username/MyApp/Development/Code/MyApp
setenv MACOSX_DEPLOYMENT_TARGET 10.4
/Developer/usr/bin/gcc-4.2 -arch ppc -L/Users/username/MyApp/Development/Code/MyApp/build/Release -L/Users/username/MyApp/Development/Code/MyApp -L/Users/username/MyApp/Development/Code/MyApp -L/Users/username/MyApp/Development/Code/MyApp -L/Users/username/MyApp/Development/Code/MyApp -F/Users/username/MyApp/Development/Code/MyApp/build/Release -F/Users/username/MyApp/Development/Code/MyApp -F/Users/username/MyApp/Development/Code/MyApp -F/Users/username/MyApp/Development/Code/MyApp/../../../Programs -F/Users/username/MyApp/Development/Code/MyApp/../../../../Programming -F/Users/username/MyApp/Development/Code/MyApp -filelist /Users/username/MyApp/Development/Code/MyApp/build/MyApp.build/Release/MyApp.build/Objects-normal/ppc/MyApp.LinkFileList -mmacosx-version-min=10.4 -weak_framework QuickLook -framework Cocoa -framework Carbon -framework ScrAppKit -framework QTKit -framework Quartz -framework WebKit -framework QuickTime -framework AddressBook
-framework QuickLook -framework QuartzCore -framework Sparkle -lEWS -lValidateUniversal -framework Growl -framework SystemConfiguration -o /Users/username/MyApp/Development/Code/MyApp/build/MyApp.build/Release/MyApp.build/Objects-normal/ppc/MyApp
ld: warning: directory '/Users/username/MyApp/Development/Code/MyApp/../../../Programs' following -F not found
----- Original Message ----
From: Ken Thomases <email@hidden>
To: Keith Blount <email@hidden>
Cc: email@hidden
Sent: Mon, February 8, 2010 12:18:20 PM
Subject: Re: Programs' following -F not found
On Feb 7, 2010, at 5:34 PM, Keith Blount wrote:
> Sorry for what is bound to be a dumb question, but I finally got around to updating to the latest version of Xcode and suddenly I'm seeing this compile warning:
>
> ld: warning: directory '/Users/myusername/MyFolder/MyProgramName/../../../Programs' following -F not found
>
> Everything was compiling fine before, but clearly this is telling me that a folder can't be found, and it's bound to be something I've set somewhere myself at some point (it's a large project that represents years' worth of work, so I bet it's just something that was set a while back and needs resetting, but given all the ../../ in the path I can't see where).
>
> Does anybody know exactly what "following -F not found" means?
This complaint is coming from the "ld" program, which is the linker. That's why the line is prefixed with "ld:". The -F option to the linker informs it of directories, in addition to the standard locations, in which is should look for frameworks.
The warning is saying something specified a framework search directory which doesn't exist. It's only a warning because, unless the failure to find that directory also prevented the linker from finding a framework, everything can still build correctly. However, it's worth warning about because maybe you meant the linker to find one framework in the specified directory and it found a different framework of the same name in a different directory.
If you didn't/don't intend to tell the linker to look anywhere in particular for frameworks, then the case the linker is concerned about is not relevant.
Still, you should check the Framework Search Paths setting in the build settings for your project and target(s). Xcode may have automatically added a search path if you ever added a framework to a target that wasn't in the usual place. If you later removed that framework, Xcode does not automatically remove the search path.
Cheers,
Ken
_______________________________________________
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