Hi,
For legacy reasons a ODBC driver is installed into "/usr/lib" or
"/usr/local/lib" even if more to be considered a "plugin" than a
normal shared library (i.e. it will be loaded with dlopen()).
Together with building and installing the driver, I also want to put
the path of the installed driver into a script generated in the build.
A script to register the driver with an ODBC manager. But the script
needs to contain the path to the driver install location, including
possible ".so", ".dylib", ".sl" or similar shared library extension.
I was thinking of something like in the make file
# Put the real installation path into the script to register the driver
register : register.in
DRIVER_PATH=`libtool --print-shared-install-path libdriver.la`
sed 's/@DRIVER_PATH@/$$DRIVER_PATH/' < register.in > register
Is this possible? Or doesn't even libtool know about the final file
name of the shared library?
kent
--
Kent Boortz, Senior Production Engineer
MySQL AB, www.mysql.com
Office: +46 18 174400 ext. 4450 (VoIP)
Office: +46 19 182931
Mobile: +46 70 2791171
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
