3:04:33remexrewith cffi, is there a way to "late-bind" which library name is used? e.g. glfw can load as libglfw or libglfw3, but it appears that it gets "frozen" to whatever name was actually found
3:05:18remexreso if my build machine uses libglfw.so.3.1, and my target machine uses libglfw.so.3.2, the binary fails to run
3:05:48remexre(I guess that's not directly related to libglfw vs libglfw3... /shrug)
3:12:11LdBethseems the only thing you do is recompile the project
3:12:49LdBethwith the library symlinks to appripate locations
3:18:57LdBethremexre: you may do that by hacking directly with the lower level FFI provided by the implementation
3:19:43remexreer, what I want is a binary that will work with any libglfw.so
3:20:26remexrelike if I linked C w/ -lglfw, it'd link to libglfw.so and the symlinks would resolve to .so.3.1 or .so.3.2
3:30:24remexreer, my point is that there's a slight behavioral difference between gcc -l and cffi; I don't think there's any fundamental difference in capabilities
3:33:00LdBeththen you just need to redefine the cffi library to use only libglfw.so for example, and expect the target machine does have the symlink setup
3:33:20remexreonce I compile a binary, it /doesn't/ use the symlink
3:33:59remexreI'm trying to make it use the symlink