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.
89 These libraries are not required to make Window Maker work, but they
90 are supported in case you want to use them. Version numbers are those
91 that I have (and therefore, guraranteed to work), but other versions
96 Older versions may not work!!!
97 Available at ftp://sunsite.unc.edu/pub/Linux/libs/X/
99 There is builtin support for XPM files, but it will not
100 load images in some uncommon encodings.
102 - libpng 0.96 or newer and zlib
103 For PNG image support.
104 http://www.cdrom.com/pub/png/
106 - libtiff 3.4 or newer
107 For TIFF image support.
108 You can get it at ftp://ftp.sgi.com/graphics/tiff
110 - libjpeg 6.0.1 or newer
111 For JPEG image support
114 - libgif 2.2 or libungif
115 For GIF image support
116 ftp://prtr-13.ucsc.edu/pub/libungif/
119 If you want to use translated messages, you will need GNU gettext.
120 Other versions of gettext are not compatible and will not work.
121 Get the GNU version from ftp://ftp.gnu.org
128 These options can be passed to the configure script to enable/disable
129 some Window Maker features. Example:
131 ./configure --enable-modelock --disable-gif
133 will configure Window Maker with modelock supported and disable gif support.
136 To get a list of other options, run ./configure --help
139 specify additional paths for libraries to be searched.
140 The -L flag must precede each path, like:
141 --with-libs-from="-L/opt/libs -L/usr/local/lib"
144 specify additional paths for header files to be searched.
145 The -I flag must precede each paths, like:
146 --with-incs-from="-I/opt/headers -I/usr/local/include"
149 disable use of the MIT shared memory extension. This will slow down
150 texture generation a little bit, but in some cases it seems to be
151 necessary due to a bug that manifests as messed icons and textures.
154 disable support for mwm window manager hints
157 remove things that are already supported in desktop environments,
158 like KDE and GNOME. Disabled things are: window list, root
159 applications menu, multiple window selection. Note that you will not
160 be able to exit Window Maker from itself anymore; you will have to
161 use kill with the SIGTERM signal or exit it from KDE. It is not
162 advisable to enable it.
165 XKB language status lock support. If you don't know what it is you
166 probably don't need it.
169 disables use of the XPM library even if it is available on your
173 disables use of PNG library
176 disable use of TIFF library
179 disable use of GIF library
182 disable use of JPEG library
185 disables shaped windows (for oclock, xeyes etc.)
188 PLATFORM SPECIFIC NOTES:
189 ========================
194 From: Anton Ivanov <aivanov@eu.level3.net>
195 To: Marcelo E. Magallon <mmagallo@debian.org>
196 Subject: Re: Is the WindowMaker package working ok on Alpha?
200 > I was reading some docs on the WindowMaker tarball, and found this:
202 > | - DEC/Alpha machines
203 > | You might need to pass the --disable-shm flag to configure,
204 > | like ./configure --disable-shm
206 > is anyone having problems with WindowMaker on Alpha? Can someone
207 > please test this? Should the flag be passed when building on Alpha?
209 Disclaimer: alphas under my command have never run X and are least likely to
210 suddenly start running it anytime soon.
212 Alpha used to have some ridiculously low amount of shared memory
214 So quite a lot of apps used to barf. Namely - cdrecord, mysql server, etc.
216 Check where is yours at the moment and raise it to a more appropriate
217 value by either catting to the appropriate /proc entry or changing the
218 /usr/src/linux/include/asm/shmparam.h.
220 Otherwise the shared memory on alpha should be fully functional and I
221 see no reason to disable it. Mine are bumped up to 32 or more on most
224 And If I recall correctly the comments in that file are actually
225 wrong. Value is not bytes, but in machine size word. For alpha *8.
227 As I said - I do not run X on them so all #include "stdisclaimer.h"
232 - SCO Unix - run configure like
233 CFLAGS="-belf -DANSICPP" ./configure
236 If you have gcc installed, run configure as:
237 CPP_PATH="gcc -E -x c" ./configure
238 Sun's cpp lacks some features needed by Window Maker and it can
239 cause problems when parsing the config files.
240 You also might need to use the --with-libs-from and --with-incs-from
241 to supply the directory where libtiff is located.
242 Someone mailed me that you also must make /usr/local/lib be the
243 first path in LD_LIBRARY_PATH to make it work.
245 If you have a Ultra Creator 3D or some other machine with high-end
246 graphics, be sure to start the X server with the default visual
247 set to 24bpp or you might experience problems with mangled colors.
248 This is a wmaker bug and will be fixed.
250 - GNU/Linux in general
251 Make sure you have /usr/local/lib in /etc/ld.so.conf and that you
252 run ldconfig after installing.
253 Uninstall any packaged version of Window Maker before installing a new
257 RedHat systems have several annoying problems. If you use it,
258 be sure to follow the steps below or Window Maker will not work:
260 * if you installed the Window Maker that comes with RedHat, uninstall
263 * make sure you don't have the LANG and LINGUAS environment variables
266 * make sure you have /usr/local/bin in your PATH environment
269 * make sure you have /usr/local/lib in /etc/ld.so.conf before running
272 * if you have problems that mention an error message with --no-reexec
273 uninstall libtool-1.2b and install libtool-1.3 instead. libtool-1.3
274 can be found in ftp.gnu.org Also read the TROUBLESHOOTING section;
276 * if you installed the Window Maker package from RedHat and are
277 installing a new version of it by hand (compiling yourself), uninstall
278 the package from RedHat before.
280 * make sure you have a symbolic link from /usr/include/X11 to
281 /usr/X11R6/include/X11 (if not, type ln -s /usr/X11R6/include/X11
284 * make sure you have /lib/cpp pointing to the cpp program
286 If you have any doubts in doing any of the stuff above, please
287 don't hesitate to contact the RedHat user support. They will
288 kindly answer to all your questions regarding their system.
289 They also know much more about their own system than us
290 (we don't use RedHat).
294 You will need to have the latest version of Xpmac. Older versions
295 seem to have bugs that cause the system to hang.
298 If you want JPEG and TIFF support, make sure you have libtiff-dev
299 and libjpeg-dev installed.
302 If you installed the Window Maker package from SuSE,
303 uninstall it before trying to compile wmaker or you
306 - MetroX (unknown version)
307 MetroX has a bug that corrupts pixmaps that are set as window
308 backgrounds. If you use MetroX and has weird problems with
309 textures, do not use textures in titlebars. Or use a different
317 For a quick start, type the following in your shell prompt:
322 then, login as root and type:
327 or if you want to strip the debugging symbols from the binaries and make them
328 smaller, you can instead type:
333 This will build and install Window Maker with default parameters.
335 If you want to customize some compile-time options, you can do the
338 1. (optional) Look at the CONFIGURE OPTIONS section above for the
339 options available. Also run:
343 to get a complete listing of other options that are available.
345 2. Run configure with the options you want. For example, if you
346 want to use the --enable-modelock option, type:
348 ./configure --enable-modelock
350 3. (optional) Edit src/wconfig.h with your favorite text editor
351 and browse through it for some options you might want to change.
353 4. Compile. Just type:
357 5. Login as root (if you can't do that, read the "I don't have the
358 root password :-(" section) and install Window Maker in your system:
363 User specific configuration
364 ---------------------------
366 These instructions do not need to be followed when upgrading Window Maker
367 from an older version, unless stated differently in the NEWS file.
369 Every user on your system that wishes to run Window Maker must do the
372 1. Install Window Maker configuration files in your home directory.
376 wmaker.inst will install Window Maker configuration files and will
377 setup X to automatically launch Window Maker at startup.
381 You can type "man wmaker" to get some general help for configuration
384 Read the User Guide for a more in-depth explanation of Window Maker.
386 You might want to take a look at the FAQ too.
390 Installing the extras package
391 -----------------------------
393 Unpack WindowMaker-extra-<version-number>.tar.gz in /usr/local/share
395 You can get the file at ftp://ftp.windowmaker.org. This file is optional
396 and only have a few icons, and themes. Look for the latest <version-number>
398 Also there is a WindowMaker-extra.readme to instruct you where that package
403 I don't have the root password :(
404 ---------------------------------
406 If you can't get superuser privileges (can't be root) you can install
407 wmaker in your own home directory. For that, supply the --prefix option
408 when running configure in step 2 of building Window Maker. You will
409 also need to supply the --with-appspath option, to specify the path for
412 ./configure --prefix=/home/jshmoe --with-appspath=/home/jshmoe/GNUstep/Apps
415 Then make /home/jshmoe/bin be included in your search PATH, add
416 /home/jshmoe/lib to your LD_LIBRARY_PATH environment variable and run
419 Of course, /home/jshmoe is supposed to be replaced with your actual home
427 If you are upgrading from an older version of Window Maker:
429 1. Configure and build Window Maker as always
430 2. Install Window Maker (but do not run wmaker.inst)
431 3. Read the NEWS file and update your configuration files if necessary.
437 When you have some trouble during configuration (while running configure),
438 like not being able to use a graphic format library you think you have
439 installed, look at the config.log file for clues of the problem.
442 == Error with loading fonts, even if they exist.
444 Try rebuilding without NLS support.
446 == Error when configuring
448 ltconfig: unrecognized option `--no-reexec'
449 Try `ltconfig --help' for more information.
450 configure: error: libtool configure failed
452 remove the --no-reexec option from aclocal.m4 and reconfigure
453 Also make sure the autoconf and automake versions you have installed are:
458 Note that it must not be libtool 1.2b, it must be libtool 1.3,
461 == configure doesn't detect libtiff, or other graphic libraries.
463 Delete config.cache, then rerun configure adding the following options to
464 configure (among the other options you use):
465 --with-libs-from="-L/usr/local/lib"
466 --with-incs-from="-I/usr/local/include -I/usr/local/include/tiff"
467 Put the paths where your graphic libs and their corresponding header files are
468 located. You can put multiple paths in any of these options, as the example
469 of --with-incs-from shows. Just put a space between them.
472 == configure doesn't detect libXpm.
474 * Check if you have a symbolic link from libXpm.so.4.9 to libXpm.so
477 == Segmentation fault on startup
479 * Check if the version of libXPM you have is at least 4.7
481 * Check if you have an updated version of ~/GNUstep/Defaults/WindowMaker
483 If you're not sure, try renaming ~/GNUstep to ~/GNUtmp and then run wmaker.inst
485 == "...: your machine is misconfigured. gethostname() returned (none)"
487 * the hostname of your machine is set to something invalid, that starts
488 with a parenthesis. Do a man hostname for info about how to set it.
491 == The root menu contains only 2 entries. ("XTerm" and "Exit...")
493 * Window Maker is not finding cpp (the C preprocessor). If your cpp is
494 not located in /lib/cpp, edit src/config.h and correct the path in
497 == checking lex output file root... configure: error: cannot find output from true; giving up
499 * Read the REQUIREMENTS section of this file.
502 LOCALES/INTERNATIONALIZATION
503 ============================
505 Window Maker has national language support. To enable national language
506 support, you must compile Window Maker with some additional parameters.
509 0 - You must have the GNU gettext package installed. It can be
510 obtained at ftp://prep.ai.mit.edu/pub/gnu/gettext-nnn.tar.gz
512 Steps 1 to 3 can be skipped if you use the Install script.
514 1 - You have to select the languages you want to support. Set the
515 LINGUAS to the list of locales you want. English is always
518 setenv LINGUAS "pt ja de"
523 export LINGUAS;LINGUAS="pt ja de"
526 The list of supported locales can be found in po/README.
527 English is the default language.
529 Read po/README if you wish to translate and maintain locale files
532 2 - Additionally, if your language uses multi-byte characters, such
533 as Japanese or Korean, you must set the MultiByteText option to YES
534 in ~/GNUstep/Defaults/WMGLOBAL
536 3 - Configure, build and install Window Maker normally.
538 4 - To select a particular locale at runtime you must set the LANG
539 environment variable to the locale you want. For example, if you want to set
540 the portuguese locale, you must run
548 in Bourne sh and similars
550 Note: If you have the LC_CTYPE environment variable set, you must
551 unset it before running wmaker.
553 For menu definition files, Window Maker searches for them in the
554 following order (for brazilian portuguese, in this case):
561 5 - If you chose a language that uses multi-byte characters, you must
562 configure the fonts appropriately. Read the manual page for XCreateFontSet
563 to have more details about it. You must change the ~/G/D/WindowMaker file
564 for fonts used in titlebars, menus and other things. For fonts used in
565 dialog windows, change ~/G/D/WMGLOBAL. The %d in the font names must not be
566 removed. You can also use the supplied wsetfont script for the task.
567 Read the script itself for instructions.
569 For example, you can specify the following in ~/G/D/WindowMaker:
571 WindowTitleFont = "-*-helvetica-bold-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
572 MenuTitleFont = "-*-helvetica-bold-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
573 MenuTextFont = "-*-helvetica-medium-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
574 IconTitleFont = "-*-helvetica-medium-r-normal-*-8-*,-*-*-medium-r-normal-*-12-*";
575 ClipTitleFont = "-*-helvetica-bold-r-normal-*-10-*,-*-*-medium-r-normal-*-12-*";
576 DisplayFont = "-*-helvetica-medium-r-normal-*-12-*,-*-*-medium-r-normal-*-12-*";
578 and in ~/G/D/WMGLOBAL:
580 SystemFont = "-*-*-medium-r-normal-*-%d-*-*-*-*-*-*-*";
581 BoldSystemFont = "-*-*-medium-r-normal-*-%d-*-*-*-*-*-*-*";
583 The above 2 fonts are only used by applications that use WINGs (WindowMaker
586 The wsetfont script that's supplied will allow you to change the font
587 settings in a easier way. Take a look in the script for details on usage.