2 Installation Instructions for Window Maker
8 (ie: I've heard someone has compiled it on...)
10 - Intel/Linux RedHat 4.2 (primary platform)
11 - Intel/Linux other distributions
12 - Sparc/Linux RedHat 5.1
14 - Alpha/Linux RedHat 5.1
16 - Solaris 2.5.1, 2.5.2
23 - AIX 4.1.4 / IBM PowerPC
25 - DEC Alpha/Digital UNIX 4.x
30 Patches to make it work on other platforms are welcome.
36 The following software is required to use Window Maker:
39 Window Maker can be compiled in older versions of X, like X11R5
40 (Solaris) or X11R4 (OpenWindows) but it will not work 100% correctly.
41 In such servers there will not be application icons and you'll have
42 trouble using the dock. Upgrading the client libraries (Xlib, Xt etc)
43 will help if you can't upgrade the server.
45 The following is required to build Window Maker:
48 If you will build Window Maker, make sure you have gcc (or some
49 other ANSI C compiler) and the X header files installed. Specially
50 for newbie Linux users: you must install all X development packages
51 and the gcc suite. Otherwise you won't be able to build any X
52 program, including Window Maker.
54 - autoconf and automake
55 autoconf and automake are not required, but if you have them
56 installed, make sure you have autoconf 2.12 and automake 1.3 or
57 newer. If you have an older version, disable them by temporarily
58 renaming them to something else or uninstalling them from your
61 - lex (or flex) and yacc (or bison)
62 These are used by libPropList. lex is actually not needed since
63 it's output file is included, but either me or automake is stupid,
64 causing the configure script for libPropList to simply abort for no
65 convincent reason if lex is not found.
71 These libraries are not required to make Window Maker work, but they
72 are supported in case you want to use them. Version numbers are those
73 that I have (and therefore, guraranteed to work), but other versions
74 might work too. Tell me if you made wmaker work with some library
75 with a version older than the stated here.
79 Older versions may not work!!!
80 Available at ftp://sunsite.unc.edu/pub/Linux/libs/X/
82 There is builtin support for XPM files, but it will not
83 load images in some uncommon encodings.
85 - libpng 0.96 or newer and zlib
86 For PNG image support.
88 - libtiff 3.4 or newer
89 For TIFF image support.
90 You can get it at ftp://ftp.sgi.com/graphics/tiff
92 - libjpeg 6.0.1 or newer
93 For JPEG image support
95 - libgif 2.2 or libungif
99 If you want to use translated messages, you will need GNU gettext.
100 Other versions of gettext are not compatible and will not work.
101 Get the GNU version from ftp://prep.ai.mit.edu
103 Most of these can be get from ftp.uu.net/pub/graphics
109 These options can be passed to the configure script to enable/disable
110 some Window Maker features. Example:
112 ./configure --enable-kanji
114 will configure Window Maker with kanji (and other multi-byte) characters
118 To get a list of other options, run ./configure --help
120 --enable-sound enable support of sound effects module
122 --disable-xpm disables use of the XPM library even if it is available on
125 --disable-png disables use of PNG library
127 --disable-tiff disable use of TIFF library
129 --disable-gif disable use of GIF library
131 --disable-jpeg disable use of JPEG library
133 --disable-shape disables shaped windows (for oclock, xeyes etc.)
135 --enable-debug adds extra debugging information. Do not use it
136 unless you're debugging Window Maker.
138 --enable-kanji support to display Kanji characters, Korean, Chinese
139 and other languagues that require special characters.
141 --enable-single-icon enables the collapsing of all appicons of the
142 WM_CLASS+WM_INSTANCE into a single one. This feature is not
143 supported at all by the developers. If you have some trouble with it,
144 contact it's author: Christopher Seawood <cls@seawood.org>
146 --disable-shm disable use of the MIT shared memory extension. This will
147 slow down texture generation.
149 --enable-modelock XKB language status lock support. If you don't know
150 what it is you probably don't need it.
153 PLATFORM SPECIFIC NOTES:
154 ========================
155 - SCO Unix - run configure like
156 CFLAGS="-belf -DANSICPP" ./configure
159 If you have gcc installed, run configure as:
160 CPP_PATH="gcc -E -x c" ./configure
161 Sun's cpp lacks some features needed by Window Maker and it can
162 cause problems when parsing the config files.
163 You also might need to use the --with-gfx-libs and --with-gfx-incs
164 to supply the directory where libtiff is located.
167 Make sure you don't have the LANG and LINGUAS environment variables
168 set to en_RN. Also, make sure you have /usr/local/bin in your
169 PATH environment variable, as for some mysterious reason the folks
170 at RedHat did not include it in the default configuration files
174 You will need to have the latest version of Xpmac. Older versions
175 seem to have bugs that cause the system to hang.
178 If you want JPEG and TIFF support, make sure you have libtiff-dev
179 and libjpeg-dev installed.
182 If you installed the Window Maker package from SuSE,
183 uninstall it before trying to compile wmaker or you
186 - MetroX (unknown version)
187 MetroX has a bug that corrupts pixmaps that are set as window
188 backgrounds. If you use MetroX and has weird problems with
189 textures, do not use textures in titlebars. Or use a different
196 Unpack WindowMaker-data.tar.gz and move the pixmaps directory in it
197 to /usr/local/share/pixmaps
199 You can get the file at ftp://ftp.windowmaker.org. This file is optional
200 and only have a few icons.
205 For a quick start, type the following in your shell prompt:
210 then, login as root and type:
214 or if you want to strip the debugging symbols from the binaries and make them
215 smaller, you can instead type:
219 This will build and install Window Maker with default parameters.
221 If you want to customize some compile-time options, you can do the
224 1. (optional) Look at the CONFIGURE OPTIONS section above for the
225 options available. Also run:
229 to get a complete listing of other options that are available.
231 2. Run configure with the options you want. For example, if you
232 want to use the --enable-kanji option, type:
234 ./configure --enable-kanji
236 3. (optional) Edit src/wconfig.h with your favorite text editor
237 and browse through it for some options you might want to change.
239 4. Compile. Just type:
243 5. Login as root (if you can't do that, read the "I don't have the
244 root password :-(" section) and install Window Maker in your system:
249 User specific configuration
250 ---------------------------
252 These instructions do not need to be followed when upgrading Window Maker
253 from an older version, unless stated differently in the NEWS file.
255 Every user on your system that wishes to run Window Maker must do the
258 1. Install Window Maker configuration files in your home directory.
262 wmaker.inst will install Window Maker configuration files and will
263 setup X to automatically launch Window Maker at startup.
267 You can type "man wmaker" to get some general help for configuration
270 Read the User Guide for a more in-depth explanation of Window Maker.
272 You might want to take a look at the FAQ too.
275 I don't have the root password :(
276 ---------------------------------
278 If you can't get superuser privileges (can't be root) you can install
279 wmaker in your own home directory. For that, supply the --prefix option
280 when running configure in step 2 of building Window Maker. You will
281 also need to supply the --with-appspath option, to specify the path for
284 ./configure --prefix=/home/jshmoe --with-appspath=/home/jshmoe/GNUstep/Apps
287 Then make /home/jshmoe/bin be included in your search path and run
294 If you are upgrading from an older version of Window Maker:
296 1. Configure and build Window Maker as always
297 2. Install Window Maker (but do not run wmaker.inst)
298 3. Read the NEWS file and update your configuration files,
304 When you have some trouble during configuration (while running configure),
305 like not being able to use a graphic format library you think you have
306 installed, look at the config.log file for clues of the problem.
309 == Error during build of libPropList
311 make: *** No rule to make target `libPropList.a.c', needed by
312 `libPropList.a.o'. Stop.
314 Make sure the autoconf and automake versions you have installed are at
319 If you are using the RPM's that come with RedHat 4.x, don't use them.
320 It is broken. Uninstall the RPM and reinstall a fresh package from
321 ftp://prep.ai.mit.edu or any mirror.
323 == configure doesn't detect libtiff, or other graphic libraries.
325 Delete config.cache, then rerun configure adding the following options to
326 configure (among the other options you use):
327 --with-gfx-libs="-L/usr/local/lib"
328 --with-gfx-incs="-I/usr/local/include -I/usr/local/include/tiff"
329 Put the paths where your graphic libs and their corresponding header files are
330 located. You can put multiple paths in any of these options, as the example
331 of --with-gfx-incs shows. Just put a space between them.
334 == configure doesn't detect libXpm.
336 * Check if you have a symbolic link from libXpm.so.4.9 to libXpm.so
339 == Segmentation fault on startup
341 * Check if the version of libXPM you have is at least 4.7
343 * Check if you have an updated version of ~/GNUstep/Defaults/WindowMaker
345 If you're not sure, try renaming ~/GNUstep to ~/GNUtmp and then run wmaker.inst
347 == "...: your machine is misconfigured. gethostname() returned (none)"
349 * the hostname of your machine is set to something invalid, that starts
350 with a parenthesis. Do a man hostname for info about how to set it.
353 == The root menu contains only 2 entries. ("XTerm" and "Exit...")
355 * Window Maker is not finding cpp (the C preprocessor). If your cpp is
356 not located in /lib/cpp, edit src/config.h and correct the path in
359 == checking lex output file root... configure: error: cannot find output from true; giving up
361 * Read the REQUIREMENTS section of this file.
364 LOCALES/INTERNATIONALIZATION
365 ============================
367 Window Maker has national language support.
368 To enable national language support, you must compile
369 Window Maker with some additional parameters.
371 0 - You must have the GNU gettext package installed. It can be
372 obtained at ftp://prep.ai.mit.edu/pub/gnu/gettext-nnn.tar.gz
374 Steps 1 to 3 can be skipped if you use the Install script.
376 1 - You have to select the languages you want to support. Set the
377 LINGUAS to the list of locales you want. English is always
380 setenv LINGUAS "pt ja de"
385 export LINGUAS;LINGUAS="pt ja de"
388 The list of supported locales can be found in po/README.
389 English is the default language.
391 Read po/README if you wish to translate and maintain locale files
394 2 - Additionally, if your language uses multi-byte characters, such
395 as Japanese or Korean, you must supply the --enable-kanji flag to configure.
397 3 - Configure, build and install Window Maker normally.
399 4 - To select a particular locale at runtime you must set the LANG
400 environment variable to the locale you want. For example, if you want to set
401 the portuguese locale, you must run
409 in Bourne sh and similars
411 Note: If you have the LC_CTYPE environment variable set, you must
412 unset it before running wmaker.
414 For menu definition files, Window Maker searches for them in the
415 following order (for brazilian portuguese, in this case):
422 5 - If you chose a language that uses multi-byte characters, you must
423 configure the fonts appropriately. Read the manual page for XCreateFontSet
424 to have more details about it. You must change the ~/G/D/WindowMaker file
425 for fonts used in titlebars, menus and other things. For fonts used in
426 dialog windows, change ~/G/D/WMGLOBAL. Note that at the moment you can only
427 supply a single font in WMGLOBAL. The %d in the font names must not be
430 For example, you can specify the following in ~/G/D/WindowMaker:
432 WindowTitleFont = "-*-helvetica-bold-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
433 MenuTitleFont = "-*-helvetica-bold-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
434 MenuTextFont = "-*-helvetica-medium-r-normal-*-12-*,-*-*-medium-r-normal-*-14-*";
435 IconTitleFont = "-*-helvetica-medium-r-normal-*-8-*,-*-*-medium-r-normal-*-12-*";
436 ClipTitleFont = "-*-helvetica-bold-r-normal-*-10-*,-*-*-medium-r-normal-*-12-*";
437 DisplayFont = "-*-helvetica-medium-r-normal-*-12-*,-*-*-medium-r-normal-*-12-*";
439 and in ~/G/D/WMGLOBAL:
441 SystemFont = "-*-*-medium-r-normal-*-%d-*-*-*-*-*-*-*";
442 BoldSystemFont = "-*-*-medium-r-normal-*-%d-*-*-*-*-*-*-*";
444 The above 2 fonts are only used by applications that use WINGs (WindowMaker