#51618: glfw @3.2: install_name is not set properly -----------------------+------------------------- Reporter: sakari@… | Owner: michaelld@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: glfw | -----------------------+------------------------- Changes (by ryandesign@…): * owner: macports-tickets@… => michaelld@… * priority: High => Normal * keywords: library,build,linking => Old description:
I just updated to GLFW 3.2 release from the previous one. Now when building my project, even when using pkg-config to get the correct library directories, the resulting binary points to
lib/libglfw.3.dylib (compatibility version 3.0.0, current version 3.2.0)
When obviously, it should point to
'/opt/local/lib'
pkg-config gives the correct info:
pkg-config --libs glfw3 -L/opt/local/lib -lglfw
And linkin works, but when I try to run my resulting binary,
dyld: Library not loaded: lib/libglfw.3.dylib Referenced from: /Users/sakari/dvl/geometrify/geometrify/src/build/geometrify Reason: image not found fish: “build/geometrify -s scripts/t...” terminated by signal SIGTRAP (Trace or breakpoint trap)
I can fix this temporarily easily of course, but I have no idea why this happens, maybe the path is wrong in the build process ?
New description: I just updated to GLFW 3.2 release from the previous one. Now when building my project, even when using pkg-config to get the correct library directories, the resulting binary points to lib/libglfw.3.dylib (compatibility version 3.0.0, current version 3.2.0) When obviously, it should point to '/opt/local/lib' pkg-config gives the correct info: {{{ pkg-config --libs glfw3 -L/opt/local/lib -lglfw }}} And linkin works, but when I try to run my resulting binary, {{{ dyld: Library not loaded: lib/libglfw.3.dylib Referenced from: /Users/sakari/dvl/geometrify/geometrify/src/build/geometrify Reason: image not found fish: “build/geometrify -s scripts/t...” terminated by signal SIGTRAP (Trace or breakpoint trap) }}} I can fix this temporarily easily of course, but I have no idea why this happens, maybe the path is wrong in the build process ? -- Comment: Sounds like the `install_name` is not being set correctly. -- Ticket URL: <https://trac.macports.org/ticket/51618#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X