Closed alex85k closed 11 years ago
This version is not ABI compatible to the origial version (see e.g. 204ef5de4510fae63cb17996f8ba4626839e9503). So to use this luabind version, users will have to recompile from source; and if the source is available, you can also change luabind to luabind09.
However, if you want the library to be found as libluabind.a
you could still do one of the following:
ln
to create an (symbolic) link libluabind.a -> libluabind09.a
.src/CMakeLists.txt
(set_property(TARGET luabind PROPERTY OUTPUT_NAME "luabind09"
).To be honest, I do not really know much about shared libraries on Linux (or any OS other than Windows). Do you think using the CMake VERSION
and SOVERSION
target properties instead of manually setting the name would be better?
OK, if there binary compatibilty with original luabind, then the name may be different, so libluabind09 is good enough name (we should include it in cmake scripts of https://github.com/DennisOSRM/Project-OSRM for example). But in future it may replace original one in binary distribution.
As far as I see, luabind is not shared library (and this is very good - less problems), so user needs to know only the name of .a or .lib file and include path. Changing the name with each version causes more problems with finding library, so let it be luabind09 or (maybe better) be configurable from cmake with default value luabind09.
Is it possible to change generated library name to libluabind.a , or it was changed to libluabind09 intentionally?
Your repository seems to be the most suitable replacement for almost dead "official" one.and many software/CMake modules try to find it without "09".