search for: autobook

Hi, > I hope this brief tutorial has helped. Feel free to ask questions. > Further details can be found in Makefile.rules. Although I don't think it uses automake, chapter 13 of http://sources.redhat.com/autobook/autobook/autobook_toc.html may still be useful since it gives a similar overview. Cheers, Ralph.

...form. (Optionally, there can be a ‘cleanup.win’ script as well. Both should be shell scripts to be executed by ash, which is a minimal version of Bourne-style sh.) " Which tool do I need to write config script on windows? Do I need an autoconf-cygwin solution? ( http://sources.redhat.com/autobook/autobook/autobook_242.html#SEC242 ) or just a port of autoconf available on sourceforge? Thanks in advance Christophe [[alternative HTML version deleted]]

...> relevant if configure is passed an interpreter path by the user > which doesn't exist (as my debian packaging makefile just did). A problem is that "test -x" isn't portable, at least according to the goat book - see the bottom of this page: http://sources.redhat.com/autobook/autobook/autobook_216.html I don't know which platforms it isn't supported on, but this message suggests it's not a totally academic concern: http://mail.gnu.org/archive/html/autoconf/2002-12/msg00098.html With your fix to use $PYTHON instead of python, test -x isn't actually nee...

Hi Tanya, The first thing you need to understand is that there are multiple make targets to support this feature. I'll briefly describe each here so you have an overview and then delve into the details later. * distdir - builds the distribution directory from which the distribution will be packaged * dist - builds each of the distribution tarballs (tar.gz,

Reid, Could you explain in detail what make dist does? :) I'd like to see how it can be integrated into the release process. Thanks, Tanya