Chapter 5. Writing a Portable 'configure.in'
Writing a portable 'configure.in' is a tricky business. Because you can put arbitrary shell code into 'configure.in', your options seem overwhelming. The first-time Autoconf user asks many questions: 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?
Get GNU Autoconf, Automake, and Libtool now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
