6. Writing configure.in

back: documentation and changelogs
forward: what is portability?
fastback: introducing gnu automake
up: top
fastforward: introducing gnu automake
top: autoconf, automake, and libtool
contents: table of contents
index: index
about: about this document

Writing a portable `configure.in' is a tricky business. Since you can put arbitrary shell code into `configure.in' , your options seem overwhelming. There are many questions the first-time Autoconf user asks: What constructs are portable and what constructs aren't portable? How do I decide what to check for? What shouldn't I check for? How do I best use Autoconf's features? What shouldn't I put in `configure.in' ? In what order should I run my checks? When should I look at the name of the system instead of checking for specific features?

This document was generated by Gary V. Vaughan on May, 24 2001 using texi2html

GNU Autoconf, Automake and Libtool
GNU Autoconf, Automake, and Libtool
ISBN: 1578701902
EAN: 2147483647
Year: 2002
Pages: 290

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net