Changes between Version 8 and Version 9 of PortingTips
- Timestamp:
- Nov 17, 2016, 3:11:21 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PortingTips
v8 v9 24 24 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. 26 27 === Have libtool adding a buildlevel string to the DLL === 28 29 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