2 Installation Instructions for Window Maker
8 (ie: I've heard someone has compiled it on...)
10 - Intel/Linux RedHat 4.2 (primary platform)
11 - Intel/Linux other distributions
12 - Sparc/Linux RedHat 5.1
14 - Alpha/Linux RedHat 5.1
16 - Solaris 2.5.1, 2.5.2
23 - AIX 4.1.4 / IBM PowerPC
25 - DEC Alpha/Digital UNIX 4.x
29 Patches to make it work on other platforms are welcome.
35 The following software is required to use Window Maker:
38 Window Maker can be compiled in older versions of X, like X11R5
39 (Solaris) or X11R4 (OpenWindows) but it will not work 100% correctly.
40 In such servers there will not be application icons and you'll have
41 trouble using the dock. Upgrading the client libraries (Xlib, Xt etc)
42 will help if you can't upgrade the server.
44 The following is required to build Window Maker:
47 If you will build Window Maker, make sure you have gcc (or some
48 other ANSI C compiler) and the X header files installed. Specially
49 for newbie Linux users: you must install all X development packages
50 and the gcc suite. Otherwise you won't be able to build any X
51 program, including Window Maker.
53 - autoconf and automake
54 autoconf and automake are not required, but if you have them
55 installed, make sure you have autoconf 2.12 and automake 1.3 or
56 newer. If you have an older version, disable them by temporarily
57 renaming them to something else or uninstalling them from your
60 - lex (or flex) and yacc (or bison)
61 These are used by libPropList. lex is actually not needed since
62 it's output file is included, but either me or automake is stupid,
63 causing the configure script for libPropList to simply abort for no
64 convincent reason if lex is not found.
70 These libraries are not required to make Window Maker work, but they
71 are supported in case you want to use them. Version numbers are those
72 that I have (and therefore, guraranteed to work), but other versions
73 might work too. Tell me if you made wmaker work with some library
74 with a version older than the stated here.
78 Older versions may not work!!!
79 Available at ftp://sunsite.unc.edu/pub/Linux/libs/X/
81 There is builtin support for XPM files, but it will not
82 load images in some uncommon encodings.
84 - libpng 0.96 or newer and zlib
85 For PNG image support.
87 - libtiff 3.4 or newer
88 For TIFF image support.
89 You can get it at ftp://ftp.sgi.com/graphics/tiff
91 - libjpeg 6.0.1 or newer
92 For JPEG image support
94 - libgif 2.2 or libungif
98 If you want to use translated messages, you will need GNU gettext.
99 Other versions of gettext are not compatible and will not work.
100 Get the GNU version from ftp://prep.ai.mit.edu
102 Most of these can be get from ftp.uu.net/pub/graphics
108 These options can be passed to the configure script to enable/disable
109 some Window Maker features. Example:
111 ./configure --enable-kanji
113 will configure Window Maker with kanji (and other multi-byte) characters
117 To get a list of other options, run ./configure --help
119 --enable-sound enable support of sound effects module
121 --disable-xpm disables use of the XPM library even if it is available on
124 --disable-png disables use of PNG library
126 --disable-tiff disable use of TIFF library
128 --disable-gif disable use of GIF library
130 --disable-jpeg disable use of JPEG library
132 --disable-shape disables shaped windows (for oclock, xeyes etc.)
134 --enable-debug adds extra debugging information. Do not use it
135 unless you're debugging Window Maker.
137 --enable-kanji support to display Kanji characters, Korean, Chinese
138 and other languagues that require special characters.
140 --enable-single-icon enables the collapsing of all appicons of the
141 WM_CLASS+WM_INSTANCE into a single one. This feature is not
142 supported at all by the developers. If you have some trouble with it,
143 contact it's author: Christopher Seawood <cls@seawood.org>
145 --disable-shm disable use of the MIT shared memory extension. This will
146 slow down texture generation.
148 --enable-modelock XKB language status lock support. If you don't know
149 what it is you probably don't need it.
152 PLATFORM SPECIFIC NOTES:
153 ========================
154 - SCO Unix - run configure like
155 CFLAGS="-belf -DANSICPP" ./configure
158 If you have gcc installed, run configure as:
159 CPP_PATH="gcc -E -x c" ./configure
160 Sun's cpp lacks some features needed by Window Maker and it can
161 cause problems when parsing the config files.
162 You also might need to use the --with-gfx-libs and --with-gfx-incs
163 to supply the directory where libtiff is located.
166 Make sure you don't have the LANG and LINGUAS environment variables
167 set to en_RN. Also, make sure you have /usr/local/bin in your
168 PATH environment variable, as for some mysterious reason the folks
169 at RedHat did not include it in the default configuration files
173 You will need to have the latest version of Xpmac. Older versions
174 seem to have bugs that cause the system to hang.
177 If you want JPEG and TIFF support, make sure you have libtiff-dev
178 and libjpeg-dev installed.
181 If you installed the Window Maker package from SuSE,
182 uninstall it before trying to compile wmaker or you
185 - MetroX (unknown version)
186 MetroX has a bug that corrupts pixmaps that are set as window
187 backgrounds. If you use MetroX and has weird problems with
188 textures, do not use textures in titlebars. Or use a different
195 Unpack WindowMaker-data.tar.gz and move the pixmaps directory in it
196 to /usr/local/share/pixmaps
198 You can get the file at ftp://ftp.windowmaker.org. This file is optional
199 and only have a few icons.
204 For a quick start, type the following in your shell prompt:
209 then, login as root and type:
213 or if you want to strip the debugging symbols from the binaries and make them
214 smaller, you can instead type:
218 This will build and install Window Maker with default parameters.
220 If you want to customize some compile-time options, you can do the
223 1. (optional) Look at the CONFIGURE OPTIONS section above for the
224 options available. Also run:
228 to get a complete listing of other options that are available.
230 2. Run configure with the options you want. For example, if you
231 want to use the --enable-kanji option, type:
233 ./configure --enable-kanji
235 3. (optional) Edit src/wconfig.h with your favorite text editor
236 and browse through it for some options you might want to change.
238 4. Compile. Just type:
242 5. Login as root (if you can't do that, read the "I don't have the
243 root password :-(" section) and install Window Maker in your system:
248 User specific configuration
249 ---------------------------
251 These instructions do not need to be followed when upgrading Window Maker
252 from an older version, unless stated differently in the NEWS file.
254 Every user on your system that wishes to run Window Maker must do the
257 1. Install Window Maker configuration files in your home directory.
261 wmaker.inst will install Window Maker configuration files and will
262 setup X to automatically launch Window Maker at startup.
266 You can type "man wmaker" to get some general help for configuration
269 Read the User Guide for a more in-depth explanation of Window Maker.
271 You might want to take a look at the FAQ too.
274 I don't have the root password :(
275 ---------------------------------
277 If you can't get superuser privileges (can't be root) you can install
278 wmaker in your own home directory. For that, supply the --prefix option
279 when running configure in step 2 of building Window Maker. You will
280 also need to supply the --with-appspath option, to specify the path for
283 ./configure --prefix=/home/jshmoe --with-appspath=/home/jshmoe/GNUstep/Apps
285 If you use national language support, you must also supply the --with-nlsdir
288 ./configure --prefix=/home/jshmoe --with-appspath=/home/jshmoe/GNUstep/Apps \
289 --with-nlsdir=/home/jshmoe/lib/locale
291 Then make /home/jshmoe/bin be included in your search path and run
298 If you are upgrading from an older version of Window Maker:
300 1. Configure and build Window Maker as always
301 2. Install Window Maker (but do not run wmaker.inst)
302 3. Read the NEWS file and update your configuration files,
308 When you have some trouble during configuration (while running configure),
309 like not being able to use a graphic format library you think you have
310 installed, look at the config.log file for clues of the problem.
313 == Error during build of libPropList
315 make: *** No rule to make target `libPropList.a.c', needed by
316 `libPropList.a.o'. Stop.
318 Make sure the autoconf and automake versions you have installed are at
323 If you are using the RPM's that come with RedHat 4.x, don't use them.
324 It is broken. Uninstall the RPM and reinstall a fresh package from
325 ftp://prep.ai.mit.edu or any mirror.
327 == configure doesn't detect libtiff, or other graphic libraries.
329 Delete config.cache, then rerun configure adding the following options to
330 configure (among the other options you use):
331 --with-gfx-libs="-L/usr/local/lib"
332 --with-gfx-incs="-I/usr/local/include -I/usr/local/include/tiff"
333 Put the paths where your graphic libs and their corresponding header files are
334 located. You can put multiple paths in any of these options, as the example
335 of --with-gfx-incs shows. Just put a space between them.
338 == configure doesn't detect libXpm.
340 * Check if you have a symbolic link from libXpm.so.4.9 to libXpm.so
343 == Segmentation fault on startup
345 * Check if the version of libXPM you have is at least 4.7
347 * Check if you have an updated version of ~/GNUstep/Defaults/WindowMaker
349 If you're not sure, try renaming ~/GNUstep to ~/GNUtmp and then run wmaker.inst
351 == "...: your machine is misconfigured. gethostname() returned (none)"
353 * the hostname of your machine is set to something invalid, that starts
354 with a parenthesis. Do a man hostname for info about how to set it.
357 == The root menu contains only 2 entries. ("XTerm" and "Exit...")
359 * Window Maker is not finding cpp (the C preprocessor). If your cpp is
360 not located in /lib/cpp, edit src/config.h and correct the path in
363 == checking lex output file root... configure: error: cannot find output from true; giving up
365 * Read the REQUIREMENTS section of this file.
368 LOCALES/INTERNATIONALIZATION
369 ============================
371 Window Maker has national language support.
372 To enable national language support, you must compile
373 Window Maker with some additional parameters.
375 0 - You must have the GNU gettext package installed. It can be
376 obtained at ftp://prep.ai.mit.edu/pub/gnu/gettext-nnn.tar.gz
378 Steps 1 to 3 can be skipped if you use the Install script.
380 1 - You have to select the languages you want to support. Set the
381 LINGUAS to the list of locales you want. English is always
384 setenv LINGUAS "pt ja de"
389 export LINGUAS;LINGUAS="pt ja de"
392 The list of supported locales can be found in po/README.
393 English is the default language.
395 Read po/README if you wish to translate and maintain locale files
398 2 - Additionally, if your language uses multi-byte characters, such
399 as Japanese or Korean, you must supply the --enable-kanji flag to configure.
401 3 - Configure, build and install Window Maker normally.
403 4 - To select a particular locale at runtime you must set the LANG
404 environment variable to the locale you want. For example, if you want to set
405 the portuguese locale, you must run
413 in Bourne sh and similars
415 Note: If you have the LC_CTYPE environment variable set, you must
416 unset it before running wmaker.
418 For menu definition files, Window Maker searches for them in the
419 following order (for brazilian portuguese, in this case):
426 5 - If you chose a language that uses multi-byte characters, you must
427 configure the fonts appropriately. Read the manual page for XCreateFontSet
428 to have more details about it. You must change the ~/G/D/WindowMaker file
429 for fonts used in titlebars, menus and other things. For fonts used in
430 dialog windows, change ~/G/D/WMGLOBAL. Note that at the moment you can only
431 supply a single font in WMGLOBAL. The %d in the font names must not be
434 For example, you can specify the following in ~/G/D/WindowMaker:
436 WindowTitleFont = "-*-helvetica-bold-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
437 MenuTitleFont = "-*-helvetica-bold-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
438 MenuTextFont = "-*-helvetica-medium-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
439 IconTitleFont = "-*-helvetica-medium-r-normal-*-8-*,-*-*-medium-r-normal-*-12-*";
440 ClipTitleFont = "-*-helvetica-bold-r-normal-*-10-*,-*-*-medium-r-normal-*-12-*";
441 DisplayFont = "-*-helvetica-medium-r-normal-*-12-*,-*-*-medium-r-normal-*-12-*";
443 and in ~/G/D/WMGLOBAL:
445 SystemFont = "-*-*-medium-r-normal-*-%d-*-*-*-*-*-*-*";
446 BoldSystemFont = "-*-*-medium-r-normal-*-%d-*-*-*-*-*-*-*";
448 The above 2 fonts are only used by applications that use WINGs (WindowMaker