X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=docs%2Fautoconf.html;h=5c29e5ee2c6edb601fbbda1c096af8bb1871a867;hb=f4d2d491522aea8c7de46311c3f5e9c588307dd2;hp=ab1e21db08f9d36deecb52d41f98e4e3d84ab502;hpb=4c5a2b3af214e7a0ec0742b17beb1e719552ecae;p=mesa.git diff --git a/docs/autoconf.html b/docs/autoconf.html index ab1e21db08f..5c29e5ee2c6 100644 --- a/docs/autoconf.html +++ b/docs/autoconf.html @@ -1,34 +1,33 @@ - - -Compilation and Installation using Autoconf - - - + + + + + Compilation and Installation using Autoconf + + +
+

The Mesa 3D Graphics Library

+
+ + +

Compilation and Installation using Autoconf

    -
  1. Basic Usage
    2. -
  2. Driver Options
    3. +

  3. Basic Usage

    4. +

  4. Driver Options

    -
  5. Library Options
    6. - -
  6. Demo Program Options
- -

1. Basic Usage

+

1. Basic Usage

The autoconf generated configure script can be used to guess your @@ -43,9 +42,12 @@ configure script, type:

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: +script does not exist, type ./autogen.sh to generate it +first. If you know the options you want to pass to +configure, you can pass them to autogen.sh. It +will run configure with these options after it is +generated. Once you have run configure and set the options +to your preference, type: 

@@ -60,173 +62,194 @@ configuration run make realclean before rebuilding.
 
 

 Some of the generic autoconf options are used with Mesa:
-
-
    
-
  • --prefix=PREFIX - This is the root directory where
+
    
+
    
+
    --prefix=PREFIX
    
+
    This is the root directory where
 files will be installed by make install. The default is
-/usr/local.
-
    • 
-
  • --exec-prefix=EPREFIX - This is the root directory
+/usr/local.
    
+
+
+
    --exec-prefix=EPREFIX
    
+
    This is the root directory
 where architecture-dependent files will be installed. In Mesa, this is
 only used to derive the directory for the libraries. The default is
-${prefix}.
-
    • 
-
  • --libdir=LIBDIR - This option specifies the directory
+${prefix}.
    
+
+
+
    --libdir=LIBDIR
    
+
    This option specifies the directory
 where the GL libraries will be installed. The default is
 ${exec_prefix}/lib. It also serves as the name of the
 library staging area in the source tree. For instance, if the option
 --libdir=/usr/local/lib64 is used, the libraries will be
 created in a lib64 directory at the top of the Mesa source
-tree.
-
    • 
-
  • --enable-static, --disable-shared - By default, Mesa
+tree.
    
+
+
+
    --sysconfdir=DIR
    
+
    This option specifies the directory where the configuration
+files will be installed. The default is ${prefix}/etc.
+Currently there's only one config file provided when dri drivers are
+enabled - it's drirc.
    
+
    
+
+
    --enable-static, --disable-shared
    
+
    By default, Mesa
 will build shared libraries. Either of these options will force static
 libraries to be built. It is not currently possible to build static and
-shared libraries in a single pass.
-
    • 
-
  • CC, CFLAGS, CXX, CXXFLAGS - These environment variables
+shared libraries in a single pass.
    
+
+
+
    CC, CFLAGS, CXX, CXXFLAGS
    
+
    These environment variables
 control the C and C++ compilers used during the build. By default,
-gcc and g++ are used with the options
-"-g -O2".
-
    • 
-
  • LDFLAGS - An environment variable specifying flags to
-pass when linking programs. These are normally empty, but can be used
-to direct the linker to use libraries in nonstandard directories. For
-example, LDFLAGS="-L/usr/X11R6/lib".
-
    • 
-
  • PKG_CONFIG_PATH - When available, the
-pkg-config utility is used to search for external libraries
+gcc and g++ are used and the debug/optimisation
+level is left unchanged.
    
+
+
+
    LDFLAGS
    
+
    An environment variable specifying flags to
+pass when linking programs. These should be empty and
+PKG_CONFIG_PATH is recommended to be used instead. If needed
+it can be used to direct the linker to use libraries in nonstandard
+directories. For example, LDFLAGS="-L/usr/X11R6/lib".
    
+
    
+
+
    PKG_CONFIG_PATH
    
+
    The
+pkg-config utility is a hard requirement for cofiguring and
+building mesa. It is used to search for external libraries
 on the system. This environment variable is used to control the search
 path for pkg-config. For instance, setting
 PKG_CONFIG_PATH=/usr/X11R6/lib/pkgconfig will search for
 package metadata in /usr/X11R6 before the standard
-directories.
-
    • 
-

-

+directories.

+
+
 
 

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

-

+assembly will not be used.

+
+
+
--build=

+
--host=

+
By default, the build will compile code for the architecture that
+it's running on. In order to build cross-compile Mesa on a x86-64 machine
+that is to run on a i686, one would need to set the options to:

+
+
--build=x86_64-pc-linux-gnu --host=i686-pc-linux-gnu

+
+Note that these can vary from distribution to distribution. For more
+information check with the
+
+autoconf manual.
+Note that you will need to correctly set PKG_CONFIG_PATH as well.
+
+
+
In some cases a single compiler is capable of handling both architectures
+(multilib) in that case one would need to set the CC,CXX variables
+appending the correct machine options. Seek your compiler documentation for
+further information -
+ gcc
+machine dependent options

 
+
In addition to specifying correct PKG_CONFIG_PATH for the target
+architecture, the following should be sufficient to configure multilib Mesa

 
-
-
2. Driver Options

+./configure CC="gcc -m32" CXX="g++ -m32" --build=x86_64-pc-linux-gnu --host=i686-pc-linux-gnu ...
+

+
+
+
+
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.
+configure options --enable-xlib-glx, --enable-osmesa,
+and --enable-dri.
 

 
-
+
 
 
-
-
3. Library Options

+
3. Library Options

 
 

 The configure script provides more fine grained control over the GL
@@ -234,50 +257,6 @@ 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.
-
-
    
-
  • --with-demos=DEMOS,DEMOS,... - This option allows a
-specific set of demo programs to be built. For example,
---with-demos="xdemos,slang". Beware that if this option is
-used, it will not be ensured that the necessary GL libraries will be
-available.
-
    • 
-
  • --without-demos - This completely disables building the
-demo programs. It is equivalent to --with-demos=no.
-
    • 
-

-

-
+