On Wed, 2004-01-28 at 13:02, Patrick Welche wrote: > On Wed, Jan 28, 2004 at 10:01:27AM +0000, Gary V. Vaughan wrote: > > ~From libtool configure.ac (which uses maj.min[.mic][alpha]): > > > > LT_MAJOR=`echo "AC_PACKAGE_VERSION" | sed ['s,\..*$,,g']` > > LT_MINOR=`echo "AC_PACKAGE_VERSION" | sed ['s,^[0-9]*\.\([0-9]*\).*$,\1,']` > > LT_MICRO=`echo "AC_PACKAGE_VERSION" \ > > | sed ['s,^[0-9]*\.[0-9]*\(\.[0-9]*\).*$,\1,']` > > LT_ALPHA=`echo "AC_PACKAGE_VERSION" | sed ['s,^[0-9.]*,,']` > > > > Note the lack of $AC_PACKAGE_VERSION, AC_PACKAGE_VERSION is an m4 macro! > > After this you could add, say: > > > > VERSION=$LT_MAJOR.$LT_MINOR.$LT_MICRO > > On a tangent - is there an "easy" way of finding out the libtool.m4 > version without having to process libtoolize --version? A sort of > AC_PREREQ(2.59) equivalent? This is to deal with left overs in packages > which use the autobook technique of: > This is something I'm intending to work on, along with making sure ltmain.sh and libtool.m4 came from the same source. I've worked out in my head how to make it all work, was going to do it yesterday but got distracted and rewrote the pkg-config m4 stuff instead :-) > 11.3 Using libtoolize > ... > $ cp /usr/share/libtool/libtool.m4 ./acinclude.m4 > $ aclocal > > so keep doing that if have old libtool, else do something better.. > > On a further tangent, shouldn't something better be, set AC_CONFIG_MACRO_DIR, > run libtoolize, then presumably use aclocal, however: > This is what happens with libtoolize on CVS HEAD currently, it copies libtool.m4 (and other relevant files) into AC_CONFIG_MACRO_DIR for you. Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
Attachment:
signature.asc
Description: This is a digitally signed message part
