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 gcc (or some other ANSI C compiler)
68 glibc development files (usually glibc-devel in Linux distributions)
69 X development files (XFree86-devel or something similar)
71 - autoconf, automake and libtool
77 and its dependencies (such as freetype2 and fontconfig)
78 You will also need the development files for it (xft2-devel)
84 These libraries are not required to make Window Maker work, but they
85 are supported in case you want to use them. Version numbers are those
86 that I have (and therefore, guraranteed to work), but other versions
91 Older versions may not work!!!
92 Available at ftp://sunsite.unc.edu/pub/Linux/libs/X/
94 There is builtin support for XPM files, but it will not
95 load images in some uncommon encodings.
97 - libpng 0.96 or newer and zlib
98 For PNG image support.
99 http://www.cdrom.com/pub/png/
101 - libtiff 3.4 or newer
102 For TIFF image support.
103 You can get it at ftp://ftp.sgi.com/graphics/tiff
105 - libjpeg 6.0.1 or newer
106 For JPEG image support
109 - libgif 2.2 or libungif
110 For GIF image support
111 ftp://prtr-13.ucsc.edu/pub/libungif/
114 If you want to use translated messages, you will need GNU gettext.
115 Other versions of gettext are not compatible and will not work.
116 Get the GNU version from ftp://ftp.gnu.org
123 These options can be passed to the configure script to enable/disable
124 some Window Maker features. Example:
126 ./configure --enable-modelock --disable-gif
128 will configure Window Maker with modelock supported and disable gif support.
129 Normally, you won't need any of them.
131 To get a list of other options, run ./configure --help
134 specify additional paths for libraries to be searched.
135 The -L flag must precede each path, like:
136 --with-libs-from="-L/opt/libs -L/usr/local/lib"
139 specify additional paths for header files to be searched.
140 The -I flag must precede each paths, like:
141 --with-incs-from="-I/opt/headers -I/usr/local/include"
144 disable use of the MIT shared memory extension. This will slow down
145 texture generation a little bit, but in some cases it seems to be
146 necessary due to a bug that manifests as messed icons and textures.
149 disable support for mwm window manager hints
152 remove things that are already supported in desktop environments,
153 like KDE and GNOME. Disabled things are: window list, root
154 applications menu, multiple window selection. Note that you will not
155 be able to exit Window Maker from itself anymore; you will have to
156 use kill with the SIGTERM signal or exit it from KDE. It is not
157 advisable to enable it.
160 XKB language status lock support. If you don't know what it is you
161 probably don't need it.
164 disables use of the XPM library even if it is available on your
168 disables use of PNG library
171 disable use of TIFF library
174 disable use of GIF library
177 disable use of JPEG library
180 disables shaped windows (for oclock, xeyes etc.)
183 PLATFORM SPECIFIC NOTES:
184 ========================
189 From: Anton Ivanov <aivanov@eu.level3.net>
190 To: Marcelo E. Magallon <mmagallo@debian.org>
191 Subject: Re: Is the WindowMaker package working ok on Alpha?
195 > I was reading some docs on the WindowMaker tarball, and found this:
197 > | - DEC/Alpha machines
198 > | You might need to pass the --disable-shm flag to configure,
199 > | like ./configure --disable-shm
201 > is anyone having problems with WindowMaker on Alpha? Can someone
202 > please test this? Should the flag be passed when building on Alpha?
204 Disclaimer: alphas under my command have never run X and are least likely to
205 suddenly start running it anytime soon.
207 Alpha used to have some ridiculously low amount of shared memory
209 So quite a lot of apps used to barf. Namely - cdrecord, mysql server, etc.
211 Check where is yours at the moment and raise it to a more appropriate
212 value by either catting to the appropriate /proc entry or changing the
213 /usr/src/linux/include/asm/shmparam.h.
215 Otherwise the shared memory on alpha should be fully functional and I
216 see no reason to disable it. Mine are bumped up to 32 or more on most
219 And If I recall correctly the comments in that file are actually
220 wrong. Value is not bytes, but in machine size word. For alpha *8.
222 As I said - I do not run X on them so all #include "stdisclaimer.h"
227 - SCO Unix - run configure like
228 CFLAGS="-belf -DANSICPP" ./configure
231 If you have gcc installed, run configure as:
232 CPP_PATH="gcc -E -x c" ./configure
233 Sun's cpp lacks some features needed by Window Maker and it can
234 cause problems when parsing the config files.
235 You also might need to use the --with-libs-from and --with-incs-from
236 to supply the directory where libtiff is located.
237 Someone mailed me that you also must make /usr/local/lib be the
238 first path in LD_LIBRARY_PATH to make it work.
240 If you have a Ultra Creator 3D or some other machine with high-end
241 graphics, be sure to start the X server with the default visual
242 set to 24bpp or you might experience problems with mangled colors.
243 This is a wmaker bug and will be fixed.
245 - GNU/Linux in general
246 Make sure you have /usr/local/lib in /etc/ld.so.conf and that you
247 run ldconfig after installing.
248 Uninstall any packaged version of Window Maker before installing a new
252 RedHat systems have several annoying problems. If you use it,
253 be sure to follow the steps below or Window Maker will not work:
255 * if you installed the Window Maker that comes with RedHat, uninstall
258 * make sure you don't have the LANG and LINGUAS environment variables
261 * make sure you have /usr/local/bin in your PATH environment
264 * make sure you have /usr/local/lib in /etc/ld.so.conf before running
268 You will need to have the latest version of Xpmac. Older versions
269 seem to have bugs that cause the system to hang.
272 If you want JPEG and TIFF support, make sure you have libtiff-dev
273 and libjpeg-dev installed.
276 If you installed the Window Maker package from SuSE,
277 uninstall it before trying to compile wmaker or you
280 - MetroX (unknown version)
281 MetroX has a bug that corrupts pixmaps that are set as window
282 backgrounds. If you use MetroX and has weird problems with
283 textures, do not use textures in titlebars. Or use a different
291 For a quick start, type the following in your shell prompt:
296 then, login as root and type:
301 or if you want to strip the debugging symbols from the binaries and make them
302 smaller, you can instead type:
307 This will build and install Window Maker with default parameters.
309 If you want to customize some compile-time options, you can do the
312 1. (optional) Look at the CONFIGURE OPTIONS section above for the
313 options available. Also run:
317 to get a complete listing of other options that are available.
319 2. Run configure with the options you want. For example, if you
320 want to use the --enable-modelock option, type:
322 ./configure --enable-modelock
324 3. (optional) Edit src/wconfig.h with your favorite text editor
325 and browse through it for some options you might want to change.
327 4. Compile. Just type:
331 5. Login as root (if you can't do that, read the "I don't have the
332 root password :-(" section) and install Window Maker in your system:
337 User specific configuration
338 ---------------------------
340 These instructions do not need to be followed when upgrading Window Maker
341 from an older version, unless stated differently in the NEWS file.
343 Every user on your system that wishes to run Window Maker must do the
346 1. Install Window Maker configuration files in your home directory.
350 wmaker.inst will install Window Maker configuration files and will
351 setup X to automatically launch Window Maker at startup.
355 You can type "man wmaker" to get some general help for configuration
358 Read the User Guide for a more in-depth explanation of Window Maker.
360 You might want to take a look at the FAQ too.
364 Installing the extras package
365 -----------------------------
367 Unpack WindowMaker-extra-<version-number>.tar.gz in /usr/local/share
369 You can get the file at ftp://ftp.windowmaker.org. This file is optional
370 and only have a few icons, and themes. Look for the latest <version-number>
372 Also there is a WindowMaker-extra.readme to instruct you where that package
377 I don't have the root password :(
378 ---------------------------------
380 If you can't get superuser privileges (can't be root) you can install
381 wmaker in your own home directory. For that, supply the --prefix option
382 when running configure in step 2 of building Window Maker. You will
383 also need to supply the --with-appspath option, to specify the path for
386 ./configure --prefix=/home/jshmoe --with-appspath=/home/jshmoe/GNUstep/Apps
389 Then make /home/jshmoe/bin be included in your search PATH, add
390 /home/jshmoe/lib to your LD_LIBRARY_PATH environment variable and run
393 Of course, /home/jshmoe is supposed to be replaced with your actual home
401 If you are upgrading from an older version of Window Maker:
403 1. Configure and build Window Maker as always
404 2. Install Window Maker (but do not run wmaker.inst)
405 3. Read the NEWS file and update your configuration files if necessary.
411 When you have some trouble during configuration (while running configure),
412 like not being able to use a graphic format library you think you have
413 installed, look at the config.log file for clues of the problem.
416 == Error with loading fonts, even if they exist.
418 Try rebuilding without NLS support.
420 == Error when configuring
422 ltconfig: unrecognized option `--no-reexec'
423 Try `ltconfig --help' for more information.
424 configure: error: libtool configure failed
426 remove the --no-reexec option from aclocal.m4 and reconfigure
427 Also make sure the autoconf and automake versions you have installed are:
432 Note that it must not be libtool 1.2b, it must be libtool 1.3,
435 == configure doesn't detect libtiff, or other graphic libraries.
437 Delete config.cache, then rerun configure adding the following options to
438 configure (among the other options you use):
439 --with-libs-from="-L/usr/local/lib"
440 --with-incs-from="-I/usr/local/include -I/usr/local/include/tiff"
441 Put the paths where your graphic libs and their corresponding header files are
442 located. You can put multiple paths in any of these options, as the example
443 of --with-incs-from shows. Just put a space between them.
446 == configure doesn't detect libXpm.
448 * Check if you have a symbolic link from libXpm.so.4.9 to libXpm.so
451 == Segmentation fault on startup
453 * Check if the version of libXPM you have is at least 4.7
455 * Check if you have an updated version of ~/GNUstep/Defaults/WindowMaker
457 If you're not sure, try renaming ~/GNUstep to ~/GNUtmp and then run wmaker.inst
459 == "...: your machine is misconfigured. gethostname() returned (none)"
461 * the hostname of your machine is set to something invalid, that starts
462 with a parenthesis. Do a man hostname for info about how to set it.
465 == The root menu contains only 2 entries. ("XTerm" and "Exit...")
467 * Window Maker is not finding cpp (the C preprocessor). If your cpp is
468 not located in /lib/cpp, edit src/config.h and correct the path in
471 == checking lex output file root... configure: error: cannot find output from true; giving up
473 * Read the REQUIREMENTS section of this file.
476 LOCALES/INTERNATIONALIZATION
477 ============================
479 Window Maker has national language support. To enable national language
480 support, you must compile Window Maker with some additional parameters.
483 0 - You must have the GNU gettext package installed. It can be
484 obtained at ftp://prep.ai.mit.edu/pub/gnu/gettext-nnn.tar.gz
486 Steps 1 to 3 can be skipped if you use the Install script.
488 1 - You have to select the languages you want to support. Set the
489 LINGUAS to the list of locales you want. English is always
492 setenv LINGUAS "pt ja de"
497 export LINGUAS;LINGUAS="pt ja de"
500 The list of supported locales can be found in po/README.
501 English is the default language.
503 Read po/README if you wish to translate and maintain locale files
506 2 - Additionally, if your language uses multi-byte characters, such
507 as Japanese or Korean, you must set the MultiByteText option to YES
508 in ~/GNUstep/Defaults/WMGLOBAL
510 3 - Configure, build and install Window Maker normally.
512 4 - To select a particular locale at runtime you must set the LANG
513 environment variable to the locale you want. For example, if you want to set
514 the portuguese locale, you must run
522 in Bourne sh and similars
524 Note: If you have the LC_CTYPE environment variable set, you must
525 unset it before running wmaker.
527 For menu definition files, Window Maker searches for them in the
528 following order (for brazilian portuguese, in this case):