diff --git a/docs/autoconf.html b/docs/autoconf.html new file mode 100644 index 0000000000000000000000000000000000000000..ab1e21db08f9d36deecb52d41f98e4e3d84ab502 --- /dev/null +++ b/docs/autoconf.html @@ -0,0 +1,283 @@ + + +Compilation and Installation using Autoconf + + + + + + +

Compilation and Installation using Autoconf

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

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. + +

+

+ + + diff --git a/docs/faq.html b/docs/faq.html index 89496c8404d4f6bd75ada643f17e470cdef2410a..30239dcab40d1d640a792e5407aeb23e0d4024ed 100644 --- a/docs/faq.html +++ b/docs/faq.html @@ -187,24 +187,7 @@ has Mesa packages (like RPM or DEB) which you can easily install.

-

2.2 Running configure; make doesn't Work

-

-Mesa no longer supports GNU autoconf/automake. Why? -

- -

-Now Mesa again uses a conventional Makefile system (as it did originally). -Basically, each Makefile in the tree includes one of the configuration -files from the config/ directory. -The config files specify all the variables for a variety of popular systems. -

- - -

2.3 I get undefined symbols such as bgnpolygon, v3f, etc...

+

2.2 I get undefined symbols such as bgnpolygon, v3f, etc...

You're application is written in IRIS GL, not OpenGL. IRIS GL was the predecessor to OpenGL and is a different thing (almost) @@ -213,7 +196,7 @@ Mesa's not the solution.

-

2.4 Where is the GLUT library?

+

2.3 Where is the GLUT library?

GLUT (OpenGL Utility Toolkit) is in the separate MesaGLUT-x.y.z.tar.gz file. If you don't already have GLUT installed, you should grab the MesaGLUT @@ -222,7 +205,7 @@ package and compile it with the rest of Mesa. -

2.5 What's the proper place for the libraries and headers?

+

2.4 What's the proper place for the libraries and headers?

On Linux-based systems you'll want to follow the 1.1 Compilation

-Mesa may be compiled in several different ways: +Mesa is built by reading Makefile stubs from the configs directory. +There are configurations for many Unix variants and different Mesa +options. Type make from the top-level directory to see a list of +supported system configurations. Alternatively, an autoconf system can +be used to create a Makefile stub for your system. See the autoconf instructions for more details. Mesa +may be compiled in several ways using the predefined configurations: