xcode library not found

Question

I'm getting the following error:

ld: library not found for -lGoogleAnalytics clang: error: linker command failed with exit code 1 (use -v to see invokation)

I've spent some time googling but can't find how to fix this problem. I'm new to xcode and this is an existing project that I need to work on.

I'm getting the same error whenever i try to archive .ipa. How did you solve it ? — aqsa arshad, Dec 14 '16 at 10:18

score 28 · Answer 1 · answered Jul 06 '12 at 08:49

28

You need to set the "linker search paths" of the project (for both Debug and Release builds). If this library was in, say, a sibling directory to the project then you can set it like this:

$(PROJECT_DIR)/../GoogleAnalytics/lib

(you want to avoid using an absolute path, instead keep the library directory relative to the project).

answered Jul 06 '12 at 08:49

trojanfoe

118,129
19
204
237

30

you didn't tell how to do it. Show, don't tell. – C Johnson Jul 17 '15 at 21:06
7

In the build settings? Do I need to post an image to make the answer valid? – trojanfoe Jul 17 '15 at 21:25
12

@trojanfoe, yes as this would have helped others who may not have as much experience in Xcode as you. For example, I am familiar with **Header Search Paths**, but I have no idea where the "linker search path" is in **Build Settings**. – Daniel Aug 28 '19 at 20:41
1

@Daniel The *Linker Search Path* is the `-L` option to the linker (`ld`). It's not so much about experience with Xcode as experience with the underlying tools; Xcode provides simplified access to the options of the compiler/linker/etc. however it's assumed you know what the options do. – trojanfoe Aug 29 '19 at 05:58
1

@Daniel, this is the challenge with XCode: If I'm content building things using command line scripts, I can add any options I'd like. With XCode, knowing the option you want is not the same as knowing how to get XCode to add it. So IMO it is indeed experience with XCode that is at issue. Even when you add an option where you're supposed to (like Library Search Paths), it still often doesn't work, and debugging what's wrong is incredibly difficult. – user2465201 Sep 10 '21 at 19:34
Build Settings -> Search Paths -> Library Search Paths (both Debug and Release) – juan_marti Oct 07 '21 at 10:50

Aniruddha Shevle · Answer 2 · 2020-05-26T15:03:39.447

26

In my case, the project uses CocoaPods. And some files are missing from my project.

So I install it from CocoaPods: https://cocoapods.org/.

And if the project uses CocoaPods we've to be aware to always open the .xcworkspace folder instead of the .xcodeproj folder in the Xcode.

edited May 26 '20 at 15:03

answered Dec 05 '19 at 03:51

Aniruddha Shevle

4,156
2
20
34

2

what is the reason "if the project uses CocoaPods we've to be aware to always open the .xcworkspace folder instead of the .xcodeproj " ?? – rohitwtbs Jun 01 '20 at 20:00
1

@rohitwtbs: https://guides.cocoapods.org/using/faq.html#cocoapods-uses-workspaces-which-are-considered-user-data-why-does-it-not-use-normal-sub-projects – Aniruddha Shevle Jun 02 '20 at 13:49
2

You saved my day ) – Alex Sep 25 '20 at 21:03
1

You saved my day too! – Chad Oct 04 '21 at 16:48
1

You saved my bacon! – JCraine Feb 19 '22 at 13:44

score 20 · Answer 3 · answered Sep 29 '13 at 05:19

All in all, the Xcode cannot find the position of library/header/framework, then you tell Xcode where they are.

set the path that Xcode use to find library/header/framework in Build Settings --> Library/Header/Framework Search Paths.

Say, now it cannot find -lGoogleAnalytics, so you add the directory where -lGoogleAnalytics is to the Library Search Paths.

score 12 · Answer 4 · answered Mar 03 '17 at 22:05

12

In my case I had a project with lots of entries in "Build Settings > Other Linker Flags"

I needed to reduce it down to just

  $(inherited)
  -ObjC

Old settings:

