2 Installation Instructions for Window Maker
8 (ie: I've heard someone has compiled it on...)
10 - Intel GNU/Linux Slackware 3.5 (primary platform)
11 - Intel GNU/Linux other distributions
12 - Sparc GNU/Linux RedHat 5.1
14 - Alpha GNU/Linux RedHat 5.1
18 - Solaris 2.5.1, 2.5.2
25 - AIX 4.1.4 / IBM PowerPC
26 - AIX 4.3.1 / IBM CC compiler
27 - AIX 4.3.2 / IBM PowerPC
29 - DEC Alpha/Digital UNIX 4.x
33 - PowerMac / Power MachTen 4.1.1 over MacOS
34 - Amiga 3000 running RedHat Linux 5.1 (Rawhide)
36 Patches to make it work on other platforms are welcome.
38 If the latest version doesn't work for you, try 0.19.3,
39 which is known to be pretty stable on many platforms.
45 The following software is required to use Window Maker:
48 Window Maker can be compiled in older versions of X, like X11R5
49 (Solaris) or X11R4 (OpenWindows) but it will not work 100% correctly.
50 In such servers there will not be application icons and you'll have
51 trouble using the dock. Upgrading the client libraries (Xlib, Xt etc)
52 will help if you can't upgrade the server.
54 The following is required to build Window Maker:
57 If you will build Window Maker, make sure you have gcc (or some
58 other ANSI C compiler) and the X header files installed. Specially
59 for newbie Linux users: you must install all X development packages
60 and the gcc suite. Otherwise you won't be able to build any X
61 program, including Window Maker.
64 This library can be found in ftp://ftp.windowmaker.org/pub/libs
65 or in ftp://ftp.gnome.org/pub/libPropList
66 Install it before building Window Maker.
68 - autoconf, automake and libtool
69 These tools are not needed, but IF you have one or
70 more of them installed, make sure you have ALL of the following
71 with exactly these versions:
75 If you have a different version, disable them by temporarily
76 renaming them to something else or uninstalling them from your
77 system. If you don't develop software you don't need them,
78 so you can safely uninstall.
80 - lex (or flex) and yacc (or bison)
81 These are used by libPropList. lex is actually not needed since
82 it's output file is included, but either me or automake is stupid,
83 causing the configure script for libPropList to simply abort for no
84 convincent reason if lex is not found.
90 These libraries are not required to make Window Maker work, but they
91 are supported in case you want to use them. Version numbers are those
92 that I have (and therefore, guraranteed to work), but other versions
97 Older versions may not work!!!
98 Available at ftp://sunsite.unc.edu/pub/Linux/libs/X/
100 There is builtin support for XPM files, but it will not
101 load images in some uncommon encodings.
103 - libpng 0.96 or newer and zlib
104 For PNG image support.
106 - libtiff 3.4 or newer
107 For TIFF image support.
108 You can get it at ftp://ftp.sgi.com/graphics/tiff
110 - libjpeg 6.0.1 or newer
111 For JPEG image support
113 - libgif 2.2 or libungif
114 For GIF image support
117 If you want to use translated messages, you will need GNU gettext.
118 Other versions of gettext are not compatible and will not work.
119 Get the GNU version from ftp://prep.ai.mit.edu
121 Most of these can be get from ftp.uu.net/pub/graphics
127 These options can be passed to the configure script to enable/disable
128 some Window Maker features. Example:
130 ./configure --enable-kanji
132 will configure Window Maker with kanji (and other multi-byte) characters
136 To get a list of other options, run ./configure --help
139 support to display Kanji characters, Korean, Chinese and other
140 languagues that require special characters.
143 enables the collapsing of all appicons of the WM_CLASS+WM_INSTANCE
144 into a single one. This feature is not supported at all by the
145 developers. If you have some trouble with it, contact it's author:
146 Christopher Seawood <cls@seawood.org>
149 disable use of the MIT shared memory extension. This will slow down
150 texture generation a little bit, but in some cases it seems to be
151 necessary due to a bug that manifests as messed icons and textures.
154 disable support for mwm window manager hints
157 enable support for OPEN LOOK(tm) window manager hints
160 enable support for GNOME window manager hints
163 enable support for kde/kwm window manager hints
166 remove things that are already supported in desktop environments,
167 like KDE and GNOME. Disabled things are: window list, root
168 applications menu, multiple window selection. Note that you will not
169 be able to exit Window Maker from itself anymore; you will have to
170 use kill with the SIGTERM signal or exit it from KDE. It is not
171 advisable to enable it.
174 XKB language status lock support. If you don't know what it is you
175 probably don't need it.
178 enable support of sound effects module
181 disables use of the XPM library even if it is available on your
185 disables use of PNG library
188 disable use of TIFF library
191 disable use of GIF library
194 disable use of JPEG library
197 disables shaped windows (for oclock, xeyes etc.)
200 Do not use it unless you know what you're doing.
203 PLATFORM SPECIFIC NOTES:
204 ========================
205 - SCO Unix - run configure like
206 CFLAGS="-belf -DANSICPP" ./configure
209 If you have gcc installed, run configure as:
210 CPP_PATH="gcc -E -x c" ./configure
211 Sun's cpp lacks some features needed by Window Maker and it can
212 cause problems when parsing the config files.
213 You also might need to use the --with-gfx-libs and --with-gfx-incs
214 to supply the directory where libtiff is located.
216 If you have a Ultra Creator 3D or some other machine with high-end
217 graphics, be sure to start the X server with the default visual
218 set to 24bpp or you might experience problems with mangled colors.
219 This is a wmaker bug and will be fixed.
221 - GNU/Linux in general
222 Make sure you have /usr/local/lib in /etc/ld.so.conf and that you
223 run ldconfig after installing.
226 RedHat systems have several annoying problems. If you use it,
227 be sure to follow the steps below or Window Maker will not work:
229 * make sure you don't have the LANG and LINGUAS environment variables
232 * make sure you have /usr/local/bin in your PATH environment
233 variable, as for some mysterious reason the folks at RedHat did not
234 include it in the default configuration files in RH 5.x;
236 * make sure you have /usr/local/lib in /etc/ld.so.conf before running
239 * if you have problems that mention an error message with --no-reexec
240 uninstall libtool-1.2b and install libtool-1.2 instead. libtool-1.2
241 can be found in ftp.gnu.org Also read the TROUBLESHOOTING section;
243 * if you installed the Window Maker package from RedHat and are
244 installing a new version of it by hand (compiling yourself), uninstall
245 the package from RedHat before.
247 * make a symbolic link from /usr/X11 to /usr/X11R6
248 (type ln -s /usr/X11R6 /usr/X11 ) and make sure you have a symbolic
249 link from /usr/include/X11 to /usr/X11R6/include/X11 (if not,
250 type ln -s /usr/X11R6/include/X11 /usr/include/X11 )
253 You will need to have the latest version of Xpmac. Older versions
254 seem to have bugs that cause the system to hang.
257 If you want JPEG and TIFF support, make sure you have libtiff-dev
258 and libjpeg-dev installed.
261 If you installed the Window Maker package from SuSE,
262 uninstall it before trying to compile wmaker or you
265 - MetroX (unknown version)
266 MetroX has a bug that corrupts pixmaps that are set as window
267 backgrounds. If you use MetroX and has weird problems with
268 textures, do not use textures in titlebars. Or use a different
274 Unpack WindowMaker-data.tar.gz and move the pixmaps directory in it
275 to /usr/local/share/pixmaps
277 You can get the file at ftp://ftp.windowmaker.org. This file is optional
278 and only have a few icons.
283 For a quick start, type the following in your shell prompt:
288 then, login as root and type:
293 or if you want to strip the debugging symbols from the binaries and make them
294 smaller, you can instead type:
299 This will build and install Window Maker with default parameters.
301 If you want to customize some compile-time options, you can do the
304 1. (optional) Look at the CONFIGURE OPTIONS section above for the
305 options available. Also run:
309 to get a complete listing of other options that are available.
311 2. Run configure with the options you want. For example, if you
312 want to use the --enable-kanji option, type:
314 ./configure --enable-kanji
316 3. (optional) Edit src/wconfig.h with your favorite text editor
317 and browse through it for some options you might want to change.
319 4. Compile. Just type:
323 5. Login as root (if you can't do that, read the "I don't have the
324 root password :-(" section) and install Window Maker in your system:
329 User specific configuration
330 ---------------------------
332 These instructions do not need to be followed when upgrading Window Maker
333 from an older version, unless stated differently in the NEWS file.
335 Every user on your system that wishes to run Window Maker must do the
338 1. Install Window Maker configuration files in your home directory.
342 wmaker.inst will install Window Maker configuration files and will
343 setup X to automatically launch Window Maker at startup.
347 You can type "man wmaker" to get some general help for configuration
350 Read the User Guide for a more in-depth explanation of Window Maker.
352 You might want to take a look at the FAQ too.
355 I don't have the root password :(
356 ---------------------------------
358 If you can't get superuser privileges (can't be root) you can install
359 wmaker in your own home directory. For that, supply the --prefix option
360 when running configure in step 2 of building Window Maker. You will
361 also need to supply the --with-appspath option, to specify the path for
364 ./configure --prefix=/home/jshmoe --with-appspath=/home/jshmoe/GNUstep/Apps
367 Then make /home/jshmoe/bin be included in your search path and run
374 If you are upgrading from an older version of Window Maker:
376 1. Configure and build Window Maker as always
377 2. Install Window Maker (but do not run wmaker.inst)
378 3. Read the NEWS file and update your configuration files,
384 When you have some trouble during configuration (while running configure),
385 like not being able to use a graphic format library you think you have
386 installed, look at the config.log file for clues of the problem.
389 == Error when configuring
391 ltconfig: unrecognized option `--no-reexec'
392 Try `ltconfig --help' for more information.
393 configure: error: libtool configure failed
395 remove the --no-reexec option from aclocal.m4 and libPropList/aclocal.m4
397 Also make sure the autoconf and automake versions you have installed are:
402 Note that it must not be libtool 1.2b, it must be libtool 1.2,
405 == Cant find proplist.h or libPropList.something
407 Download and install libPropList from the places pointed to
408 somewhere else in this file.
411 == configure doesn't detect libtiff, or other graphic libraries.
413 Delete config.cache, then rerun configure adding the following options to
414 configure (among the other options you use):
415 --with-gfx-libs="-L/usr/local/lib"
416 --with-gfx-incs="-I/usr/local/include -I/usr/local/include/tiff"
417 Put the paths where your graphic libs and their corresponding header files are
418 located. You can put multiple paths in any of these options, as the example
419 of --with-gfx-incs shows. Just put a space between them.
422 == configure doesn't detect libXpm.
424 * Check if you have a symbolic link from libXpm.so.4.9 to libXpm.so
427 == Segmentation fault on startup
429 * Check if the version of libXPM you have is at least 4.7
431 * Check if you have an updated version of ~/GNUstep/Defaults/WindowMaker
433 If you're not sure, try renaming ~/GNUstep to ~/GNUtmp and then run wmaker.inst
435 == "...: your machine is misconfigured. gethostname() returned (none)"
437 * the hostname of your machine is set to something invalid, that starts
438 with a parenthesis. Do a man hostname for info about how to set it.
441 == The root menu contains only 2 entries. ("XTerm" and "Exit...")
443 * Window Maker is not finding cpp (the C preprocessor). If your cpp is
444 not located in /lib/cpp, edit src/config.h and correct the path in
447 == checking lex output file root... configure: error: cannot find output from true; giving up
449 * Read the REQUIREMENTS section of this file.
452 LOCALES/INTERNATIONALIZATION
453 ============================
455 Window Maker has national language support.
456 To enable national language support, you must compile
457 Window Maker with some additional parameters.
459 0 - You must have the GNU gettext package installed. It can be
460 obtained at ftp://prep.ai.mit.edu/pub/gnu/gettext-nnn.tar.gz
462 Steps 1 to 3 can be skipped if you use the Install script.
464 1 - You have to select the languages you want to support. Set the
465 LINGUAS to the list of locales you want. English is always
468 setenv LINGUAS "pt ja de"
473 export LINGUAS;LINGUAS="pt ja de"
476 The list of supported locales can be found in po/README.
477 English is the default language.
479 Read po/README if you wish to translate and maintain locale files
482 2 - Additionally, if your language uses multi-byte characters, such
483 as Japanese or Korean, you must supply the --enable-kanji flag to configure.
485 3 - Configure, build and install Window Maker normally.
487 4 - To select a particular locale at runtime you must set the LANG
488 environment variable to the locale you want. For example, if you want to set
489 the portuguese locale, you must run
497 in Bourne sh and similars
499 Note: If you have the LC_CTYPE environment variable set, you must
500 unset it before running wmaker.
502 For menu definition files, Window Maker searches for them in the
503 following order (for brazilian portuguese, in this case):
510 5 - If you chose a language that uses multi-byte characters, you must
511 configure the fonts appropriately. Read the manual page for XCreateFontSet
512 to have more details about it. You must change the ~/G/D/WindowMaker file
513 for fonts used in titlebars, menus and other things. For fonts used in
514 dialog windows, change ~/G/D/WMGLOBAL. The %d in the font names must not be
515 removed. You can also use the supplied wsetfont script for the task.
516 Read the script itself for instructions.
518 For example, you can specify the following in ~/G/D/WindowMaker:
520 WindowTitleFont = "-*-helvetica-bold-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
521 MenuTitleFont = "-*-helvetica-bold-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
522 MenuTextFont = "-*-helvetica-medium-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
523 IconTitleFont = "-*-helvetica-medium-r-normal-*-8-*,-*-*-medium-r-normal-*-12-*";
524 ClipTitleFont = "-*-helvetica-bold-r-normal-*-10-*,-*-*-medium-r-normal-*-12-*";
525 DisplayFont = "-*-helvetica-medium-r-normal-*-12-*,-*-*-medium-r-normal-*-12-*";
527 and in ~/G/D/WMGLOBAL:
529 SystemFont = "-*-*-medium-r-normal-*-%d-*-*-*-*-*-*-*";
530 BoldSystemFont = "-*-*-medium-r-normal-*-%d-*-*-*-*-*-*-*";
532 The above 2 fonts are only used by applications that use WINGs (WindowMaker