-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't build on Ubuntu 13.04 #42
Comments
Did you have a static or dynamic glfw3 library? It used to be the case that you needed dynamic, but that seems to be changing over time. |
Quite frankly, no idea. I grabbed the glfw3 sources, generated the make files, compiled and installed. Not sure what's the default there. |
Use cmake -DBUILD_SHARED_LIBS=ON. Right now we're only using static lib on mac os because of the mentioned Most linux distributions come with the dyanmic library.
|
I used cmake -DBUILD_SHARED_LIBS=ON. Still could not go install. Is there any method one could tell whether the compiled libglfw.so and libglfw3.a is static or dynamic? |
*.so = shared object can you try to do this: export LD_LIBRARY_PATH="/path/to/libglfw.so/"
go build github.com/go-gl/glfw3 |
It's weird. I do have those .so files: :/usr/local/lib$ ls Still cannot build. export LD_LIBRARY_PATH="/usr/local/lib/libglfw.so/" I rm -rf the glfw3 directory, and go get again, still those errors: github.com/go-gl/glfw3/usr/local/lib/libglfw3.a(context.c.o): In function |
It should be export LD_LIBRARY_PATH="/usr/local/lib/" But if you don't want to do this everytime you're using glfw3, you can configure glfw with |
export still has no effect:
I make the glfw3 with the option as you told, everything is ok now.
Thank you very much. |
no problem |
After trying to install it on Ubuntu, the only way I could find was to change the cgo line in glfw.go to look like this:
//#cgo linux LDFLAGS: -lglfw3 -lGL -lm -lGLU -lX11 -lXi -lXxf86vm -lXrandr
Maybe it should be possible to use a cgo pkg-config instead of that line. Haven't tried though
The text was updated successfully, but these errors were encountered: