Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Programming
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Databases
Mail Systems
openSolaris
Eclipse Documentation
Techotopia.com
Virtuatopia.com

How To Guides
Virtualization
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Windows
Problem Solutions
Privacy Policy

  




 

 

Back: Guidelines for writing macros
Forward: Testing system features at application runtime
 
FastBack: Implementation specifics
Up: Guidelines for writing macros
FastForward: Implementation specifics
Top: Autoconf, Automake, and Libtool
Contents: Table of Contents
Index: Index
About: About this document

23.3.1 Non-interactive behavior

Autoconf's generated `configure' scripts are designed to be non-interactive -- they should not prompt the user for input. Many users like the fact that `configure' can be used as part of a automated build process. By introducing code into `configure' which prompts a user for more information, you will prohibit unattended operation. Instead, you should use the AC_ARG_ENABLE macro in `configure.in' to add extra options to `configure' or consider runtime configuration (see section 23.3.2 Testing system features at application runtime).


This document was generated by Gary V. Vaughan on February, 8 2006 using texi2html

 
 
  Published under the terms of the Open Publication License Design by Interspire