If you want the curse-based interface, try:

With gcc compiler and ncurses:
$ make -f Makefile.ncurses.gcc

With HP-UX cc and ncurses:
$ make -f Makefile.ncurses.HP-UX

With HP-UX cc and curses:
$ make -f Makefile.curses.HP-UX

With SunOS cc and curses:
% make -f Makefile.curses.SunOS

With gcc compiler and PDcurses:
$ make -f Makefile.pdcurses.gcc

You may need to edit the makefile first.
You may need to convert the source files in ../src
to unix text first. E.g. with 'dos2unix'.

   ----------------------------------------------

To compile wcd with plain stdin/stdout interface type:

$ make

You may need to edit file 'Makefile' first if you don't
have the gcc compiler.

   ----------------------------------------------

Wcd can also be compiled with Imake:

$ xmkmf
$ make depend
$ make
$ make install

The last command copies wcd.exe to your ~/bin/ directory.
Note: Imake will overwrite the makefile "Makefile".

   ----------------------------------------------
*** PORTABILITY ***

See also section "Source code" in file wcd.txt.

--

Cygwin

The Cygwin version of wcd makes use of WIN32 API functions
to scan Windows SMB LAN servers. So library 'mpr' is included
during linking.

--

A compile error occurs when you use gcc < 3.0 and
<stdbool.h> is included somewhere (e.g. in curses.h).

Apply the following patch:

$ cd ../src
$ patch -p1 < patch/wcd_bool.diff

(thanks to Kevin M. Rosenberg)

--

Conflicting curses.h ncurses.h

On some systems curses.h is conflicting with ncurses.h. To compile wcd you can
solve this by creating a symbolic link curses.h in the wcd source directory
pointing to the ncurses.h file and adding -I. to CFLAGS in
Makefile.ncurses.gcc.

This problem was seen on a BSDI BSD/OS 4.0 system. /usr/local/include/ncurses.h
......................................................................

Make sure that you have a copy of wcd.exe in a directory listed in your
PATH environment. If you install a local copy, for example in your
$HOME/bin directory, this directory must be added to the PATH
environment.

Copy file wcd.1 somewhere in $MANPATH .

......................................................................

Note that the current working directory of a Bourne-like or C shell can only be
changed by the builtin cd command. Therefore the binary is always called by a
function or alias. The function or alias sources a shell script (go-script)
which is generated by the binary wcd.exe. Wcd can only work after the function
or alias is defined.

......................................................................

 ===== Bourne-like shells: =====

Korn Shell (ksh, pdksh), Bourne Again Shell (bash), Z shell (zsh), ash, ...

1)

 copy wcd.exe to your $HOME/bin directory.

2)

 Add the following function to a startup file of your shell. For instance in:
$HOME/.kshrc (ksh)
$HOME/.bashrc (bash)
$HOME/.zshenv (zsh)

function wcd
{
   $HOME/bin/wcd.exe $*
   . $HOME/bin/wcd.go
}


Start a new shell


 ===== C Shell (csh): =====

1)

 copy wcd.exe to your $HOME/bin directory.

2)

 Add the following alias to your $HOME/.cshrc
 file.

alias wcd "$HOME/bin/wcd.exe \!* ; source $HOME/bin/wcd.go"

Start a new C Shell


......................................................................

There are more detailed information and tips about installing wcd
in file wcd.txt.

