2 Installation Instructions for Window Maker
8 (ie: I've heard someone has compiled it on...)
10 - Intel GNU/Linux Conectiva 5.9 (beta)
11 - Intel GNU/Linux Slackware
12 - Intel GNU/Linux Debian
13 - Intel GNU/Linux other distributions
14 - Sparc GNU/Linux RedHat 5.1
16 - Alpha GNU/Linux RedHat 5.1
21 - Solaris 2.5.1, 2.5.2
24 - Solaris 2.8 on Ultra Sparc 10 and E450
30 - AIX 4.1.4 / IBM PowerPC
31 - AIX 4.3.1 / IBM CC compiler
32 - AIX 4.3.2 / IBM PowerPC
34 - DEC Alpha/Digital UNIX 4.x
38 - PowerMac / Power MachTen 4.1.1 over MacOS
39 - Amiga 3000 running RedHat Linux 5.1 (Rawhide)
40 - IBM S/390 running Linux
41 - IBM S/390 running Conectiva Linux (experimental)
42 - iBook running Darwin
43 - Darwin PPC / Macos X
44 - Windows NT with Cygwin/XFree86
45 - Sony PlayStation2 running Linux
47 All registered trademarks are registered by their owners. (duh)
49 Patches to make it work on other platforms are welcome.
55 The following software is required to use Window Maker:
58 Window Maker can be compiled in older versions of X, like X11R5
59 (Solaris) or X11R4 (OpenWindows) but it will not work 100% correctly.
60 In such servers there will not be application icons and you'll have
61 trouble using the dock. Upgrading the client libraries (Xlib, Xt etc)
62 will help if you can't upgrade the server.
64 The following is required to build Window Maker:
67 If you will build Window Maker, make sure you have gcc (or some
68 other ANSI C compiler) and the X header files installed. Specially
69 for newbie Linux users: you must install all X development packages
70 and the gcc suite. Otherwise you won't be able to build any X
71 program, including Window Maker.
73 - autoconf, automake and libtool
74 These tools are NOT needed, but IF you have one or
75 more of them installed, make sure you have ALL of the following
76 with exactly these versions:
80 If you have a different version, disable them by temporarily
81 renaming them to something else or uninstalling them from your
82 system. If you don't develop software you don't need them,
83 so you can safely uninstall.
85 - Xft2 and its dependencies (such as freetype2 and fontconfig)
86 For the Antialiased text support.
92 These libraries are not required to make Window Maker work, but they
93 are supported in case you want to use them. Version numbers are those
94 that I have (and therefore, guraranteed to work), but other versions
99 Older versions may not work!!!
100 Available at ftp://sunsite.unc.edu/pub/Linux/libs/X/
102 There is builtin support for XPM files, but it will not
103 load images in some uncommon encodings.
105 - libpng 0.96 or newer and zlib
106 For PNG image support.
107 http://www.cdrom.com/pub/png/
109 - libtiff 3.4 or newer
110 For TIFF image support.
111 You can get it at ftp://ftp.sgi.com/graphics/tiff
113 - libjpeg 6.0.1 or newer
114 For JPEG image support
117 - libgif 2.2 or libungif
118 For GIF image support
119 ftp://prtr-13.ucsc.edu/pub/libungif/
122 If you want to use translated messages, you will need GNU gettext.
123 Other versions of gettext are not compatible and will not work.
124 Get the GNU version from ftp://ftp.gnu.org
131 These options can be passed to the configure script to enable/disable
132 some Window Maker features. Example:
134 ./configure --enable-modelock --disable-gif
136 will configure Window Maker with modelock supported and disable gif support.
139 To get a list of other options, run ./configure --help
142 specify additional paths for libraries to be searched.
143 The -L flag must precede each path, like:
144 --with-libs-from="-L/opt/libs -L/usr/local/lib"
147 specify additional paths for header files to be searched.
148 The -I flag must precede each paths, like:
149 --with-incs-from="-I/opt/headers -I/usr/local/include"
152 disable use of the MIT shared memory extension. This will slow down
153 texture generation a little bit, but in some cases it seems to be
154 necessary due to a bug that manifests as messed icons and textures.
157 disable support for mwm window manager hints
160 remove things that are already supported in desktop environments,
161 like KDE and GNOME. Disabled things are: window list, root
162 applications menu, multiple window selection. Note that you will not
163 be able to exit Window Maker from itself anymore; you will have to
164 use kill with the SIGTERM signal or exit it from KDE. It is not
165 advisable to enable it.
168 XKB language status lock support. If you don't know what it is you
169 probably don't need it.
172 disables use of the XPM library even if it is available on your
176 disables use of PNG library
179 disable use of TIFF library
182 disable use of GIF library
185 disable use of JPEG library
188 disables shaped windows (for oclock, xeyes etc.)
191 PLATFORM SPECIFIC NOTES:
192 ========================
197 From: Anton Ivanov <aivanov@eu.level3.net>
198 To: Marcelo E. Magallon <mmagallo@debian.org>
199 Subject: Re: Is the WindowMaker package working ok on Alpha?
203 > I was reading some docs on the WindowMaker tarball, and found this:
205 > | - DEC/Alpha machines
206 > | You might need to pass the --disable-shm flag to configure,
207 > | like ./configure --disable-shm
209 > is anyone having problems with WindowMaker on Alpha? Can someone
210 > please test this? Should the flag be passed when building on Alpha?
212 Disclaimer: alphas under my command have never run X and are least likely to
213 suddenly start running it anytime soon.
215 Alpha used to have some ridiculously low amount of shared memory
217 So quite a lot of apps used to barf. Namely - cdrecord, mysql server, etc.
219 Check where is yours at the moment and raise it to a more appropriate
220 value by either catting to the appropriate /proc entry or changing the
221 /usr/src/linux/include/asm/shmparam.h.
223 Otherwise the shared memory on alpha should be fully functional and I
224 see no reason to disable it. Mine are bumped up to 32 or more on most
227 And If I recall correctly the comments in that file are actually
228 wrong. Value is not bytes, but in machine size word. For alpha *8.
230 As I said - I do not run X on them so all #include "stdisclaimer.h"
235 - SCO Unix - run configure like
236 CFLAGS="-belf -DANSICPP" ./configure
239 If you have gcc installed, run configure as:
240 CPP_PATH="gcc -E -x c" ./configure
241 Sun's cpp lacks some features needed by Window Maker and it can
242 cause problems when parsing the config files.
243 You also might need to use the --with-libs-from and --with-incs-from
244 to supply the directory where libtiff is located.
245 Someone mailed me that you also must make /usr/local/lib be the
246 first path in LD_LIBRARY_PATH to make it work.
248 If you have a Ultra Creator 3D or some other machine with high-end
249 graphics, be sure to start the X server with the default visual
250 set to 24bpp or you might experience problems with mangled colors.
251 This is a wmaker bug and will be fixed.
253 - GNU/Linux in general
254 Make sure you have /usr/local/lib in /etc/ld.so.conf and that you
255 run ldconfig after installing.
256 Uninstall any packaged version of Window Maker before installing a new
260 RedHat systems have several annoying problems. If you use it,
261 be sure to follow the steps below or Window Maker will not work:
263 * if you installed the Window Maker that comes with RedHat, uninstall
266 * make sure you don't have the LANG and LINGUAS environment variables
269 * make sure you have /usr/local/bin in your PATH environment
272 * make sure you have /usr/local/lib in /etc/ld.so.conf before running
276 You will need to have the latest version of Xpmac. Older versions
277 seem to have bugs that cause the system to hang.
280 If you want JPEG and TIFF support, make sure you have libtiff-dev
281 and libjpeg-dev installed.
284 If you installed the Window Maker package from SuSE,
285 uninstall it before trying to compile wmaker or you
288 - MetroX (unknown version)
289 MetroX has a bug that corrupts pixmaps that are set as window
290 backgrounds. If you use MetroX and has weird problems with
291 textures, do not use textures in titlebars. Or use a different
299 For a quick start, type the following in your shell prompt:
304 then, login as root and type:
309 or if you want to strip the debugging symbols from the binaries and make them
310 smaller, you can instead type:
315 This will build and install Window Maker with default parameters.
317 If you want to customize some compile-time options, you can do the
320 1. (optional) Look at the CONFIGURE OPTIONS section above for the
321 options available. Also run:
325 to get a complete listing of other options that are available.
327 2. Run configure with the options you want. For example, if you
328 want to use the --enable-modelock option, type:
330 ./configure --enable-modelock
332 3. (optional) Edit src/wconfig.h with your favorite text editor
333 and browse through it for some options you might want to change.
335 4. Compile. Just type:
339 5. Login as root (if you can't do that, read the "I don't have the
340 root password :-(" section) and install Window Maker in your system:
345 User specific configuration
346 ---------------------------
348 These instructions do not need to be followed when upgrading Window Maker
349 from an older version, unless stated differently in the NEWS file.
351 Every user on your system that wishes to run Window Maker must do the
354 1. Install Window Maker configuration files in your home directory.
358 wmaker.inst will install Window Maker configuration files and will
359 setup X to automatically launch Window Maker at startup.
363 You can type "man wmaker" to get some general help for configuration
366 Read the User Guide for a more in-depth explanation of Window Maker.
368 You might want to take a look at the FAQ too.
372 Installing the extras package
373 -----------------------------
375 Unpack WindowMaker-extra-<version-number>.tar.gz in /usr/local/share
377 You can get the file at ftp://ftp.windowmaker.org. This file is optional
378 and only have a few icons, and themes. Look for the latest <version-number>
380 Also there is a WindowMaker-extra.readme to instruct you where that package
385 I don't have the root password :(
386 ---------------------------------
388 If you can't get superuser privileges (can't be root) you can install
389 wmaker in your own home directory. For that, supply the --prefix option
390 when running configure in step 2 of building Window Maker. You will
391 also need to supply the --with-appspath option, to specify the path for
394 ./configure --prefix=/home/jshmoe --with-appspath=/home/jshmoe/GNUstep/Apps
397 Then make /home/jshmoe/bin be included in your search PATH, add
398 /home/jshmoe/lib to your LD_LIBRARY_PATH environment variable and run
401 Of course, /home/jshmoe is supposed to be replaced with your actual home
409 If you are upgrading from an older version of Window Maker:
411 1. Configure and build Window Maker as always
412 2. Install Window Maker (but do not run wmaker.inst)
413 3. Read the NEWS file and update your configuration files if necessary.
419 When you have some trouble during configuration (while running configure),
420 like not being able to use a graphic format library you think you have
421 installed, look at the config.log file for clues of the problem.
424 == Error with loading fonts, even if they exist.
426 Try rebuilding without NLS support.
428 == Error when configuring
430 ltconfig: unrecognized option `--no-reexec'
431 Try `ltconfig --help' for more information.
432 configure: error: libtool configure failed
434 remove the --no-reexec option from aclocal.m4 and reconfigure
435 Also make sure the autoconf and automake versions you have installed are:
440 Note that it must not be libtool 1.2b, it must be libtool 1.3,
443 == configure doesn't detect libtiff, or other graphic libraries.
445 Delete config.cache, then rerun configure adding the following options to
446 configure (among the other options you use):
447 --with-libs-from="-L/usr/local/lib"
448 --with-incs-from="-I/usr/local/include -I/usr/local/include/tiff"
449 Put the paths where your graphic libs and their corresponding header files are
450 located. You can put multiple paths in any of these options, as the example
451 of --with-incs-from shows. Just put a space between them.
454 == configure doesn't detect libXpm.
456 * Check if you have a symbolic link from libXpm.so.4.9 to libXpm.so
459 == Segmentation fault on startup
461 * Check if the version of libXPM you have is at least 4.7
463 * Check if you have an updated version of ~/GNUstep/Defaults/WindowMaker
465 If you're not sure, try renaming ~/GNUstep to ~/GNUtmp and then run wmaker.inst
467 == "...: your machine is misconfigured. gethostname() returned (none)"
469 * the hostname of your machine is set to something invalid, that starts
470 with a parenthesis. Do a man hostname for info about how to set it.
473 == The root menu contains only 2 entries. ("XTerm" and "Exit...")
475 * Window Maker is not finding cpp (the C preprocessor). If your cpp is
476 not located in /lib/cpp, edit src/config.h and correct the path in
479 == checking lex output file root... configure: error: cannot find output from true; giving up
481 * Read the REQUIREMENTS section of this file.
484 LOCALES/INTERNATIONALIZATION
485 ============================
487 Window Maker has national language support. To enable national language
488 support, you must compile Window Maker with some additional parameters.
491 0 - You must have the GNU gettext package installed. It can be
492 obtained at ftp://prep.ai.mit.edu/pub/gnu/gettext-nnn.tar.gz
494 Steps 1 to 3 can be skipped if you use the Install script.
496 1 - You have to select the languages you want to support. Set the
497 LINGUAS to the list of locales you want. English is always
500 setenv LINGUAS "pt ja de"
505 export LINGUAS;LINGUAS="pt ja de"
508 The list of supported locales can be found in po/README.
509 English is the default language.
511 Read po/README if you wish to translate and maintain locale files
514 2 - Additionally, if your language uses multi-byte characters, such
515 as Japanese or Korean, you must set the MultiByteText option to YES
516 in ~/GNUstep/Defaults/WMGLOBAL
518 3 - Configure, build and install Window Maker normally.
520 4 - To select a particular locale at runtime you must set the LANG
521 environment variable to the locale you want. For example, if you want to set
522 the portuguese locale, you must run
530 in Bourne sh and similars
532 Note: If you have the LC_CTYPE environment variable set, you must
533 unset it before running wmaker.
535 For menu definition files, Window Maker searches for them in the
536 following order (for brazilian portuguese, in this case):