Add one link
[whome.git] / installation.php
1 <html xmlns="">
2 <head>
3 <meta name="generator" content="HTML Tidy for Linux (vers 25 March 2009), see" />
5 <title>Window Maker: Documentation</title>
6 <meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
7 <link href="title.css" rel="stylesheet" type="text/css" />
8 </head>
10 <body>
11 <?php include("dock.php"); ?>
12 <?php include("header.php"); ?>
14 <div>
15 <table class="inner" border="0" cellpadding="1" cellspacing="1">
16 <tr>
17 <td content="content" colspan="2" valign="top">
18 <br />
19 <br />
21 <h3>Installation Basics</h3>
23 <h3>Downloading and Extracting</h3>
25 <p>The first necessary step is to <a href="">download</a>
26 the Window Maker source distribution. From this point on, we'll assume it has
27 been retrieved and is residing on the local hard disk. The next step is to extract it, and change into the source
28 directory.</p>
29 <pre>
30 <code># cd /path/to/your/download
31 # gunzip WindowMaker-0.xx.xx.tar.gz
32 # tar -xf WindowMaker-0.xx.xx.tar
33 # cd WindowMaker-0.xx.xx
34 </code>
35 </pre>
37 <p>Now that things are extracted, it's time to look at the relevant pieces of documentation. Most UNIX oriented free
38 software packages come with a README file, and Window Maker is no exception. The README file contains a summary
39 overview of what the distribution is, what the various directories contain, and other general information.</p>
41 <p>Moving along, we have the NEWS file. For now, we just want to point out its existence. It will become more useful to
42 novice users over time. Veteran Window Maker users will find it handy for keeping their configuration files up to date,
43 and learning about various changes which affect Window Maker's behavior.</p>
45 <p>The two remaining files we need to look at are INSTALL and BUGS. The INSTALL file provides additional information
46 that is necessary to install Window Maker successfully. The BUGS file contains a list of known Window Maker bugs. If a
47 user feels they've found a bug in Window Maker, they should consult the BUGS file first. If the bug isn't listed,
48 proceed to the Bug Tracker and see if its there.</p>
50 <h3>Compiling</h3>
52 <p>After extracting the latest version of Window Maker using the previous instructions, the next step is to compile it.
53 First of all, the configure script should be run. It will test to make sure all the necessary libraries, compilers and
54 build tools are available on the local system. The configure script allows for various arguments to be passed to it
55 which relate to Window Maker's installation. For a complete list of all configurable settings, enter:</p>
56 <pre>
57 <code>$ ./configure --help
58 </code>
59 </pre>
61 <p>Commonly used configuration options are:</p>
62 <pre>
63 <code>--prefix=DIR --enable-modelock --enable-xinerama --enable-silent-rules
64 </code>
65 </pre>
67 <p>The first configuration option lets Window Maker be installed into a non-default installation directory (e.g if
68 Window Maker cannot be installed system wide for some reason, a user can specify a path under his/her home directory).
69 The default installation directory is /usr/local/bin. Note that root access
70 will be needed later on during the installation process if the defaults were used.</p>
72 <p>So if a user johndoe would like to install the wmaker binary into /home/johndoe/wmaker/bin instead of the default
73 /usr/local/bin, the following argument would be passed to the configure script:</p>
74 <pre>
75 <code> $ ./configure --prefix=/home/johndoe/wmaker
76 </code>
77 </pre>
79 <p>After the configure script has been successfully executed, Window Maker can now be compiled with the make command;
80 simply enter:</p>
81 <pre>
82 <code>$ make
83 </code>
84 </pre>
86 <p>The final step is to install the binaries and other support files. This is accomplished by entering: # make install</p>
88 <p>Note that this is the step that needs to be performed by root if the default installation directory was used, or if
89 a directory was specified that the running user cannot write to. If the installing user has root access, they should
90 first become root by issuing <code>su - root</code>. Otherwise, reconfigure and recompile Window Maker by specifying a
91 different installation directory, or kindly ask the local system administator to install it system wide.</p>
93 <p>Once Window Maker is installed system-wide, a default configuration can be installed on a per-user basis, through
94 the bundled installation script, <code>wmaker.inst</code>. Enter <code>wmaker.inst</code> in a terminal emulator to
95 configure Window Maker for your user.</p>
97 <p>This script copies the default Window Maker configuration to your user's home directory and sets Window Maker as the
98 default window manager. It is recommended to create ~/GNUstep before executing the script.</p>
100 <h3> Final tweaks</h3>
102 <p> Edit your ~/.xinitrc to load your newly installed Window Maker using the line
103 <code> exec /usr/local/bin/wmaker</code>.</p>
105 <p> Generate a new root menu (accessible with F12) with <code>wmgenmenu</code>, for example
106 <pre>
107 <code> $ wmgenmenu > $HOME/GNUstep/Defaults/WMRootMenu </code>
108 </pre>
111 <p> Another recommended step is to install a few dockapps like wmvolman, wmmixer and wmsystemtray which allow one to
112 easily mount external media on /media among other things. Visit <a href=""> dockapps</a>
113 for many more choices.</p>
115 <br><br><br>
116 </td>
117 </tr>
118 </table>
120 <?php include("footer.php"); ?>
123 </body>
124 </html>