gryf/window-maker.github.io
1
0
Fork 0
mirror of https://github.com/gryf/window-maker.github.io.git synced 2025-12-17 19:20:17 +01:00
Code Issues Projects Releases Wiki Activity

Initial state for the homepage

Browse Source
This commit is contained in:
Carlos R. Mafra
2012-02-04 21:21:32 +00:00
commit a6df0c6b3c
25 changed files with 898 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

112
installation.php Normal file
View File

@@ -0,0 +1,112 @@
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy for Linux (vers 25 March 2009), see www.w3.org" />
<title>Window Maker: Documentation</title>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
<link href="title.css" rel="stylesheet" type="text/css" />
</head>
<body>
<?php include("header.php"); ?><?php include("dock.php"); ?>
<div id="inhalt">
<table width="880" border="0" cellpadding="1" cellspacing="1">
<tr>
<td content="content" colspan="2" valign="top">
<br />
<br />
<h1>Installation Basics</h1>
<h2>Downloading and Extracting</h2>
<p>The first necessary step is to <span class="newWikiWord"><a title="Not found. Click to create this page." href=
"/download.edit">download?</a></span> the Window Maker source distribution. From this point on, we'll assume it has
been retrieved and is residing on the local hard disk. The next step is to extract it, and change into the source
directory.</p>
<pre>
<code># cd /path/to/your/download
# gunzip WindowMaker-0.xx.xx.tar.gz
# tar -xf WindowMaker-0.xx.xx.tar
# cd WindowMaker-0.xx.xx
</code>
</pre>
<p>Now that things are extracted, it's time to look at the relevant pieces of documentation. Most UNIX oriented free
software packages come with a README file, and Window Maker is no exception. The README file contains a summary
overview of what the distribution is, what the various directories contain, and other general information.</p>
<p>Next, we have the ChangeLog which describes a list of changes since the first version. Although it usually lists
technical advancements about the distribution, it is also useful for finding out about bug fixes and recently added
features.</p>
<p>Moving along, we have the NEWS file. For now, we just want to point out its existence. It will become more useful to
novice users over time. Veteran Window Maker users will find it handy for keeping their configuration files up to date,
and learning about various changes which affect Window Maker's behavior.</p>
<p>The two remaining files we need to look at are INSTALL and BUGS. The INSTALL file provides additional information
that is necessary to install Window Maker successfully. The BUGS file contains a list of known Window Maker bugs. If a
user feels they've found a bug in Window Maker, they should consult the BUGS file first. If the bug isn't listed,
proceed to the Bug Tracker and see if its there.</p>
<h2>Compiling</h2>
<p>After extracting the latest version of Window Maker using the previous instructions, the next step is to compile it.
First of all, the configure script should be run. It will test to make sure all the necessary libraries, compilers and
build tools are available on the local system. The configure script allows for various arguments to be passed to it
which relate to Window Maker's installation. For a complete list of all configurable settings, enter:</p>
<pre>
<code># ./configure -help
</code>
</pre>
<p>Three commonly used configuration options are:</p>
<pre>
<code>--prefix=DIR --enable-kde --enable-gnome
</code>
</pre>
<p>The first configuration option lets Window Maker be installed into a non-default installation directory (e.g if
Window Maker cannot be installed system wide for some reason, a user can specify a path under his/her home directory).
The default installation directory is /usr/local/bin for the wmaker binary and /usr/local/GNUstep/Apps for the WPrefs
application (the WPrefs installation directory can be specified by using --with-appspath=DIR). Note that root access
will be needed later on during the installation process if the defaults were used. The second and third configuration
options will enable Window Maker to fully cooperate with <a href="http://kde.org">KDE</a> and <a href=
"http://gnome.org">GNOME</a> respectively.</p>
<p>So if a user johndoe would like to install the wmaker binary into /home/johndoe/wmaker/bin instead of the default
/usr/local/bin, and if he wishes to use Window Maker in cooperation with KDE, the following arguments would be passed
to the configure script:</p>
<pre>
<code> # ./configure --prefix=/home/johndoe/wmaker --enable-kde
</code>
</pre>
<p>After the configure script has been successfully executed, Window Maker can now be compiled with the make command;
simply enter:</p>
<pre>
<code># make
</code>
</pre>
<p>Now is a good time to get a drink while the compilation takes place. Providing the compilation goes well, the final
step is to install the binaries and other support files. This is accomplished by entering: # make install</p>
<p>Note that this is the step that needs to be performed by root if the default installation directory was used, or if
a directory was specified that the running user cannot write to. If the installing user has root access, they should
first become root by issuing <code>su - root</code>. Otherwise, reconfigure and recompile Window Maker by specifying a
different installation directory, or kindly ask the local system administator to install it system wide.</p>
<p>Once Window Maker is installed system-wide, a default configuration can be installed on a per-user basis, through
the bundled installation script, <code>wmaker.inst</code>. Enter <code>wmaker.inst</code> in a terminal emulator to
configure Window Maker for your user.</p>
<p>This script copies the default Window Maker configuration to your user's home directory and sets Window Maker as the
default window manager. It is recommended to create ~/GNUstep before executing the script.</p>
</td>
</tr>
</table>
</div>
</body>
</html>