Jump to content

  • Log In with Google      Sign In   
  • Create Account


Why do i need to use libglfw.dylib if I am statically linking against GLFW?


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
No replies to this topic

#1 Aitorman   Members   -  Reputation: 126

Like
0Likes
Like

Posted 27 July 2012 - 07:08 AM

Hello everyone,
I'm trying to use GLFW in mac osx. I have already built the project (using "make cocoa" on the terminal), which generates libglfw.a, libglfw.dylib, and libglfw.pc.in. In my Xcode project I've added the Cocoa and OpenGL frameworks (in Build Phases/Link binary with libraries), and the libglfw.a static library. If i'm not mistaken (I'm new to this so I probably am), this should be enough to statically link against GLFW, and I should not need the dynamic library, but when I try to run the program, it says that libglfw.dylib could not be found. My question is, ¿why do i need the dynamic library If i am linking against GLFW statically?

Sponsor:



Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS