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 - Windows NT with Cygwin/XFree86
44 - Sony PlayStation2 running Linux
46 All registered trademarks are registered by their owners. (duh)
48 Patches to make it work on other platforms are welcome.
54 The following software is required to use Window Maker:
57 Window Maker can be compiled in older versions of X, like X11R5
58 (Solaris) or X11R4 (OpenWindows) but it will not work 100% correctly.
59 In such servers there will not be application icons and you'll have
60 trouble using the dock. Upgrading the client libraries (Xlib, Xt etc)
61 will help if you can't upgrade the server.
63 The following is required to build Window Maker:
66 If you will build Window Maker, make sure you have gcc (or some
67 other ANSI C compiler) and the X header files installed. Specially
68 for newbie Linux users: you must install all X development packages
69 and the gcc suite. Otherwise you won't be able to build any X
70 program, including Window Maker.
73 This library can be found in ftp://ftp.windowmaker.org/pub/libs
74 or in ftp://ftp.gnome.org/pub/libPropList
75 Install it before building Window Maker.
77 - autoconf, automake and libtool
78 These tools are NOT needed, but IF you have one or
79 more of them installed, make sure you have ALL of the following
80 with exactly these versions:
84 If you have a different version, disable them by temporarily
85 renaming them to something else or uninstalling them from your
86 system. If you don't develop software you don't need them,
87 so you can safely uninstall.
89 - lex (or flex) and yacc (or bison)
90 These are used by libPropList. lex is actually not needed since
91 it's output file is included, but either me or automake is stupid,
92 causing the configure script for libPropList to simply abort for no
93 convincent reason if lex is not found.
99 These libraries are not required to make Window Maker work, but they
100 are supported in case you want to use them. Version numbers are those
101 that I have (and therefore, guraranteed to work), but other versions
105 - libXPM 4.7 or newer
106 Older versions may not work!!!
107 Available at ftp://sunsite.unc.edu/pub/Linux/libs/X/
109 There is builtin support for XPM files, but it will not
110 load images in some uncommon encodings.
112 - libpng 0.96 or newer and zlib
113 For PNG image support.
114 http://www.cdrom.com/pub/png/
116 - libtiff 3.4 or newer
117 For TIFF image support.
118 You can get it at ftp://ftp.sgi.com/graphics/tiff
120 - libjpeg 6.0.1 or newer
121 For JPEG image support
124 - libgif 2.2 or libungif
125 For GIF image support
126 ftp://prtr-13.ucsc.edu/pub/libungif/
128 - libHermes 1.3.2 or newer
129 For faster pixel conversion in the wraster library
130 (its used only in some conversions - for TrueColor visuals)
131 http://www.clanlib.org/hermes/
134 If you want to use translated messages, you will need GNU gettext.
135 Other versions of gettext are not compatible and will not work.
136 Get the GNU version from ftp://ftp.gnu.org
143 These options can be passed to the configure script to enable/disable
144 some Window Maker features. Example:
146 ./configure --enable-kde --enable-gnome
148 will configure Window Maker with KDE and GNOME supported compiled in.
151 To get a list of other options, run ./configure --help
154 specify additional paths for libraries to be searched.
155 The -L flag must precede each path, like:
156 --with-libs-from="-L/opt/libs -L/usr/local/lib"
159 specify additional paths for header files to be searched.
160 The -I flag must precede each paths, like:
161 --with-incs-from="-I/opt/headers -I/usr/local/include"
164 enables the collapsing of all appicons of the WM_CLASS+WM_INSTANCE
165 into a single one. This feature is not supported at all by the
166 developers. If you have some trouble with it, contact it's author:
167 Christopher Seawood <cls@seawood.org>
170 disable use of the MIT shared memory extension. This will slow down
171 texture generation a little bit, but in some cases it seems to be
172 necessary due to a bug that manifests as messed icons and textures.
175 disable support for mwm window manager hints
178 enable support for OPEN LOOK(tm) window manager hints
181 enable support for GNOME window manager hints
184 enable support for kde/kwm window manager hints
187 remove things that are already supported in desktop environments,
188 like KDE and GNOME. Disabled things are: window list, root
189 applications menu, multiple window selection. Note that you will not
190 be able to exit Window Maker from itself anymore; you will have to
191 use kill with the SIGTERM signal or exit it from KDE. It is not
192 advisable to enable it.
195 XKB language status lock support. If you don't know what it is you
196 probably don't need it.
199 enable support of sound effects module
202 disables use of the XPM library even if it is available on your
206 disables use of PNG library
209 disable use of TIFF library
212 disable use of GIF library
215 disable use of JPEG library
218 disables shaped windows (for oclock, xeyes etc.)
221 PLATFORM SPECIFIC NOTES:
222 ========================
227 From: Anton Ivanov <aivanov@eu.level3.net>
228 To: Marcelo E. Magallon <mmagallo@debian.org>
229 Subject: Re: Is the WindowMaker package working ok on Alpha?
233 > I was reading some docs on the WindowMaker tarball, and found this:
235 > | - DEC/Alpha machines
236 > | You might need to pass the --disable-shm flag to configure,
237 > | like ./configure --disable-shm
239 > is anyone having problems with WindowMaker on Alpha? Can someone
240 > please test this? Should the flag be passed when building on Alpha?
242 Disclaimer: alphas under my command have never run X and are least likely to
243 suddenly start running it anytime soon.
245 Alpha used to have some ridiculously low amount of shared memory
247 So quite a lot of apps used to barf. Namely - cdrecord, mysql server, etc.
249 Check where is yours at the moment and raise it to a more appropriate
250 value by either catting to the appropriate /proc entry or changing the
251 /usr/src/linux/include/asm/shmparam.h.
253 Otherwise the shared memory on alpha should be fully functional and I
254 see no reason to disable it. Mine are bumped up to 32 or more on most
257 And If I recall correctly the comments in that file are actually
258 wrong. Value is not bytes, but in machine size word. For alpha *8.
260 As I said - I do not run X on them so all #include "stdisclaimer.h"
265 - SCO Unix - run configure like
266 CFLAGS="-belf -DANSICPP" ./configure
269 If you have gcc installed, run configure as:
270 CPP_PATH="gcc -E -x c" ./configure
271 Sun's cpp lacks some features needed by Window Maker and it can
272 cause problems when parsing the config files.
273 You also might need to use the --with-libs-from and --with-incs-from
274 to supply the directory where libtiff is located.
275 Someone mailed me that you also must make /usr/local/lib be the
276 first path in LD_LIBRARY_PATH to make it work.
278 If you have a Ultra Creator 3D or some other machine with high-end
279 graphics, be sure to start the X server with the default visual
280 set to 24bpp or you might experience problems with mangled colors.
281 This is a wmaker bug and will be fixed.
283 - GNU/Linux in general
284 Make sure you have /usr/local/lib in /etc/ld.so.conf and that you
285 run ldconfig after installing.
286 Uninstall any packaged version of Window Maker before installing a new
290 RedHat systems have several annoying problems. If you use it,
291 be sure to follow the steps below or Window Maker will not work:
293 * if you installed the Window Maker that comes with RedHat, uninstall
296 * make sure you don't have the LANG and LINGUAS environment variables
299 * make sure you have /usr/local/bin in your PATH environment
302 * make sure you have /usr/local/lib in /etc/ld.so.conf before running
305 * if you have problems that mention an error message with --no-reexec
306 uninstall libtool-1.2b and install libtool-1.3 instead. libtool-1.3
307 can be found in ftp.gnu.org Also read the TROUBLESHOOTING section;
309 * if you installed the Window Maker package from RedHat and are
310 installing a new version of it by hand (compiling yourself), uninstall
311 the package from RedHat before.
313 * make sure you have a symbolic link from /usr/include/X11 to
314 /usr/X11R6/include/X11 (if not, type ln -s /usr/X11R6/include/X11
317 * make sure you have /lib/cpp pointing to the cpp program
319 If you have any doubts in doing any of the stuff above, please
320 don't hesitate to contact the RedHat user support. They will
321 kindly answer to all your questions regarding their system.
322 They also know much more about their own system than us
323 (we don't use RedHat).
327 You will need to have the latest version of Xpmac. Older versions
328 seem to have bugs that cause the system to hang.
331 If you want JPEG and TIFF support, make sure you have libtiff-dev
332 and libjpeg-dev installed.
335 If you installed the Window Maker package from SuSE,
336 uninstall it before trying to compile wmaker or you
339 - MetroX (unknown version)
340 MetroX has a bug that corrupts pixmaps that are set as window
341 backgrounds. If you use MetroX and has weird problems with
342 textures, do not use textures in titlebars. Or use a different
350 For a quick start, type the following in your shell prompt:
355 then, login as root and type:
360 or if you want to strip the debugging symbols from the binaries and make them
361 smaller, you can instead type:
366 This will build and install Window Maker with default parameters.
368 If you want to customize some compile-time options, you can do the
371 1. (optional) Look at the CONFIGURE OPTIONS section above for the
372 options available. Also run:
376 to get a complete listing of other options that are available.
378 2. Run configure with the options you want. For example, if you
379 want to use the --enable-kde option, type:
381 ./configure --enable-kde
383 3. (optional) Edit src/wconfig.h with your favorite text editor
384 and browse through it for some options you might want to change.
386 4. Compile. Just type:
390 5. Login as root (if you can't do that, read the "I don't have the
391 root password :-(" section) and install Window Maker in your system:
396 User specific configuration
397 ---------------------------
399 These instructions do not need to be followed when upgrading Window Maker
400 from an older version, unless stated differently in the NEWS file.
402 Every user on your system that wishes to run Window Maker must do the
405 1. Install Window Maker configuration files in your home directory.
409 wmaker.inst will install Window Maker configuration files and will
410 setup X to automatically launch Window Maker at startup.
414 You can type "man wmaker" to get some general help for configuration
417 Read the User Guide for a more in-depth explanation of Window Maker.
419 You might want to take a look at the FAQ too.
423 Installing the extras package
424 -----------------------------
426 Unpack WindowMaker-extra-<version-number>.tar.gz in /usr/local/share
428 You can get the file at ftp://ftp.windowmaker.org. This file is optional
429 and only have a few icons, and themes. Look for the latest <version-number>
431 Also there is a WindowMaker-extra.readme to instruct you where that package
436 I don't have the root password :(
437 ---------------------------------
439 If you can't get superuser privileges (can't be root) you can install
440 wmaker in your own home directory. For that, supply the --prefix option
441 when running configure in step 2 of building Window Maker. You will
442 also need to supply the --with-appspath option, to specify the path for
445 ./configure --prefix=/home/jshmoe --with-appspath=/home/jshmoe/GNUstep/Apps
448 Then make /home/jshmoe/bin be included in your search PATH, add
449 /home/jshmoe/lib to your LD_LIBRARY_PATH environment variable and run
452 Of course, /home/jshmoe is supposed to be replaced with your actual home
460 If you are upgrading from an older version of Window Maker:
462 1. Configure and build Window Maker as always
463 2. Install Window Maker (but do not run wmaker.inst)
464 3. Read the NEWS file and update your configuration files,
470 When you have some trouble during configuration (while running configure),
471 like not being able to use a graphic format library you think you have
472 installed, look at the config.log file for clues of the problem.
475 == Error with loading fonts, even if they exist.
477 Try rebuilding without NLS support.
479 == Error when configuring
481 ltconfig: unrecognized option `--no-reexec'
482 Try `ltconfig --help' for more information.
483 configure: error: libtool configure failed
485 remove the --no-reexec option from aclocal.m4 and libPropList/aclocal.m4
487 Also make sure the autoconf and automake versions you have installed are:
492 Note that it must not be libtool 1.2b, it must be libtool 1.3,
495 == Cant find proplist.h or libPropList.something
497 Download and install libPropList from the places pointed to
498 somewhere else in this file.
501 == configure doesn't detect libtiff, or other graphic libraries.
503 Delete config.cache, then rerun configure adding the following options to
504 configure (among the other options you use):
505 --with-libs-from="-L/usr/local/lib"
506 --with-incs-from="-I/usr/local/include -I/usr/local/include/tiff"
507 Put the paths where your graphic libs and their corresponding header files are
508 located. You can put multiple paths in any of these options, as the example
509 of --with-incs-from shows. Just put a space between them.
512 == configure doesn't detect libXpm.
514 * Check if you have a symbolic link from libXpm.so.4.9 to libXpm.so
517 == Segmentation fault on startup
519 * Check if the version of libXPM you have is at least 4.7
521 * Check if you have an updated version of ~/GNUstep/Defaults/WindowMaker
523 If you're not sure, try renaming ~/GNUstep to ~/GNUtmp and then run wmaker.inst
525 == "...: your machine is misconfigured. gethostname() returned (none)"
527 * the hostname of your machine is set to something invalid, that starts
528 with a parenthesis. Do a man hostname for info about how to set it.
531 == The root menu contains only 2 entries. ("XTerm" and "Exit...")
533 * Window Maker is not finding cpp (the C preprocessor). If your cpp is
534 not located in /lib/cpp, edit src/config.h and correct the path in
537 == checking lex output file root... configure: error: cannot find output from true; giving up
539 * Read the REQUIREMENTS section of this file.
542 LOCALES/INTERNATIONALIZATION
543 ============================
545 Window Maker has national language support. To enable national language
546 support, you must compile Window Maker with some additional parameters.
549 0 - You must have the GNU gettext package installed. It can be
550 obtained at ftp://prep.ai.mit.edu/pub/gnu/gettext-nnn.tar.gz
552 Steps 1 to 3 can be skipped if you use the Install script.
554 1 - You have to select the languages you want to support. Set the
555 LINGUAS to the list of locales you want. English is always
558 setenv LINGUAS "pt ja de"
563 export LINGUAS;LINGUAS="pt ja de"
566 The list of supported locales can be found in po/README.
567 English is the default language.
569 Read po/README if you wish to translate and maintain locale files
572 2 - Additionally, if your language uses multi-byte characters, such
573 as Japanese or Korean, you must set the MultiByteText option to YES
574 in ~/GNUstep/Defaults/WMGLOBAL
576 3 - Configure, build and install Window Maker normally.
578 4 - To select a particular locale at runtime you must set the LANG
579 environment variable to the locale you want. For example, if you want to set
580 the portuguese locale, you must run
588 in Bourne sh and similars
590 Note: If you have the LC_CTYPE environment variable set, you must
591 unset it before running wmaker.
593 For menu definition files, Window Maker searches for them in the
594 following order (for brazilian portuguese, in this case):
601 5 - If you chose a language that uses multi-byte characters, you must
602 configure the fonts appropriately. Read the manual page for XCreateFontSet
603 to have more details about it. You must change the ~/G/D/WindowMaker file
604 for fonts used in titlebars, menus and other things. For fonts used in
605 dialog windows, change ~/G/D/WMGLOBAL. The %d in the font names must not be
606 removed. You can also use the supplied wsetfont script for the task.
607 Read the script itself for instructions.
609 For example, you can specify the following in ~/G/D/WindowMaker:
611 WindowTitleFont = "-*-helvetica-bold-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
612 MenuTitleFont = "-*-helvetica-bold-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
613 MenuTextFont = "-*-helvetica-medium-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
614 IconTitleFont = "-*-helvetica-medium-r-normal-*-8-*,-*-*-medium-r-normal-*-12-*";
615 ClipTitleFont = "-*-helvetica-bold-r-normal-*-10-*,-*-*-medium-r-normal-*-12-*";
616 DisplayFont = "-*-helvetica-medium-r-normal-*-12-*,-*-*-medium-r-normal-*-12-*";
618 and in ~/G/D/WMGLOBAL:
620 SystemFont = "-*-*-medium-r-normal-*-%d-*-*-*-*-*-*-*";
621 BoldSystemFont = "-*-*-medium-r-normal-*-%d-*-*-*-*-*-*-*";
623 The above 2 fonts are only used by applications that use WINGs (WindowMaker
626 The wsetfont script that's supplied will allow you to change the font
627 settings in a easier way. Take a look in the script for details on usage.