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
43 Patches to make it work on other platforms are welcome.
49 The following software is required to use Window Maker:
52 Window Maker can be compiled in older versions of X, like X11R5
53 (Solaris) or X11R4 (OpenWindows) but it will not work 100% correctly.
54 In such servers there will not be application icons and you'll have
55 trouble using the dock. Upgrading the client libraries (Xlib, Xt etc)
56 will help if you can't upgrade the server.
58 The following is required to build Window Maker:
61 If you will build Window Maker, make sure you have gcc (or some
62 other ANSI C compiler) and the X header files installed. Specially
63 for newbie Linux users: you must install all X development packages
64 and the gcc suite. Otherwise you won't be able to build any X
65 program, including Window Maker.
68 This library can be found in ftp://ftp.windowmaker.org/pub/libs
69 or in ftp://ftp.gnome.org/pub/libPropList
70 Install it before building Window Maker.
72 - autoconf, automake and libtool
73 These tools are NOT needed, but IF you have one or
74 more of them installed, make sure you have ALL of the following
75 with exactly these versions:
79 If you have a different version, disable them by temporarily
80 renaming them to something else or uninstalling them from your
81 system. If you don't develop software you don't need them,
82 so you can safely uninstall.
84 - lex (or flex) and yacc (or bison)
85 These are used by libPropList. lex is actually not needed since
86 it's output file is included, but either me or automake is stupid,
87 causing the configure script for libPropList to simply abort for no
88 convincent reason if lex is not found.
94 These libraries are not required to make Window Maker work, but they
95 are supported in case you want to use them. Version numbers are those
96 that I have (and therefore, guraranteed to work), but other versions
100 - libXPM 4.7 or newer
101 Older versions may not work!!!
102 Available at ftp://sunsite.unc.edu/pub/Linux/libs/X/
104 There is builtin support for XPM files, but it will not
105 load images in some uncommon encodings.
107 - libpng 0.96 or newer and zlib
108 For PNG image support.
109 http://www.cdrom.com/pub/png/
111 - libtiff 3.4 or newer
112 For TIFF image support.
113 You can get it at ftp://ftp.sgi.com/graphics/tiff
115 - libjpeg 6.0.1 or newer
116 For JPEG image support
119 - libgif 2.2 or libungif
120 For GIF image support
121 ftp://prtr-13.ucsc.edu/pub/libungif/
123 - libHermes 1.3.2 or newer
124 For faster pixel conversion in the wraster library
125 (its used only in some conversions - for TrueColor visuals)
126 http://www.clanlib.org/hermes/
129 If you want to use translated messages, you will need GNU gettext.
130 Other versions of gettext are not compatible and will not work.
131 Get the GNU version from ftp://ftp.gnu.org
138 These options can be passed to the configure script to enable/disable
139 some Window Maker features. Example:
141 ./configure --enable-kde --enable-gnome
143 will configure Window Maker with KDE and GNOME supported compiled in.
146 To get a list of other options, run ./configure --help
149 specify additional paths for libraries to be searched.
150 The -L flag must precede each path, like:
151 --with-libs-from="-L/opt/libs -L/usr/local/lib"
154 specify additional paths for header files to be searched.
155 The -I flag must precede each paths, like:
156 --with-incs-from="-I/opt/headers -I/usr/local/include"
159 enables the collapsing of all appicons of the WM_CLASS+WM_INSTANCE
160 into a single one. This feature is not supported at all by the
161 developers. If you have some trouble with it, contact it's author:
162 Christopher Seawood <cls@seawood.org>
165 disable use of the MIT shared memory extension. This will slow down
166 texture generation a little bit, but in some cases it seems to be
167 necessary due to a bug that manifests as messed icons and textures.
170 disable support for mwm window manager hints
173 enable support for OPEN LOOK(tm) window manager hints
176 enable support for GNOME window manager hints
179 enable support for kde/kwm window manager hints
182 remove things that are already supported in desktop environments,
183 like KDE and GNOME. Disabled things are: window list, root
184 applications menu, multiple window selection. Note that you will not
185 be able to exit Window Maker from itself anymore; you will have to
186 use kill with the SIGTERM signal or exit it from KDE. It is not
187 advisable to enable it.
190 XKB language status lock support. If you don't know what it is you
191 probably don't need it.
194 enable support of sound effects module
197 disables use of the XPM library even if it is available on your
201 disables use of PNG library
204 disable use of TIFF library
207 disable use of GIF library
210 disable use of JPEG library
213 disables shaped windows (for oclock, xeyes etc.)
216 PLATFORM SPECIFIC NOTES:
217 ========================
222 From: Anton Ivanov <aivanov@eu.level3.net>
223 To: Marcelo E. Magallon <mmagallo@debian.org>
224 Subject: Re: Is the WindowMaker package working ok on Alpha?
228 > I was reading some docs on the WindowMaker tarball, and found this:
230 > | - DEC/Alpha machines
231 > | You might need to pass the --disable-shm flag to configure,
232 > | like ./configure --disable-shm
234 > is anyone having problems with WindowMaker on Alpha? Can someone
235 > please test this? Should the flag be passed when building on Alpha?
237 Disclaimer: alphas under my command have never run X and are least likely to
238 suddenly start running it anytime soon.
240 Alpha used to have some ridiculously low amount of shared memory
242 So quite a lot of apps used to barf. Namely - cdrecord, mysql server, etc.
244 Check where is yours at the moment and raise it to a more appropriate
245 value by either catting to the appropriate /proc entry or changing the
246 /usr/src/linux/include/asm/shmparam.h.
248 Otherwise the shared memory on alpha should be fully functional and I
249 see no reason to disable it. Mine are bumped up to 32 or more on most
252 And If I recall correctly the comments in that file are actually
253 wrong. Value is not bytes, but in machine size word. For alpha *8.
255 As I said - I do not run X on them so all #include "stdisclaimer.h"
260 - SCO Unix - run configure like
261 CFLAGS="-belf -DANSICPP" ./configure
264 If you have gcc installed, run configure as:
265 CPP_PATH="gcc -E -x c" ./configure
266 Sun's cpp lacks some features needed by Window Maker and it can
267 cause problems when parsing the config files.
268 You also might need to use the --with-libs-from and --with-incs-from
269 to supply the directory where libtiff is located.
270 Someone mailed me that you also must make /usr/local/lib be the
271 first path in LD_LIBRARY_PATH to make it work.
273 If you have a Ultra Creator 3D or some other machine with high-end
274 graphics, be sure to start the X server with the default visual
275 set to 24bpp or you might experience problems with mangled colors.
276 This is a wmaker bug and will be fixed.
278 - GNU/Linux in general
279 Make sure you have /usr/local/lib in /etc/ld.so.conf and that you
280 run ldconfig after installing.
281 Uninstall any packaged version of Window Maker before installing a new
285 RedHat systems have several annoying problems. If you use it,
286 be sure to follow the steps below or Window Maker will not work:
288 * if you installed the Window Maker that comes with RedHat, uninstall
291 * make sure you don't have the LANG and LINGUAS environment variables
294 * make sure you have /usr/local/bin in your PATH environment
297 * make sure you have /usr/local/lib in /etc/ld.so.conf before running
300 * if you have problems that mention an error message with --no-reexec
301 uninstall libtool-1.2b and install libtool-1.3 instead. libtool-1.3
302 can be found in ftp.gnu.org Also read the TROUBLESHOOTING section;
304 * if you installed the Window Maker package from RedHat and are
305 installing a new version of it by hand (compiling yourself), uninstall
306 the package from RedHat before.
308 * make sure you have a symbolic link from /usr/include/X11 to
309 /usr/X11R6/include/X11 (if not, type ln -s /usr/X11R6/include/X11
312 * make sure you have /lib/cpp pointing to the cpp program
314 If you have any doubts in doing any of the stuff above, please
315 don't hesitate to contact the RedHat user support. They will
316 kindly answer to all your questions regarding their system.
317 They also know much more about their own system than us
318 (we don't use RedHat).
322 You will need to have the latest version of Xpmac. Older versions
323 seem to have bugs that cause the system to hang.
326 If you want JPEG and TIFF support, make sure you have libtiff-dev
327 and libjpeg-dev installed.
330 If you installed the Window Maker package from SuSE,
331 uninstall it before trying to compile wmaker or you
334 - MetroX (unknown version)
335 MetroX has a bug that corrupts pixmaps that are set as window
336 backgrounds. If you use MetroX and has weird problems with
337 textures, do not use textures in titlebars. Or use a different
345 For a quick start, type the following in your shell prompt:
350 then, login as root and type:
355 or if you want to strip the debugging symbols from the binaries and make them
356 smaller, you can instead type:
361 This will build and install Window Maker with default parameters.
363 If you want to customize some compile-time options, you can do the
366 1. (optional) Look at the CONFIGURE OPTIONS section above for the
367 options available. Also run:
371 to get a complete listing of other options that are available.
373 2. Run configure with the options you want. For example, if you
374 want to use the --enable-kde option, type:
376 ./configure --enable-kde
378 3. (optional) Edit src/wconfig.h with your favorite text editor
379 and browse through it for some options you might want to change.
381 4. Compile. Just type:
385 5. Login as root (if you can't do that, read the "I don't have the
386 root password :-(" section) and install Window Maker in your system:
391 User specific configuration
392 ---------------------------
394 These instructions do not need to be followed when upgrading Window Maker
395 from an older version, unless stated differently in the NEWS file.
397 Every user on your system that wishes to run Window Maker must do the
400 1. Install Window Maker configuration files in your home directory.
404 wmaker.inst will install Window Maker configuration files and will
405 setup X to automatically launch Window Maker at startup.
409 You can type "man wmaker" to get some general help for configuration
412 Read the User Guide for a more in-depth explanation of Window Maker.
414 You might want to take a look at the FAQ too.
418 Installing the extras package
419 -----------------------------
421 Unpack WindowMaker-extra-<version-number>.tar.gz in /usr/local/share
423 You can get the file at ftp://ftp.windowmaker.org. This file is optional
424 and only have a few icons, and themes. Look for the latest <version-number>
426 Also there is a WindowMaker-extra.readme to instruct you where that package
431 I don't have the root password :(
432 ---------------------------------
434 If you can't get superuser privileges (can't be root) you can install
435 wmaker in your own home directory. For that, supply the --prefix option
436 when running configure in step 2 of building Window Maker. You will
437 also need to supply the --with-appspath option, to specify the path for
440 ./configure --prefix=/home/jshmoe --with-appspath=/home/jshmoe/GNUstep/Apps
443 Then make /home/jshmoe/bin be included in your search PATH, add
444 /home/jshmoe/lib to your LD_LIBRARY_PATH environment variable and run
447 Of course, /home/jshmoe is supposed to be replaced with your actual home
455 If you are upgrading from an older version of Window Maker:
457 1. Configure and build Window Maker as always
458 2. Install Window Maker (but do not run wmaker.inst)
459 3. Read the NEWS file and update your configuration files,
465 When you have some trouble during configuration (while running configure),
466 like not being able to use a graphic format library you think you have
467 installed, look at the config.log file for clues of the problem.
470 == Error with loading fonts, even if they exist.
472 Try rebuilding without NLS support.
474 == Error when configuring
476 ltconfig: unrecognized option `--no-reexec'
477 Try `ltconfig --help' for more information.
478 configure: error: libtool configure failed
480 remove the --no-reexec option from aclocal.m4 and libPropList/aclocal.m4
482 Also make sure the autoconf and automake versions you have installed are:
487 Note that it must not be libtool 1.2b, it must be libtool 1.3,
490 == Cant find proplist.h or libPropList.something
492 Download and install libPropList from the places pointed to
493 somewhere else in this file.
496 == configure doesn't detect libtiff, or other graphic libraries.
498 Delete config.cache, then rerun configure adding the following options to
499 configure (among the other options you use):
500 --with-libs-from="-L/usr/local/lib"
501 --with-incs-from="-I/usr/local/include -I/usr/local/include/tiff"
502 Put the paths where your graphic libs and their corresponding header files are
503 located. You can put multiple paths in any of these options, as the example
504 of --with-incs-from shows. Just put a space between them.
507 == configure doesn't detect libXpm.
509 * Check if you have a symbolic link from libXpm.so.4.9 to libXpm.so
512 == Segmentation fault on startup
514 * Check if the version of libXPM you have is at least 4.7
516 * Check if you have an updated version of ~/GNUstep/Defaults/WindowMaker
518 If you're not sure, try renaming ~/GNUstep to ~/GNUtmp and then run wmaker.inst
520 == "...: your machine is misconfigured. gethostname() returned (none)"
522 * the hostname of your machine is set to something invalid, that starts
523 with a parenthesis. Do a man hostname for info about how to set it.
526 == The root menu contains only 2 entries. ("XTerm" and "Exit...")
528 * Window Maker is not finding cpp (the C preprocessor). If your cpp is
529 not located in /lib/cpp, edit src/config.h and correct the path in
532 == checking lex output file root... configure: error: cannot find output from true; giving up
534 * Read the REQUIREMENTS section of this file.
537 LOCALES/INTERNATIONALIZATION
538 ============================
540 Window Maker has national language support. To enable national language
541 support, you must compile Window Maker with some additional parameters.
544 0 - You must have the GNU gettext package installed. It can be
545 obtained at ftp://prep.ai.mit.edu/pub/gnu/gettext-nnn.tar.gz
547 Steps 1 to 3 can be skipped if you use the Install script.
549 1 - You have to select the languages you want to support. Set the
550 LINGUAS to the list of locales you want. English is always
553 setenv LINGUAS "pt ja de"
558 export LINGUAS;LINGUAS="pt ja de"
561 The list of supported locales can be found in po/README.
562 English is the default language.
564 Read po/README if you wish to translate and maintain locale files
567 2 - Additionally, if your language uses multi-byte characters, such
568 as Japanese or Korean, you must set the MultiByteText option to YES
569 in ~/GNUstep/Defaults/WMGLOBAL
571 3 - Configure, build and install Window Maker normally.
573 4 - To select a particular locale at runtime you must set the LANG
574 environment variable to the locale you want. For example, if you want to set
575 the portuguese locale, you must run
583 in Bourne sh and similars
585 Note: If you have the LC_CTYPE environment variable set, you must
586 unset it before running wmaker.
588 For menu definition files, Window Maker searches for them in the
589 following order (for brazilian portuguese, in this case):
596 5 - If you chose a language that uses multi-byte characters, you must
597 configure the fonts appropriately. Read the manual page for XCreateFontSet
598 to have more details about it. You must change the ~/G/D/WindowMaker file
599 for fonts used in titlebars, menus and other things. For fonts used in
600 dialog windows, change ~/G/D/WMGLOBAL. The %d in the font names must not be
601 removed. You can also use the supplied wsetfont script for the task.
602 Read the script itself for instructions.
604 For example, you can specify the following in ~/G/D/WindowMaker:
606 WindowTitleFont = "-*-helvetica-bold-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
607 MenuTitleFont = "-*-helvetica-bold-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
608 MenuTextFont = "-*-helvetica-medium-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
609 IconTitleFont = "-*-helvetica-medium-r-normal-*-8-*,-*-*-medium-r-normal-*-12-*";
610 ClipTitleFont = "-*-helvetica-bold-r-normal-*-10-*,-*-*-medium-r-normal-*-12-*";
611 DisplayFont = "-*-helvetica-medium-r-normal-*-12-*,-*-*-medium-r-normal-*-12-*";
613 and in ~/G/D/WMGLOBAL:
615 SystemFont = "-*-*-medium-r-normal-*-%d-*-*-*-*-*-*-*";
616 BoldSystemFont = "-*-*-medium-r-normal-*-%d-*-*-*-*-*-*-*";
618 The above 2 fonts are only used by applications that use WINGs (WindowMaker
621 The wsetfont script that's supplied will allow you to change the font
622 settings in a easier way. Take a look in the script for details on usage.