| www.delorie.com/gnu/docs/libtool/libtool_72.html | search |
![]() Buy GNU books! | |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Here are a few tricks that you can use in order to make maintainership easier:
ltmain.in, I keep a permanent libtool script in my
PATH, which sources ltmain.in directly.
The following steps describe how to create such a script, where
/home/src/libtool is the directory containing the libtool source
tree, /home/src/libtool/libtool is a libtool script that has been
configured for your platform, and ~/bin is a directory in your
PATH:
trick$ cd ~/bin trick$ sed '/^# ltmain\.sh/q' /home/src/libtool/libtool > libtool trick$ echo '. /home/src/libtool/ltmain.in' >> libtool trick$ chmod +x libtool trick$ libtool --version ltmain.sh (GNU @PACKAGE@) @VERSION@@TIMESTAMP@ trick$ |
The output of the final `libtool --version' command shows that the
ltmain.in script is being used directly. Now, modify
~/bin/libtool or /home/src/libtool/ltmain.in directly in
order to test new changes without having to rerun configure.
| webmaster donations bookstore | delorie software privacy |
| Copyright © 2003 by The Free Software Foundation | Updated Jun 2003 |