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
29 - AIX 4.1.4 / IBM PowerPC
30 - AIX 4.3.1 / IBM CC compiler
31 - AIX 4.3.2 / IBM PowerPC
33 - DEC Alpha/Digital UNIX 4.x
37 - PowerMac / Power MachTen 4.1.1 over MacOS
38 - Amiga 3000 running RedHat Linux 5.1 (Rawhide)
39 - IBM S/390 running Linux
40 - IBM S/390 running Conectiva Linux (experimental)
41 - iBook running Darwin
42 - Windows NT with Cygwin/XFree86
43 - Sony PlayStation2 running Linux
45 All registered trademarks are registered by their owners. (duh)
47 Patches to make it work on other platforms are welcome.
53 The following software is required to use Window Maker:
56 Window Maker can be compiled in older versions of X, like X11R5
57 (Solaris) or X11R4 (OpenWindows) but it will not work 100% correctly.
58 In such servers there will not be application icons and you'll have
59 trouble using the dock. Upgrading the client libraries (Xlib, Xt etc)
60 will help if you can't upgrade the server.
62 The following is required to build Window Maker:
65 If you will build Window Maker, make sure you have gcc (or some
66 other ANSI C compiler) and the X header files installed. Specially
67 for newbie Linux users: you must install all X development packages
68 and the gcc suite. Otherwise you won't be able to build any X
69 program, including Window Maker.
72 This library can be found in ftp://ftp.windowmaker.org/pub/libs
73 or in ftp://ftp.gnome.org/pub/libPropList
74 Install it before building Window Maker.
76 - autoconf, automake and libtool
77 These tools are NOT needed, but IF you have one or
78 more of them installed, make sure you have ALL of the following
79 with exactly these versions:
83 If you have a different version, disable them by temporarily
84 renaming them to something else or uninstalling them from your
85 system. If you don't develop software you don't need them,
86 so you can safely uninstall.
88 - lex (or flex) and yacc (or bison)
89 These are used by libPropList. lex is actually not needed since
90 it's output file is included, but either me or automake is stupid,
91 causing the configure script for libPropList to simply abort for no
92 convincent reason if lex is not found.
98 These libraries are not required to make Window Maker work, but they
99 are supported in case you want to use them. Version numbers are those
100 that I have (and therefore, guraranteed to work), but other versions
104 - libXPM 4.7 or newer
105 Older versions may not work!!!
106 Available at ftp://sunsite.unc.edu/pub/Linux/libs/X/
108 There is builtin support for XPM files, but it will not
109 load images in some uncommon encodings.
111 - libpng 0.96 or newer and zlib
112 For PNG image support.
113 http://www.cdrom.com/pub/png/
115 - libtiff 3.4 or newer
116 For TIFF image support.
117 You can get it at ftp://ftp.sgi.com/graphics/tiff
119 - libjpeg 6.0.1 or newer
120 For JPEG image support
123 - libgif 2.2 or libungif
124 For GIF image support
125 ftp://prtr-13.ucsc.edu/pub/libungif/
127 - libHermes 1.3.2 or newer
128 For faster pixel conversion in the wraster library
129 (its used only in some conversions - for TrueColor visuals)
130 http://www.clanlib.org/hermes/
133 If you want to use translated messages, you will need GNU gettext.
134 Other versions of gettext are not compatible and will not work.
135 Get the GNU version from ftp://ftp.gnu.org
142 These options can be passed to the configure script to enable/disable
143 some Window Maker features. Example:
145 ./configure --enable-kde --enable-gnome
147 will configure Window Maker with KDE and GNOME supported compiled in.
150 To get a list of other options, run ./configure --help
153 specify additional paths for libraries to be searched.
154 The -L flag must precede each path, like:
155 --with-libs-from="-L/opt/libs -L/usr/local/lib"
158 specify additional paths for header files to be searched.
159 The -I flag must precede each paths, like:
160 --with-incs-from="-I/opt/headers -I/usr/local/include"
163 enables the collapsing of all appicons of the WM_CLASS+WM_INSTANCE
164 into a single one. This feature is not supported at all by the
165 developers. If you have some trouble with it, contact it's author:
166 Christopher Seawood <cls@seawood.org>
169 disable use of the MIT shared memory extension. This will slow down
170 texture generation a little bit, but in some cases it seems to be
171 necessary due to a bug that manifests as messed icons and textures.
174 disable support for mwm window manager hints
177 enable support for OPEN LOOK(tm) window manager hints
180 enable support for GNOME window manager hints
183 enable support for kde/kwm window manager hints
186 remove things that are already supported in desktop environments,
187 like KDE and GNOME. Disabled things are: window list, root
188 applications menu, multiple window selection. Note that you will not
189 be able to exit Window Maker from itself anymore; you will have to
190 use kill with the SIGTERM signal or exit it from KDE. It is not
191 advisable to enable it.
194 XKB language status lock support. If you don't know what it is you
195 probably don't need it.
198 enable support of sound effects module
201 disables use of the XPM library even if it is available on your
205 disables use of PNG library
208 disable use of TIFF library
211 disable use of GIF library
214 disable use of JPEG library
217 disables shaped windows (for oclock, xeyes etc.)
220 PLATFORM SPECIFIC NOTES:
221 ========================
226 From: Anton Ivanov <aivanov@eu.level3.net>
227 To: Marcelo E. Magallon <mmagallo@debian.org>
228 Subject: Re: Is the WindowMaker package working ok on Alpha?
232 > I was reading some docs on the WindowMaker tarball, and found this:
234 > | - DEC/Alpha machines
235 > | You might need to pass the --disable-shm flag to configure,
236 > | like ./configure --disable-shm
238 > is anyone having problems with WindowMaker on Alpha? Can someone
239 > please test this? Should the flag be passed when building on Alpha?
241 Disclaimer: alphas under my command have never run X and are least likely to
242 suddenly start running it anytime soon.
244 Alpha used to have some ridiculously low amount of shared memory
246 So quite a lot of apps used to barf. Namely - cdrecord, mysql server, etc.
248 Check where is yours at the moment and raise it to a more appropriate
249 value by either catting to the appropriate /proc entry or changing the
250 /usr/src/linux/include/asm/shmparam.h.
252 Otherwise the shared memory on alpha should be fully functional and I
253 see no reason to disable it. Mine are bumped up to 32 or more on most
256 And If I recall correctly the comments in that file are actually
257 wrong. Value is not bytes, but in machine size word. For alpha *8.
259 As I said - I do not run X on them so all #include "stdisclaimer.h"
264 - SCO Unix - run configure like
265 CFLAGS="-belf -DANSICPP" ./configure
268 If you have gcc installed, run configure as:
269 CPP_PATH="gcc -E -x c" ./configure
270 Sun's cpp lacks some features needed by Window Maker and it can
271 cause problems when parsing the config files.
272 You also might need to use the --with-libs-from and --with-incs-from
273 to supply the directory where libtiff is located.
274 Someone mailed me that you also must make /usr/local/lib be the
275 first path in LD_LIBRARY_PATH to make it work.
277 If you have a Ultra Creator 3D or some other machine with high-end
278 graphics, be sure to start the X server with the default visual
279 set to 24bpp or you might experience problems with mangled colors.
280 This is a wmaker bug and will be fixed.
282 - GNU/Linux in general
283 Make sure you have /usr/local/lib in /etc/ld.so.conf and that you
284 run ldconfig after installing.
285 Uninstall any packaged version of Window Maker before installing a new
289 RedHat systems have several annoying problems. If you use it,
290 be sure to follow the steps below or Window Maker will not work:
292 * if you installed the Window Maker that comes with RedHat, uninstall
295 * make sure you don't have the LANG and LINGUAS environment variables
298 * make sure you have /usr/local/bin in your PATH environment
301 * make sure you have /usr/local/lib in /etc/ld.so.conf before running
304 * if you have problems that mention an error message with --no-reexec
305 uninstall libtool-1.2b and install libtool-1.3 instead. libtool-1.3
306 can be found in ftp.gnu.org Also read the TROUBLESHOOTING section;
308 * if you installed the Window Maker package from RedHat and are
309 installing a new version of it by hand (compiling yourself), uninstall
310 the package from RedHat before.
312 * make sure you have a symbolic link from /usr/include/X11 to
313 /usr/X11R6/include/X11 (if not, type ln -s /usr/X11R6/include/X11
316 * make sure you have /lib/cpp pointing to the cpp program
318 If you have any doubts in doing any of the stuff above, please
319 don't hesitate to contact the RedHat user support. They will
320 kindly answer to all your questions regarding their system.
321 They also know much more about their own system than us
322 (we don't use RedHat).
326 You will need to have the latest version of Xpmac. Older versions
327 seem to have bugs that cause the system to hang.
330 If you want JPEG and TIFF support, make sure you have libtiff-dev
331 and libjpeg-dev installed.
334 If you installed the Window Maker package from SuSE,
335 uninstall it before trying to compile wmaker or you
338 - MetroX (unknown version)
339 MetroX has a bug that corrupts pixmaps that are set as window
340 backgrounds. If you use MetroX and has weird problems with
341 textures, do not use textures in titlebars. Or use a different
349 For a quick start, type the following in your shell prompt:
354 then, login as root and type:
359 or if you want to strip the debugging symbols from the binaries and make them
360 smaller, you can instead type:
365 This will build and install Window Maker with default parameters.
367 If you want to customize some compile-time options, you can do the
370 1. (optional) Look at the CONFIGURE OPTIONS section above for the
371 options available. Also run:
375 to get a complete listing of other options that are available.
377 2. Run configure with the options you want. For example, if you
378 want to use the --enable-kde option, type:
380 ./configure --enable-kde
382 3. (optional) Edit src/wconfig.h with your favorite text editor
383 and browse through it for some options you might want to change.
385 4. Compile. Just type:
389 5. Login as root (if you can't do that, read the "I don't have the
390 root password :-(" section) and install Window Maker in your system:
395 User specific configuration
396 ---------------------------
398 These instructions do not need to be followed when upgrading Window Maker
399 from an older version, unless stated differently in the NEWS file.
401 Every user on your system that wishes to run Window Maker must do the
404 1. Install Window Maker configuration files in your home directory.
408 wmaker.inst will install Window Maker configuration files and will
409 setup X to automatically launch Window Maker at startup.
413 You can type "man wmaker" to get some general help for configuration
416 Read the User Guide for a more in-depth explanation of Window Maker.
418 You might want to take a look at the FAQ too.
422 Installing the extras package
423 -----------------------------
425 Unpack WindowMaker-extra-<version-number>.tar.gz in /usr/local/share
427 You can get the file at ftp://ftp.windowmaker.org. This file is optional
428 and only have a few icons, and themes. Look for the latest <version-number>
430 Also there is a WindowMaker-extra.readme to instruct you where that package
435 I don't have the root password :(
436 ---------------------------------
438 If you can't get superuser privileges (can't be root) you can install
439 wmaker in your own home directory. For that, supply the --prefix option
440 when running configure in step 2 of building Window Maker. You will
441 also need to supply the --with-appspath option, to specify the path for
444 ./configure --prefix=/home/jshmoe --with-appspath=/home/jshmoe/GNUstep/Apps
447 Then make /home/jshmoe/bin be included in your search PATH, add
448 /home/jshmoe/lib to your LD_LIBRARY_PATH environment variable and run
451 Of course, /home/jshmoe is supposed to be replaced with your actual home
459 If you are upgrading from an older version of Window Maker:
461 1. Configure and build Window Maker as always
462 2. Install Window Maker (but do not run wmaker.inst)
463 3. Read the NEWS file and update your configuration files,
469 When you have some trouble during configuration (while running configure),
470 like not being able to use a graphic format library you think you have
471 installed, look at the config.log file for clues of the problem.
474 == Error with loading fonts, even if they exist.
476 Try rebuilding without NLS support.
478 == Error when configuring
480 ltconfig: unrecognized option `--no-reexec'
481 Try `ltconfig --help' for more information.
482 configure: error: libtool configure failed
484 remove the --no-reexec option from aclocal.m4 and libPropList/aclocal.m4
486 Also make sure the autoconf and automake versions you have installed are:
491 Note that it must not be libtool 1.2b, it must be libtool 1.3,
494 == Cant find proplist.h or libPropList.something
496 Download and install libPropList from the places pointed to
497 somewhere else in this file.
500 == configure doesn't detect libtiff, or other graphic libraries.
502 Delete config.cache, then rerun configure adding the following options to
503 configure (among the other options you use):
504 --with-libs-from="-L/usr/local/lib"
505 --with-incs-from="-I/usr/local/include -I/usr/local/include/tiff"
506 Put the paths where your graphic libs and their corresponding header files are
507 located. You can put multiple paths in any of these options, as the example
508 of --with-incs-from shows. Just put a space between them.
511 == configure doesn't detect libXpm.
513 * Check if you have a symbolic link from libXpm.so.4.9 to libXpm.so
516 == Segmentation fault on startup
518 * Check if the version of libXPM you have is at least 4.7
520 * Check if you have an updated version of ~/GNUstep/Defaults/WindowMaker
522 If you're not sure, try renaming ~/GNUstep to ~/GNUtmp and then run wmaker.inst
524 == "...: your machine is misconfigured. gethostname() returned (none)"
526 * the hostname of your machine is set to something invalid, that starts
527 with a parenthesis. Do a man hostname for info about how to set it.
530 == The root menu contains only 2 entries. ("XTerm" and "Exit...")
532 * Window Maker is not finding cpp (the C preprocessor). If your cpp is
533 not located in /lib/cpp, edit src/config.h and correct the path in
536 == checking lex output file root... configure: error: cannot find output from true; giving up
538 * Read the REQUIREMENTS section of this file.
541 LOCALES/INTERNATIONALIZATION
542 ============================
544 Window Maker has national language support. To enable national language
545 support, you must compile Window Maker with some additional parameters.
548 0 - You must have the GNU gettext package installed. It can be
549 obtained at ftp://prep.ai.mit.edu/pub/gnu/gettext-nnn.tar.gz
551 Steps 1 to 3 can be skipped if you use the Install script.
553 1 - You have to select the languages you want to support. Set the
554 LINGUAS to the list of locales you want. English is always
557 setenv LINGUAS "pt ja de"
562 export LINGUAS;LINGUAS="pt ja de"
565 The list of supported locales can be found in po/README.
566 English is the default language.
568 Read po/README if you wish to translate and maintain locale files
571 2 - Additionally, if your language uses multi-byte characters, such
572 as Japanese or Korean, you must set the MultiByteText option to YES
573 in ~/GNUstep/Defaults/WMGLOBAL
575 3 - Configure, build and install Window Maker normally.
577 4 - To select a particular locale at runtime you must set the LANG
578 environment variable to the locale you want. For example, if you want to set
579 the portuguese locale, you must run
587 in Bourne sh and similars
589 Note: If you have the LC_CTYPE environment variable set, you must
590 unset it before running wmaker.
592 For menu definition files, Window Maker searches for them in the
593 following order (for brazilian portuguese, in this case):
600 5 - If you chose a language that uses multi-byte characters, you must
601 configure the fonts appropriately. Read the manual page for XCreateFontSet
602 to have more details about it. You must change the ~/G/D/WindowMaker file
603 for fonts used in titlebars, menus and other things. For fonts used in
604 dialog windows, change ~/G/D/WMGLOBAL. The %d in the font names must not be
605 removed. You can also use the supplied wsetfont script for the task.
606 Read the script itself for instructions.
608 For example, you can specify the following in ~/G/D/WindowMaker:
610 WindowTitleFont = "-*-helvetica-bold-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
611 MenuTitleFont = "-*-helvetica-bold-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
612 MenuTextFont = "-*-helvetica-medium-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
613 IconTitleFont = "-*-helvetica-medium-r-normal-*-8-*,-*-*-medium-r-normal-*-12-*";
614 ClipTitleFont = "-*-helvetica-bold-r-normal-*-10-*,-*-*-medium-r-normal-*-12-*";
615 DisplayFont = "-*-helvetica-medium-r-normal-*-12-*,-*-*-medium-r-normal-*-12-*";
617 and in ~/G/D/WMGLOBAL:
619 SystemFont = "-*-*-medium-r-normal-*-%d-*-*-*-*-*-*-*";
620 BoldSystemFont = "-*-*-medium-r-normal-*-%d-*-*-*-*-*-*-*";
622 The above 2 fonts are only used by applications that use WINGs (WindowMaker
625 The wsetfont script that's supplied will allow you to change the font
626 settings in a easier way. Take a look in the script for details on usage.