diff --git a/en/gnome/docs/gnome_porting.sgml b/en/gnome/docs/gnome_porting.sgml index 8239a59258..842201acbe 100644 --- a/en/gnome/docs/gnome_porting.sgml +++ b/en/gnome/docs/gnome_porting.sgml @@ -1,6 +1,6 @@ - + %gnomeincludes; %includes; @@ -90,6 +90,12 @@
Most, if not all, GNOME applications depend on GNU's libtool. They also use the GNU configure system. If your port installs - shared libraries, you should add USE_LIBTOOL_VER= 13 to - your port's Makefile. This takes care of most of the libtool - requirements, but will not prevent things such as .la files - from being installed. To ensure a proper shared library - installation, also consider adding lthack to - USE_GNOME line in port Makefile. This prevents the - installation of .la files and ensures that - ${PTHREAD_LIBS} will be passed to the linker.
- -Some applications may use newer versions of libtool, and - lthack may not be sufficient. This is usually - apparent during the linking phase where errors such as the - following are thrown:
- --libtool: ../../libsomelib.la not found -- -
In this case, you should replace - USE_LIBTOOL_VER=13 with GNU_CONFIGURE=yes, - and patch the port's ltmain.sh script directly. - Unfortunately, there is not one patch for - ltmain.sh that will work for every port. - Therefore, you should adapt one of the existing - patch-ltmain.sh files to work with your port.
+ shared libraries, and includes an ltmain.sh script + in its ${WRKSRC} directory, you should add + USE_LIBTOOL_VER=15 to your port's Makefile. + However, if your port uses custom LIBTOOLFLAGS, you + must use USE_INC_LIBTOOL_VER=13 instead. If you have + to use USE_INC_LIBTOOL_VER, you must also add + lthack to USE_GNOME. In general, though, + lthack is deprecated, and should only be used if + absolutely necessary.