From 4c5a2b3af214e7a0ec0742b17beb1e719552ecae Mon Sep 17 00:00:00 2001 From: Dan Nicholson Date: Sun, 23 Dec 2007 16:38:18 -0800 Subject: autoconf: Documentation for using the autoconf'd build Most of the options available from configure are documented on the autoconf.html. This page is reached as an alternative provided on the install.html page. An FAQ about why there is no configure script has been removed. --- docs/autoconf.html | 283 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 283 insertions(+) create mode 100644 docs/autoconf.html (limited to 'docs/autoconf.html') diff --git a/docs/autoconf.html b/docs/autoconf.html new file mode 100644 index 0000000000..ab1e21db08 --- /dev/null +++ b/docs/autoconf.html @@ -0,0 +1,283 @@ + + +Compilation and Installation using Autoconf + + + + + + +

Compilation and Installation using Autoconf

+ +
    +
  1. Basic Usage
    2. +
  2. Driver Options
    3. + +
  3. Library Options
    4. + +
  4. Demo Program Options
    5. +
+ + + +

1. Basic Usage

+ +

+The autoconf generated configure script can be used to guess your +platform and change various options for building Mesa. To use the +configure script, type: +

+ +
+    ./configure
+
+ +

+To see a short description of all the options, type ./configure +--help. If you are using a development snapshot and the configure +script does not exist, type make configure to generate it +first. Once you have run ./configure and set the options to +your preference, type: +

+ +
+    make
+
+ +

+This will produce libGL.so and several other libraries depending on the +options you have chosen. Later, if you want to rebuild for a different +configuration run make realclean before rebuilding. +

+ +

+Some of the generic autoconf options are used with Mesa: + +

+

+ +

+There are also a few general options for altering the Mesa build: +

 +

+ + + +

2. Driver Options

+ +

+There are several different driver modes that Mesa can use. These are +described in more detail in the basic +installation instructions. The Mesa driver is controlled through the +configure option --with-driver. There are currently three supported +options in the configure script. +

+ + + + + +

3. Library Options

+ +

+The configure script provides more fine grained control over the GL +libraries that will be built. More details on the specific GL libraries +can be found in the basic installation +instructions. + +

+

+ + + +

4. Demo Program Options

+ +

+There are many demonstration programs in the MesaDemos tarball. If the +programs are available when ./configure is run, a subset of +the programs will be built depending on the driver and library options +chosen. See the directory progs for the full set of demos. + +

+

+ + + -- cgit v1.2.3 From ab57cbaccccb30fd743ba3283251430e6bc3a071 Mon Sep 17 00:00:00 2001 From: Dan Nicholson Date: Wed, 26 Dec 2007 11:12:29 -0600 Subject: autoconf: Helper options for adding GCC 32/64 bit flags Two new configure options to add -m32 or -m64 to the CFLAGS and CXXFLAGS when GCC is in use. By default, the user supplied options are environment variables are respected, but these options are quick helps for the common case of x86/x86_64 using GCC. --- configure.ac | 32 ++++++++++++++++++++++++++++++++ docs/autoconf.html | 7 +++++++ 2 files changed, 39 insertions(+) (limited to 'docs/autoconf.html') diff --git a/configure.ac b/configure.ac index f2f2d75a1a..2acbd67e51 100644 --- a/configure.ac +++ b/configure.ac @@ -79,6 +79,38 @@ AC_ARG_VAR(ARCH_FLAGS, [Additional architecture specific flags for the AC_SUBST(OPT_FLAGS) AC_SUBST(ARCH_FLAGS) +dnl +dnl Hacks to enable 32 or 64 bit build +dnl +AC_ARG_ENABLE(32-bit, + [AS_HELP_STRING([--enable-32-bit], + [build 32-bit libraries @<:@default=auto@:>@])], + enable_32bit="$enableval", + enable_32bit=auto +) +if test "x$enable_32bit" = xyes; then + if test "x$GCC" = xyes; then + CFLAGS="$CFLAGS -m32" + fi + if test "x$GXX" = xyes; then + CXXFLAGS="$CXXFLAGS -m32" + fi +fi +AC_ARG_ENABLE(64-bit, + [AS_HELP_STRING([--enable-64-bit], + [build 64-bit libraries @<:@default=auto@:>@])], + enable_64bit="$enableval", + enable_64bit=auto +) +if test "x$enable_64bit" = xyes; then + if test "x$GCC" = xyes; then + CFLAGS="$CFLAGS -m64" + fi + if test "x$GXX" = xyes; then + CXXFLAGS="$CXXFLAGS -m64" + fi +fi + dnl dnl shared/static libraries, mimic libtool options dnl diff --git a/docs/autoconf.html b/docs/autoconf.html index ab1e21db08..964ff140ab 100644 --- a/docs/autoconf.html +++ b/docs/autoconf.html @@ -124,6 +124,13 @@ available for a few architectures. These will be used by default if one of these architectures is detected. This option ensures that assembly will not be used. +
  • --enable-32-bit, --enable-64-bit - By default, the +build will compile code as directed by the environment variables +CC, CFLAGS, etc. If the compiler is +gcc, these options offer a helper to add the compiler flags +to force 32- or 64-bit code generation as used on the x86 and x86_64 +architectures. +

    • -- cgit v1.2.3