The following describes actions that should be taken to properly setup EWG.
In the following I am using the Unix notation for environment variables ${FOOBAR}, even when talking about windows (where the notation is %FOORBAR%).
Set the environment variable ${EWG} to the directory where you unpacked the EWG tar ball to or where you retrieved the CVS version to
Put ${EWG}/bin into your ${PATH} environment variable
Set ${GOBO_EIFFEL} to a supported Eiffel compiler. This compiler will then be used to generate wrappers for. The following is a list of supported values:
se
ise
Set ${GOBO_CC} to a supported C compiler. If your Eiffel compiler uses a C compiler as a backend, this option needs to be set to the C compiler you use as backend. The following is a list of supported values:
gcc ... Gnu Compiler Collection
msc ... Visual C++
bcb ... Borland C++
lcc ... lcc-win32
Please note that only gcc and msc are officially supported. Lcc and bcb have some known problems, but you are welcome to help me fix them (;
The following example shows a possible setup for windows:
set EWG=C:\ewg set PATH=%PATH%;%EWG%\bin set GOBO_EIFFEL=se set GOBO_CC=msc
The following example shows a possible setup for linux:
export EWG=/home/aleitner/ewg export PATH=$PATH:$EWG\bin export GOBO_EIFFEL=ise export GOBO_CC=gcc
You have to make sure that whatever Eiffel compiler or C compiler gets used can be located via the PATH environment variable. For Visual C, there is usually a special command line window you can open, that automatically has everything necessary set. ISE Eiffel and SmartEiffel have to be added to PATH by hand. GCC can (at least on Unix like systems) usually be located via PATH by default. If in doubt consult the corresponding tool documentation.