‘ld: warning: directory not found for option’

问题:

When I\'m building my Xcode 4 apps I\'m getting this warning:

ld: warning: directory not found for option \'-L/Users/frenck/Downloads/apz/../../../Downloads/Google Analytics SDK/Library\'
ld: warning: directory not found for option \'-L/Users/frenck/Downloads/apz/../Google Analytics SDK/Library\'

But I do not have Google Analytics in my app, I deleted all of it how can I remove the error? And archiving an app gives me the error:

clang: error: no such file or directory: \'armv6\'
Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 1

I\'ve tried so many things but I\'m still getting this error when I\'m trying to make an .IPA file

回答1:

You need to do this:

1. Click on your project (targets)
2. Click on Build Settings
3. Under Library Search Paths, delete the paths

And regarding the second error, sorry i can\'t help you out with that one. Hope someone else can help you out.

回答2:

There are two errors that people seem to be confusing.

If it is a \"directory not found for option \'-L/...\" error, that means it\'s a Library Error, and you should try to:

• Click on your project (targets)
• Click on Build Settings
• Under Library Search Paths, delete the paths

If it is a \"directory not found for option \'-F/...\", that means it\'s a Framework Error, and you should try to:

• Click on your project (targets)
• Click on Build Settings
• Under Framework Search Paths, delete the paths

This might happen when you move the referenced file around.

回答3:

I had to remove the references at:

• Target
• Build Settings
• Framework Search Paths

Then the build was broken (expected). So I removed the Framework (FB SDK), re-added it and voila. No more errors or warnings. :)

回答4:

My problem was that I opened the original .xcodeproj instead of the .xcworkspace that was generated by CocoaPods.

回答5:

For me the problem was a missing escape \"\\\" character.

My search paths were broken up on several lines in the Library Search Paths. Conveniently, they were breaking at spaces in my path. Adding the escape \"\\\" fixed it for me.

$(PROJECT_DIR)/My\\ Project\\ Name/My\\ Directory

回答6:

In my case the problem was Framework Search paths that had incomplete, dead, old links or multiple frameworks of same type. Remove them and your project will compile without any problem.

be sure to do Build -> clean

回答7:

I use cocoa pods so for me, I quit Xcode and ran

pod install

again and reopened the project. This fixed everything!

回答8:

I found the reference which I had to remove at:

• Target
• Build Settings
• Header Search Paths

回答9:

I ran into the same problem (the first one) after an Xcode crash and none of the solutions proposed worked. To suppress the warning I have done:

• manage schemes...

• deleted the current scheme

• Autocrate Schemes Now

回答10:

I got bit by what appears to be the same issue too (this time in XCode 5.0.2). In my case, what happened was XCode decided to escape the quotes already in the \"Build Settings\". So for example:

\"$(SRCROOT)/../GoogleAdMobAdsSdkiOS-6.4.1\"

became

\\\"$(SRCROOT)/../GoogleAdMobAdsSdkiOS-6.4.1\\\"

which caused the build to fail...

Once I removed the escapes on the quotes everything worked fine again. In addition, it would probably be best to remove the quotes altogether unless you need them.

回答11:

This is what worked for me:

1. Click on Project
2. Click on Build Settings
3. Search for \"Framework Search Paths\"
4. Clear the path and type \"$(inherited)\"

回答12:

If this happens after you\'ve added a Podfile to your project and run pod install, go to your project folder, you\'ll see a new file that has been created \"{ProjectName}.xcworkspace\" -- open that file in xcode

The pods that have been installed will be properly linked to your project in this file

回答13:

Follow this step-by-step solution:

1. Click on your project (targets);
2. Click on Build Settings;
3. Under Library Search Paths, delete the paths;
4. Add ./** on Library Search Paths.

回答14:

Supplemental answer

All the answers said to either delete the Framework or Library search paths from the target. I had two problems:

• First, I was looking at my main project target rather than the Unit Test target.
• Second, I couldn\'t figure out how to delete the framework search path. It turned out that it was just clicking it to get in edit mode and then just deleting the string.

回答15:

For me the problem seemed to be that I hadn\'t included the appropriate frameworks (when copying addons from another project I didn\'t copy the frameworks files as well)

回答16:

The key for this type of error is to go into build settings and look at each of the search paths sections such as Library Search Paths, Framework Search Paths and possibly even Header Search Paths and clear out any of the paths that no longer apply that your app is having a hard time trying to find. Remove them and carry on good sir

回答17:

go check out which framework is missing , then go to

=> Build Phases => Link Binary With Libraries

remove the library and then add back

回答18:

I had a similar problem that went away when I created a new scheme and used it to rebuild???

回答19:

For me I have also Tests enabled. The search path for tests was also filled incorrect.

Clear the Framework Search Path for both the regular code and the test code!

回答20:

you should check option for this:

Build Settings-> Framework Search Paths-> {input Your Project Path}

回答21:

I\'ve looked into all [Library Search Paths - Framework Search Paths - Header Search Paths]. but there are no paths to remove, so I was able to make this alert go away by going into the Xcode bundle and creating an empty directory at the path location that the alert was complaining about.

回答22:

Make sure only 1 \"libFlurry.a\" selected in target

worked for me.

回答23:

Do not forget to create the same configuration for Pod project in your workspace, If you change into MainApps new configuration.

For example,

In my case, to resolve this issue I had to create ReleaseOfficial configuration as well for Pod projects when I created ReleaseOfficial configuration for my MainApp.

回答24:

Because of the custom directories that have entered to the search paths ( frameworks and library ), the project overrides pod\'s directories. so it can\'t find it.

To solve this problem, delete all custom directories from

Search Paths -> Library Paths and Framework Paths,

only see ${inherited}.

I hope this helps. It worked for me.