Updated settings:

answered Mar 03 '17 at 22:05

Scott Jungwirth

5,238
2
33
32

score 6 · Answer 5 · answered Dec 15 '19 at 05:33

6

For me, I open the projectname.xcworkspace file and it all works.

answered Dec 15 '19 at 05:33

vr_driver

1,547
23
35

score 5 · Answer 6 · answered Oct 08 '19 at 00:40

5

If you have pods installed, make sure to open the workspace folder (white Xcode icon) not the project folder. This resolved the library not found for ... error. Very simple issue but I was stuck on this for a long time.

answered Oct 08 '19 at 00:40

Rinni

93
1
2

Thanks!! That worked for me. As you said, it's very simple but I didn't realise until I read your answer! – Jaime S Nov 15 '19 at 20:51

score 2 · Answer 7 · edited Nov 21 '14 at 21:02

2

If you are using Pods to include the GoogleAnalytics iOS SDK into your project, it's worth noting that since the 3.0 release your Other Linker Flags needs to include -lGoogleAnalyticsServices not the old -lGoogleAnalytics

edited Nov 21 '14 at 21:02

Jacksonkr

30,630
38
174
276

answered Nov 07 '13 at 11:06

James Martin

1,030
7
8

Vikas Shukla · Answer 8 · 2021-08-23T07:49:51.963

2

This worked for me:

Go to build setting -> Linking -> Other Linker Flags -> Remove all other than $(inherited)
Cd ios && pod update

edited Aug 23 '21 at 07:49

answered Aug 23 '21 at 07:43

Vikas Shukla

84
3

This worked for me. Thanks for saving the day – Sandeep Rana Dec 25 '21 at 13:29

score 1 · Answer 9 · answered May 29 '13 at 05:52

1

If your library file is called libGoogleAnalytics.a you need to put -lGoogleAnalytics so make sure the .a file is named as you'd expect

answered May 29 '13 at 05:52

David

11
1

score 0 · Answer 10 · answered Sep 02 '15 at 16:32

0

You can also try to lint with the --use-library option, as cocoapods lint libraries as framework by default since v0.36

answered Sep 02 '15 at 16:32

Loegic

3,270
19
32

score 0 · Answer 11 · answered Oct 13 '16 at 11:51

The problem might be the following: SVN ignores .a files because of its global config, which means someone didn't commit the libGoogleAnalytics.a to SVN, because it didn't show up in SVN. So now you try to check out the project from SVN which now misses the libGoogleAnalytics.a (since it was ignored and was not committed). Of course the build fails.

You might want to change the global ignore config from SVN to stop ignoring *.a files.

Or just add the one missing libGoogleAnalytics.a file manually to your SVN working copy instead of changing SVNs global ignore config.

Then re-add libGoogleAnalytics.a to your XCode project and commit it to SVN.

score 0 · Answer 12 · answered Feb 25 '19 at 02:12

0

In XCode 10.1, I had to set "Library Search Paths" to something like $(PROJECT_DIR)/.../path/to/your/library

answered Feb 25 '19 at 02:12

Rikesh Subedi

1,637
21
21

How can I find the path to the library? – Sameer Ingavale Feb 15 '21 at 07:39

score 0 · Answer 13 · edited Jul 24 '20 at 16:54

0

For me it was a silly thing: my mac uploaded the file into iCloud, and that is why Xcode did not find it.

If you turn off the automatic upload, it wont happen again.

edited Jul 24 '20 at 16:54

Adrian Mole

43,040
110
45
72

answered Jul 24 '20 at 15:00

Akos Farkas

68
6

score 0 · Answer 14 · answered Sep 25 '21 at 13:44

0

None of the above worked for me, what did was making sure the Pod file platform :ios, '11.0' matched with the minimum deployment target in the XCODE setting

answered Sep 25 '21 at 13:44

Paul van Motman

1

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Sep 25 '21 at 16:20

xcode library not found

14 Answers14

Linked

Related