Changes between Version 11 and Version 12 of PortingTips

Timestamp:

Nov 28, 2016, 12:27:18 AM (8 years ago)

Author:

dmik

Comment:

--

PortingTips

@@ -25 +25 @@
 A proper solution here is to force `libtool` use a special, short version of the base name for the DLL file (and only for it — all other files, such as the import library name, should carry the original name so that the linker can find it). This is done using the `-shortname` libtool option. Where to add it varies from project to project but the typical place is the _la_LDFLAGS variable in `Makefile.am` for the library. See r1232 for a real-life example.
 
-=== Have libtool adding a buildlevel string to the DLL ===
+=== Have libtool add a buildlevel string to the DLL ===
 
 With the latest `libtool` it is possible to have a buildlevel string built into a dll. To do so you need to teach the `Makefile` how to handle it. Most likely it is the best practice to change `Makefile.am` and then do a `sh -c "autoreconf -fvi"`. How to adjust a `Makefile.am` can be seen here: r1823