Mac OS : ld: library not found for -lglfw
up vote
0
down vote
favorite
Building my project I get error:
ld: library not found for -lglfw
clang: error: linker command failed with exit code 1 (use -v to see invocation)
But I have installed glfw, via brew install glfw
brew list --versions | grep glfw
glfw 3.2.1
ls /usr/local/lib | grep glfw
libglfw.3.2.dylib
libglfw.3.dylib
libglfw.dylib
clang -v
Apple LLVM version 10.0.0 (clang-1000.10.44.4)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
gcc -v
Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/c++/4.2.1
Apple LLVM version 10.0.0 (clang-1000.10.44.4)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
MacOS : 10.14.1 (18B75)
macos glfw
asked Nov 11 at 20:45
mrgloom
4,987958125
add a comment |
up vote
0
down vote
favorite
Building my project I get error:
ld: library not found for -lglfw
clang: error: linker command failed with exit code 1 (use -v to see invocation)
But I have installed glfw, via brew install glfw
brew list --versions | grep glfw
glfw 3.2.1
ls /usr/local/lib | grep glfw
libglfw.3.2.dylib
libglfw.3.dylib
libglfw.dylib
clang -v
Apple LLVM version 10.0.0 (clang-1000.10.44.4)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
gcc -v
Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/c++/4.2.1
Apple LLVM version 10.0.0 (clang-1000.10.44.4)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
MacOS : 10.14.1 (18B75)
macos glfw
asked Nov 11 at 20:45
mrgloom
4,987958125
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Building my project I get error:
ld: library not found for -lglfw
clang: error: linker command failed with exit code 1 (use -v to see invocation)
But I have installed glfw, via brew install glfw
brew list --versions | grep glfw
glfw 3.2.1
ls /usr/local/lib | grep glfw
libglfw.3.2.dylib
libglfw.3.dylib
libglfw.dylib
clang -v
Apple LLVM version 10.0.0 (clang-1000.10.44.4)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
gcc -v
Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/c++/4.2.1
Apple LLVM version 10.0.0 (clang-1000.10.44.4)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
MacOS : 10.14.1 (18B75)
macos glfw
asked Nov 11 at 20:45
mrgloom
4,987958125
Building my project I get error:
ld: library not found for -lglfw
clang: error: linker command failed with exit code 1 (use -v to see invocation)
But I have installed glfw, via brew install glfw
brew list --versions | grep glfw
glfw 3.2.1
ls /usr/local/lib | grep glfw
libglfw.3.2.dylib
libglfw.3.dylib
libglfw.dylib
clang -v
Apple LLVM version 10.0.0 (clang-1000.10.44.4)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
gcc -v
Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/c++/4.2.1
Apple LLVM version 10.0.0 (clang-1000.10.44.4)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
MacOS : 10.14.1 (18B75)
macos glfw
macos glfw
asked Nov 11 at 20:45
mrgloom
4,987958125
asked Nov 11 at 20:45
mrgloom
4,987958125
asked Nov 11 at 20:45
mrgloom
4,987958125
asked Nov 11 at 20:45
mrgloom
4,987958125
asked Nov 11 at 20:45
mrgloom
4,987958125
4,987958125
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Looks like adding export LIBRARY_PATH=$LIBRARY_PATH:/usr/local/lib to ~/.bash_profile solved the problem, but I'm not sure if it's ellegant solution without side effects.
answered Nov 11 at 20:57
mrgloom
4,987958125
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Looks like adding export LIBRARY_PATH=$LIBRARY_PATH:/usr/local/lib to ~/.bash_profile solved the problem, but I'm not sure if it's ellegant solution without side effects.
answered Nov 11 at 20:57
mrgloom
4,987958125
add a comment |
up vote
0
down vote
Looks like adding export LIBRARY_PATH=$LIBRARY_PATH:/usr/local/lib to ~/.bash_profile solved the problem, but I'm not sure if it's ellegant solution without side effects.
answered Nov 11 at 20:57
mrgloom
4,987958125
add a comment |
up vote
0
down vote
up vote
0
down vote
Looks like adding export LIBRARY_PATH=$LIBRARY_PATH:/usr/local/lib to ~/.bash_profile solved the problem, but I'm not sure if it's ellegant solution without side effects.
answered Nov 11 at 20:57
mrgloom
4,987958125
Looks like adding export LIBRARY_PATH=$LIBRARY_PATH:/usr/local/lib to ~/.bash_profile solved the problem, but I'm not sure if it's ellegant solution without side effects.
answered Nov 11 at 20:57
mrgloom
4,987958125
answered Nov 11 at 20:57
mrgloom
4,987958125
answered Nov 11 at 20:57
mrgloom
4,987958125
answered Nov 11 at 20:57
mrgloom
4,987958125
4,987958125
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53253061%2fmac-os-ld-library-not-found-for-lglfw%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
