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 - iBook running Darwin
41 - Windows NT with Cygwin/XFree86
42 - Sony PlayStation2 running Linux
44 All registered trademarks are registered by their owners. (duh)
46 Patches to make it work on other platforms are welcome.
52 The following software is required to use Window Maker:
55 Window Maker can be compiled in older versions of X, like X11R5
56 (Solaris) or X11R4 (OpenWindows) but it will not work 100% correctly.
57 In such servers there will not be application icons and you'll have
58 trouble using the dock. Upgrading the client libraries (Xlib, Xt etc)
59 will help if you can't upgrade the server.
61 The following is required to build Window Maker:
64 If you will build Window Maker, make sure you have gcc (or some
65 other ANSI C compiler) and the X header files installed. Specially
66 for newbie Linux users: you must install all X development packages
67 and the gcc suite. Otherwise you won't be able to build any X
68 program, including Window Maker.
71 This library can be found in ftp://ftp.windowmaker.org/pub/libs
72 or in ftp://ftp.gnome.org/pub/libPropList
73 Install it before building Window Maker.
75 - autoconf, automake and libtool
76 These tools are NOT needed, but IF you have one or
77 more of them installed, make sure you have ALL of the following
78 with exactly these versions:
82 If you have a different version, disable them by temporarily
83 renaming them to something else or uninstalling them from your
84 system. If you don't develop software you don't need them,
85 so you can safely uninstall.
87 - lex (or flex) and yacc (or bison)
88 These are used by libPropList. lex is actually not needed since
89 it's output file is included, but either me or automake is stupid,
90 causing the configure script for libPropList to simply abort for no
91 convincent reason if lex is not found.
97 These libraries are not required to make Window Maker work, but they
98 are supported in case you want to use them. Version numbers are those
99 that I have (and therefore, guraranteed to work), but other versions
103 - libXPM 4.7 or newer
104 Older versions may not work!!!
105 Available at ftp://sunsite.unc.edu/pub/Linux/libs/X/
107 There is builtin support for XPM files, but it will not
108 load images in some uncommon encodings.
110 - libpng 0.96 or newer and zlib
111 For PNG image support.
112 http://www.cdrom.com/pub/png/
114 - libtiff 3.4 or newer
115 For TIFF image support.
116 You can get it at ftp://ftp.sgi.com/graphics/tiff
118 - libjpeg 6.0.1 or newer
119 For JPEG image support
122 - libgif 2.2 or libungif
123 For GIF image support
124 ftp://prtr-13.ucsc.edu/pub/libungif/
126 - libHermes 1.3.2 or newer
127 For faster pixel conversion in the wraster library
128 (its used only in some conversions - for TrueColor visuals)
129 http://www.clanlib.org/hermes/
132 If you want to use translated messages, you will need GNU gettext.
133 Other versions of gettext are not compatible and will not work.
134 Get the GNU version from ftp://ftp.gnu.org
141 These options can be passed to the configure script to enable/disable
142 some Window Maker features. Example:
144 ./configure --enable-kde --enable-gnome
146 will configure Window Maker with KDE and GNOME supported compiled in.
149 To get a list of other options, run ./configure --help
152 specify additional paths for libraries to be searched.
153 The -L flag must precede each path, like:
154 --with-libs-from="-L/opt/libs -L/usr/local/lib"
157 specify additional paths for header files to be searched.
158 The -I flag must precede each paths, like:
159 --with-incs-from="-I/opt/headers -I/usr/local/include"
162 enables the collapsing of all appicons of the WM_CLASS+WM_INSTANCE
163 into a single one. This feature is not supported at all by the
164 developers. If you have some trouble with it, contact it's author:
165 Christopher Seawood <cls@seawood.org>
168 disable use of the MIT shared memory extension. This will slow down
169 texture generation a little bit, but in some cases it seems to be
170 necessary due to a bug that manifests as messed icons and textures.
173 disable support for mwm window manager hints
176 enable support for OPEN LOOK(tm) window manager hints
179 enable support for GNOME window manager hints
182 enable support for kde/kwm window manager hints
185 remove things that are already supported in desktop environments,
186 like KDE and GNOME. Disabled things are: window list, root
187 applications menu, multiple window selection. Note that you will not
188 be able to exit Window Maker from itself anymore; you will have to
189 use kill with the SIGTERM signal or exit it from KDE. It is not
190 advisable to enable it.
193 XKB language status lock support. If you don't know what it is you
194 probably don't need it.
197 enable support of sound effects module
200 disables use of the XPM library even if it is available on your
204 disables use of PNG library
207 disable use of TIFF library
210 disable use of GIF library
213 disable use of JPEG library
216 disables shaped windows (for oclock, xeyes etc.)
219 PLATFORM SPECIFIC NOTES:
220 ========================
225 From: Anton Ivanov <aivanov@eu.level3.net>
226 To: Marcelo E. Magallon <mmagallo@debian.org>
227 Subject: Re: Is the WindowMaker package working ok on Alpha?
231 > I was reading some docs on the WindowMaker tarball, and found this:
233 > | - DEC/Alpha machines
234 > | You might need to pass the --disable-shm flag to configure,
235 > | like ./configure --disable-shm
237 > is anyone having problems with WindowMaker on Alpha? Can someone
238 > please test this? Should the flag be passed when building on Alpha?
240 Disclaimer: alphas under my command have never run X and are least likely to
241 suddenly start running it anytime soon.
243 Alpha used to have some ridiculously low amount of shared memory
245 So quite a lot of apps used to barf. Namely - cdrecord, mysql server, etc.
247 Check where is yours at the moment and raise it to a more appropriate
248 value by either catting to the appropriate /proc entry or changing the
249 /usr/src/linux/include/asm/shmparam.h.
251 Otherwise the shared memory on alpha should be fully functional and I
252 see no reason to disable it. Mine are bumped up to 32 or more on most
255 And If I recall correctly the comments in that file are actually
256 wrong. Value is not bytes, but in machine size word. For alpha *8.
258 As I said - I do not run X on them so all #include "stdisclaimer.h"
263 - SCO Unix - run configure like
264 CFLAGS="-belf -DANSICPP" ./configure
267 If you have gcc installed, run configure as:
268 CPP_PATH="gcc -E -x c" ./configure
269 Sun's cpp lacks some features needed by Window Maker and it can
270 cause problems when parsing the config files.
271 You also might need to use the --with-libs-from and --with-incs-from
272 to supply the directory where libtiff is located.
273 Someone mailed me that you also must make /usr/local/lib be the
274 first path in LD_LIBRARY_PATH to make it work.
276 If you have a Ultra Creator 3D or some other machine with high-end
277 graphics, be sure to start the X server with the default visual
278 set to 24bpp or you might experience problems with mangled colors.
279 This is a wmaker bug and will be fixed.
281 - GNU/Linux in general
282 Make sure you have /usr/local/lib in /etc/ld.so.conf and that you
283 run ldconfig after installing.
284 Uninstall any packaged version of Window Maker before installing a new
288 RedHat systems have several annoying problems. If you use it,
289 be sure to follow the steps below or Window Maker will not work:
291 * if you installed the Window Maker that comes with RedHat, uninstall
294 * make sure you don't have the LANG and LINGUAS environment variables
297 * make sure you have /usr/local/bin in your PATH environment
300 * make sure you have /usr/local/lib in /etc/ld.so.conf before running
303 * if you have problems that mention an error message with --no-reexec
304 uninstall libtool-1.2b and install libtool-1.3 instead. libtool-1.3
305 can be found in ftp.gnu.org Also read the TROUBLESHOOTING section;
307 * if you installed the Window Maker package from RedHat and are
308 installing a new version of it by hand (compiling yourself), uninstall
309 the package from RedHat before.
311 * make sure you have a symbolic link from /usr/include/X11 to
312 /usr/X11R6/include/X11 (if not, type ln -s /usr/X11R6/include/X11
315 * make sure you have /lib/cpp pointing to the cpp program
317 If you have any doubts in doing any of the stuff above, please
318 don't hesitate to contact the RedHat user support. They will
319 kindly answer to all your questions regarding their system.
320 They also know much more about their own system than us
321 (we don't use RedHat).
325 You will need to have the latest version of Xpmac. Older versions
326 seem to have bugs that cause the system to hang.
329 If you want JPEG and TIFF support, make sure you have libtiff-dev
330 and libjpeg-dev installed.
333 If you installed the Window Maker package from SuSE,
334 uninstall it before trying to compile wmaker or you
337 - MetroX (unknown version)
338 MetroX has a bug that corrupts pixmaps that are set as window
339 backgrounds. If you use MetroX and has weird problems with
340 textures, do not use textures in titlebars. Or use a different
348 For a quick start, type the following in your shell prompt:
353 then, login as root and type:
358 or if you want to strip the debugging symbols from the binaries and make them
359 smaller, you can instead type:
364 This will build and install Window Maker with default parameters.
366 If you want to customize some compile-time options, you can do the
369 1. (optional) Look at the CONFIGURE OPTIONS section above for the
370 options available. Also run:
374 to get a complete listing of other options that are available.
376 2. Run configure with the options you want. For example, if you
377 want to use the --enable-kde option, type:
379 ./configure --enable-kde
381 3. (optional) Edit src/wconfig.h with your favorite text editor
382 and browse through it for some options you might want to change.
384 4. Compile. Just type:
388 5. Login as root (if you can't do that, read the "I don't have the
389 root password :-(" section) and install Window Maker in your system:
394 User specific configuration
395 ---------------------------
397 These instructions do not need to be followed when upgrading Window Maker
398 from an older version, unless stated differently in the NEWS file.
400 Every user on your system that wishes to run Window Maker must do the
403 1. Install Window Maker configuration files in your home directory.
407 wmaker.inst will install Window Maker configuration files and will
408 setup X to automatically launch Window Maker at startup.
412 You can type "man wmaker" to get some general help for configuration
415 Read the User Guide for a more in-depth explanation of Window Maker.
417 You might want to take a look at the FAQ too.
421 Installing the extras package
422 -----------------------------
424 Unpack WindowMaker-extra-<version-number>.tar.gz in /usr/local/share
426 You can get the file at ftp://ftp.windowmaker.org. This file is optional
427 and only have a few icons, and themes. Look for the latest <version-number>
429 Also there is a WindowMaker-extra.readme to instruct you where that package
434 I don't have the root password :(
435 ---------------------------------
437 If you can't get superuser privileges (can't be root) you can install
438 wmaker in your own home directory. For that, supply the --prefix option
439 when running configure in step 2 of building Window Maker. You will
440 also need to supply the --with-appspath option, to specify the path for
443 ./configure --prefix=/home/jshmoe --with-appspath=/home/jshmoe/GNUstep/Apps
446 Then make /home/jshmoe/bin be included in your search PATH, add
447 /home/jshmoe/lib to your LD_LIBRARY_PATH environment variable and run
450 Of course, /home/jshmoe is supposed to be replaced with your actual home
458 If you are upgrading from an older version of Window Maker:
460 1. Configure and build Window Maker as always
461 2. Install Window Maker (but do not run wmaker.inst)
462 3. Read the NEWS file and update your configuration files,
468 When you have some trouble during configuration (while running configure),
469 like not being able to use a graphic format library you think you have
470 installed, look at the config.log file for clues of the problem.
473 == Error with loading fonts, even if they exist.
475 Try rebuilding without NLS support.
477 == Error when configuring
479 ltconfig: unrecognized option `--no-reexec'
480 Try `ltconfig --help' for more information.
481 configure: error: libtool configure failed
483 remove the --no-reexec option from aclocal.m4 and libPropList/aclocal.m4
485 Also make sure the autoconf and automake versions you have installed are:
490 Note that it must not be libtool 1.2b, it must be libtool 1.3,
493 == Cant find proplist.h or libPropList.something
495 Download and install libPropList from the places pointed to
496 somewhere else in this file.
499 == configure doesn't detect libtiff, or other graphic libraries.
501 Delete config.cache, then rerun configure adding the following options to
502 configure (among the other options you use):
503 --with-libs-from="-L/usr/local/lib"
504 --with-incs-from="-I/usr/local/include -I/usr/local/include/tiff"
505 Put the paths where your graphic libs and their corresponding header files are
506 located. You can put multiple paths in any of these options, as the example
507 of --with-incs-from shows. Just put a space between them.
510 == configure doesn't detect libXpm.
512 * Check if you have a symbolic link from libXpm.so.4.9 to libXpm.so
515 == Segmentation fault on startup
517 * Check if the version of libXPM you have is at least 4.7
519 * Check if you have an updated version of ~/GNUstep/Defaults/WindowMaker
521 If you're not sure, try renaming ~/GNUstep to ~/GNUtmp and then run wmaker.inst
523 == "...: your machine is misconfigured. gethostname() returned (none)"
525 * the hostname of your machine is set to something invalid, that starts
526 with a parenthesis. Do a man hostname for info about how to set it.
529 == The root menu contains only 2 entries. ("XTerm" and "Exit...")
531 * Window Maker is not finding cpp (the C preprocessor). If your cpp is
532 not located in /lib/cpp, edit src/config.h and correct the path in
535 == checking lex output file root... configure: error: cannot find output from true; giving up
537 * Read the REQUIREMENTS section of this file.
540 LOCALES/INTERNATIONALIZATION
541 ============================
543 Window Maker has national language support. To enable national language
544 support, you must compile Window Maker with some additional parameters.
547 0 - You must have the GNU gettext package installed. It can be
548 obtained at ftp://prep.ai.mit.edu/pub/gnu/gettext-nnn.tar.gz
550 Steps 1 to 3 can be skipped if you use the Install script.
552 1 - You have to select the languages you want to support. Set the
553 LINGUAS to the list of locales you want. English is always
556 setenv LINGUAS "pt ja de"
561 export LINGUAS;LINGUAS="pt ja de"
564 The list of supported locales can be found in po/README.
565 English is the default language.
567 Read po/README if you wish to translate and maintain locale files
570 2 - Additionally, if your language uses multi-byte characters, such
571 as Japanese or Korean, you must set the MultiByteText option to YES
572 in ~/GNUstep/Defaults/WMGLOBAL
574 3 - Configure, build and install Window Maker normally.
576 4 - To select a particular locale at runtime you must set the LANG
577 environment variable to the locale you want. For example, if you want to set
578 the portuguese locale, you must run
586 in Bourne sh and similars
588 Note: If you have the LC_CTYPE environment variable set, you must
589 unset it before running wmaker.
591 For menu definition files, Window Maker searches for them in the
592 following order (for brazilian portuguese, in this case):
599 5 - If you chose a language that uses multi-byte characters, you must
600 configure the fonts appropriately. Read the manual page for XCreateFontSet
601 to have more details about it. You must change the ~/G/D/WindowMaker file
602 for fonts used in titlebars, menus and other things. For fonts used in
603 dialog windows, change ~/G/D/WMGLOBAL. The %d in the font names must not be
604 removed. You can also use the supplied wsetfont script for the task.
605 Read the script itself for instructions.
607 For example, you can specify the following in ~/G/D/WindowMaker:
609 WindowTitleFont = "-*-helvetica-bold-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
610 MenuTitleFont = "-*-helvetica-bold-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
611 MenuTextFont = "-*-helvetica-medium-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
612 IconTitleFont = "-*-helvetica-medium-r-normal-*-8-*,-*-*-medium-r-normal-*-12-*";
613 ClipTitleFont = "-*-helvetica-bold-r-normal-*-10-*,-*-*-medium-r-normal-*-12-*";
614 DisplayFont = "-*-helvetica-medium-r-normal-*-12-*,-*-*-medium-r-normal-*-12-*";
616 and in ~/G/D/WMGLOBAL:
618 SystemFont = "-*-*-medium-r-normal-*-%d-*-*-*-*-*-*-*";
619 BoldSystemFont = "-*-*-medium-r-normal-*-%d-*-*-*-*-*-*-*";
621 The above 2 fonts are only used by applications that use WINGs (WindowMaker
624 The wsetfont script that's supplied will allow you to change the font
625 settings in a easier way. Take a look in the script for details on usage.