Installation of the software packages requires root login, which can be obtained easily via the superuser/setuser command: su - (see, man su).
If you have a version of XFree86 installed already, you may want to move it or delete it. However, installing over an existing X is generally OK and preserves any programs or libraries you might have installed into the X directories (not that you should really do that):
cd /usr mv X11R6 X11R6-old cd /etc mv X11 X11-old -- you may have an X directory in /var also cd /var mv X11R6 X11R6-old
If these locations are not correct for your distribution of Linux, you will have to look around your filesystem a bit - try looking in /var
cd /usr/src mkdir release cd release tar -xvzf X402src-1.tgz tar -xvzf X402src-2.tgz tar -xvzf X402src-3.tgz tar -xvzf doctools-1.2.tar.gz -- unpack the man pages (actually, glx pages are already present) cd /usr/src tar -xvzf mangl.tar.Z tar -xvzf manglu.tar.Z
A file has to be edited to allow these man pages to compile/install with the rest of the distribution:
cd /usr/src/release/xc/doc/man/GL Edit the file: Imakefile SUBDIRS = glx gl glu
When you unpacked the man*.tar.Z files above, two new directories where added: gl glu
cd /usr/src/release cd doctools -- Having this variable set confuses the sgml docs build. -- With it unset, the build uses the proper defaults. unset $SGML_CATALOG_FILES make make install -- Note: doctools installs the perl program sgmlfmt to -- /usr/local/bin. It looks for the perl executable -- at /usr/local/bin/perl. If perl is installed -- on your system at /usr/bin/perl, then it will not -- find perl and the sgml docs build will fail! -- Make a symlink if needed (or edit the script): cd /usr/local/bin ln -s /usr/bin/perl perl cd /usr/src/release cd xc/config/cf vi host.def -- add the following three lines to host.def: -- #define HasSgmlFmt YES -- #define BuildAllDocs YES -- #define HasZlib YES -- See the README file in doctools and xc/config/cf. -- HasZlib YES instructs XFree86 not to build and install -- it's own old zlib. If you do not have zlib installed -- (check /usr/lib/libz*), then omit the HasZlib line or -- go download it and install it first: -- http://www.info-zip.org/pub/infozip/zlib/ -- A common zlib conflict occurs when a system already -- has zlib installed and XFree86 installs it's also. -- In this case, deleting /usr/X11R6/lib/libz.a fixes -- the problem. cd /usr/src/release/xc make World -- before installing, make sure you have moved -- or deleted prior installation of X -- unless you are sure you want to just overwrite make install make install.man -- make symlinks cd /usr/include ln -s ../X11R6/include/DPS DPS ln -s ../X11R6/include/GL GL ln -s ../X11R6/include/X11 X11 ln -s ../X11R6/include/bitmaps bitmaps cd .. ln -s X11R6 X11
Add /usr/X11R6/lib to your /etc/ld.so.conf file, then run the command ldconfig to update /etc/ld.so.cache so the libraries will be visible.
The GL/GLX/GLU HTML documentation is located at /usr/src/release/xc/doc/hardcopy/GL. This directory can be copied as follows:
cd /usr/src/release/xc/doc/hardcopy cp -r GL /usr/X11R6/lib/X11/doc/html
cd /usr/X11R6/lib/X11/doc/html ln -s manindex5.html manindex5x.html
When X is up and running (later), try using the xman program to see that the gl,glx,glu and glut man pages are in section 3. If you have KDE2, khelpcenter allows man-page browsing.
Note: This gives you the libGLU* and libglut* files that are missing in XFree86. XFree86 only comes with the OpenGL core library, libGL (based on Mesa). This also installs Mesa's libGL, but we will delete that since it is to be replaced by the Nvidia libGL.
It's best to uninstall any old Mesa version you may have installed before installing a new Mesa. Uninstalling software can be a dangerous operation, so know what you are doing!
To completely uninstall any Mesa libs that may have come with Slackware:
-- see what will be removed first rpm -e --test Mesa | less -- if ok, proceed rpm -e Mesa
apt-get remove Mesa
-- IF you are going to use the project GLUT distribution of GLUT, then -- unpack the Glut-3.7 packages ... -- Mesa's compile looks for it cd /usr/src tar -xvzf glut-3.7.tar.gz tar -xvzf glut_data-3.7.tar.gz -- IF you are using this GLUT, use the --with-glut=/usr/src/glut-3.7 -- parameter with Mesa's ./configure below in addition to the --prefix cd /usr/src tar -xvzf MesaLib-3.4.tar.gz tar -xvzf MesaDemos-3.4.tar.gz cd Mesa-3.4 ./configure --prefix=/usr make make install ldconfig
At this point, Mesa installed its own version of the glx.h include files over the ones that XFree86 installed. This will cause some programs to fail to compile and is corrected by copying the XFree86 GL include files from the X source back to your system:
cp /usr/src/release/xc/include/GL/*.h /usr/X11R6/include/GL
-- delete the libGL.* files that come with XFree86 / Mesa 3.4 ... -- the nvidia libGL.* should replace them cd /usr/X11R6/lib rm libGL.* cd modules/extensions rm libGL* rm libglx* cd /usr/lib rm libGL.* cd /usr/src tar -xvzf NVIDIA_kernel-0.9-769.tar.gz tar -xvzf NVIDIA_GLX-0.9-769.tar.gz cd NVIDIA_kernel-0.9-769
Tip: If you experience problems starting X, see the files TNT_USERS_README and M64_USERS_README. These files explain how to tweak the kernel driver. They were written to fix problems with TNT and TNT2 M64 cards but these tweaks are reported to help the GeForce2 MX also. Try bypassing the BIOS as explained in M64_USERS_README.
make cd .. cd NVIDIA_GLX-0.9-769 make ldconfig -- Make a basic XF86Config file using the "nv" driver: cd /etc/X11 xf86config -- Follow the prompts and fill in the information xf86config asks for. -- Select the Nvidia GeForce or appropriate name. -- You can test X with this XF86Config file, or continue for OpenGL: -- You must edit XF86Config and set the following: vi XF86Config Load "glx" Replace 'driver "nv"' with 'driver "nvidia"' Put "1600x1200" first (or your preferred screen resolution) Copy ttf fonts from Windows into a font directory and add a font path. Use ttmkfdir (check freshmeat.net) to a fonts.dir file. A good place to keep your own fonts is /usr/local/share/fonts ... -- Nvidia drivers do NOT use the dri module - don't load it. -- You may like to edit /etc/X11/xinit/xinitrc to have run "startkde" -- or "gnome-session" instead of twm. -- Note: /usr/include/GL should be a symlink to /usr/X11R6/include/GL
Specifying "nvidia" for the driver in the XF86Config makes that take effect each time you startx. But the NVdriver kernel driver will have to be loaded each time your system boots using:
alias char-major-195 NVdriver
-- for Qt, there is no "make install", just place the source -- where you want it to live: cd /usr/local tar -xvzf qt-x11-2.2.4.tar.gz ln -s qt-2.2.4 qt cd qt
Read the INSTALL file about environment variables to setup before you try to build Qt. You can add the following to /etc/profile:
QTDIR=/usr/local/qt PATH=$PATH:$QTDIR/bin MANPATH=$MANPATH:$QTDIR/man LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$QTDIR/lib export QTDIR PATH MANPATH LD_LIBRARY_PATH
-- note: configure has some options you can try, to see them -- see ./configure --help ./configure -- NOTE: when you run make as suggested on the next line, you may -- encounter a make error that halts the build IF you run make -- from outside X. The program $QTDIR/bin/uic (the User Interface Compiler) -- may Segmentation Fault when run from a Linux console. You can run -- "startx" and use the twm (tiny window manager) and xterm (or whatever you -- might have setup for X) to run the rest of the Qt build. If for some -- reason twm is not even available, then you can run "XFree86 &", use -- "CTRL-ALT-F1" to get to a console, start an xterm as -- "xterm -display localhost:0.0 &", then switch back to X with "ALT-F7". make -- Only for old versions of Qt before 2.1.0 or so ... -- compile the opengl extension -- Note that in qt 2.2.0 on, the OpenGL support has been moved out of extensions -- and is now a standard part of the library that is installed if configure -- finds OpenGL installed on your system. If you were to not want OpenGL -- support in Qt, you'd have to pass the -no-opengl option to configure. cd extensions/opengl/src -- Check the Makefile and ensure there are not Mesa references. make ldconfig cd ../examples -- Try compiling and running the examples.
If you installed the MesaDemos package along with the Mesa 3.4, then you have already installed GLUT 3.7 since it is included with MesaDemos. However, you may be interested in installing the GLUT manpages and you can skip right to the "Install GLUT manual pages", below ...
Installing GLUT is a bit tricky. I'm not too familiar with imake, the program that it uses to manage the Makefiles, and didn't quite see how to get GLUT to install to where I wanted it (/usr/lib, but MesaDemos will do this without any trouble though). It can be done manually anyhow:
cd /usr/src tar -xvzf glut-3.7.tar.gz cd glut-3.7 Read the file: README.linux cd linux READ the file: README cp Glut.cf .. cd .. Edit Glut.cf: remove any Mesa references. Replace any -lMesaGL -lMesaGLU with -lGL -lGLU if needed. In particular, replace: OPENGL = $(TOP)/../lib/libMesaGL.so GLU = $(TOP)/../lib/libMesaGLU.so with: OPENGL = -lGL GLU = -lGLU ./mkmkfiles.imake cd lib/glut cp /usr/src/glut-3.7/linux/Makefile . Edit the Makefile: remove any Mesa references. Replace any -lMesaGL -lMesaGLU with -lGL -lGLU if needed. In particular, replace: OPENGL = $(TOP)/../lib/libMesaGL.so GLU = $(TOP)/../lib/libMesaGLU.so with: OPENGL = -lGL GLU = -lGLU make ln -s libglut.so.3.7 libglut.so ln -s libglut.so.3.7 libglut.so.3 cp -d libglut.* /usr/lib cd .. cd gle -- make a shared lib for libgle make gcc -shared -o libgle.so.3.7 *.o ln -s libgle.so.3.7 libgle.so ln -s libgle.so.3.7 libgle.so.3 cp -d libgle.* /usr/lib cd .. cd mui -- make a shared lib for libmui make gcc -shared -o libmui.so.3.7 *.o ln -s libmui.so.3.7 libmui.so ln -s libmui.so.3.7 libmui.so.3 cp -d libmui.* /usr/lib -- Install the GLUT manual pages (not included with MesaDemos) cd /usr/src/glut-3.7 make SUBDIRS=man Makefile cd man/glut make install.man ldconfig cd ../../progs/demos/ideas -- edit the Makefile, change OPENGL = -lGL and GLU = -lGLU make ./ideas -- test compiling some demos -- take a look at which libraries have to be linked (-lX11 ...) in -- the Makefiles. Qt's tmake program available at www.troll.no -- is a quick way to make a Makefile but you have to edit it -- and add the -l needed.
If you already have a Java JDK/SDK or JRE, that is, a Java/Software Development Kit or Java Runtime Environment, installed, then you may have to take care to uninstall them or leave them alone!
It is recommended that you have the lastest version of Netscape 4.7x, which at this time of writing, is 4.76, if you plan to install the Java PlugIn for netscape. It works, but you may (or may not) experience Segmentation Faults when leaving a page that contained a Java 3D applet - KDE Konqueror 2.1 works well.
Assuming you are logged in as root and have downloaded the Java packages from blackdown.org into the root home directory, /root, do:
Install the Java 2 SDK (1.2.2) and Java 3D (1.2) extension:
cd /usr/local tar -xvyf ~/j2sdk-1.2.2-FCS-linux-i386-glibc-2.1.3.tar.bz2 ln -s jdk1.2.2 jdk cd jdk tar -xvyf ~/java3d1_2-FCS-linux-i386-sdk.tar.bz2 cd jre/lib/ext cp j3d* .. cp vecmath.jar .. cd /usr/local chown -R root:root jdk1.2.2
Edit /etc/profile, add:
JAVA_HOME=/usr/local/jdk PATH=$PATH:$JAVA_HOME/bin export JAVA_HOME PATH
Install the Java PlugIn for netscape:
-- source profile to set JAVA_HOME and PATH source /etc/profile cd chmod u+x JavaPlugIn-1.2.2-FCS-linux-i386-glibc-2.1.3.run ./JavaPlugIn-1.2.2-FCS-linux-i386-glibc-2.1.3.run -- each user has to run this file to install the plugin -- it is per user, not global netscape &
The next step is to configure the Java PlugIn. It comes with a configuration applet.
netscape ~/.netscape/java/ControlPanel.html & -- the Control Panel for JavaPlugIn should load
Test Java 3D demos:
cd $JAVA_HOME/demo/java3d/GearTest java GearBox & -- runs as normal java application netscape GearBox_plugin.html & -- runs in netscape as an applet
If you experience trouble with Java, you can try deleting ~/.java and related files in your home directory, then try again. These files left over from a prior Java installation can cause problems.
If all works well, you should have a complete Java Developement and Runtime Environment for both normal apps and high-performance 3D apps. See http://java.sun.com/ for further information about Java and the Java 3D extension.