How to Compile Yacas for EPOC32
===============================

Installing Programming Tools
----------------------------

Obs.: the instructions below use Windows 98SE, so some comments should
be adapted if another Windows OS is used.

Install the Microsoft Visual C++ 5/6.

Install the EPOC C++ SDK. I recommend using "SUBST" to map the
installation directory to a "P:" drive (for example), so the
"Autoexec.bat" would have these lines :

SUBST P: E:\EPOCXX
SET PATH=P:\epoc32\gcc\bin;P:\epoc32\tools;%PATH%

Unzip the "Yacas-1.0.56.zip" onto "P:\", then the source code would be
available at the directory "P:\yacas-1.0.56\src>".

I recommend installing Microsoft Windows 95 Power Toys, that has the tool :
***DOS PROMPT HERE 1.0.  
Right-click a folder and start an MS-DOS prompt right here, right away.
TIP: You can even right-click the tiny icon in the far upper left hand
corner of an open folder.

Compiling Yacas for EPOC32
--------------------------

Open a MS-DOS prompt at "P:\yacas-1.0.56\src".

EPOC32 Windows emulator (WINS)
++++++++++++++++++++++++++++++

To compile the server and client of Yacas for the EPOC32 Windows
emulator (WINS), do the following :

In the first time, delete any "Yacas.*" from
"P:\EPOC32\Wins\C\System\Apps\Yacas\", copy the file
"P:\yacas-1.0.56\epoc\Yacas.aif" to
"P:\EPOC32\Release\WINS\Deb\Z\System\Apps\Yacas" and the directory
"scripts" to "P:\EPOC32\Wins\C\System\Apps\Yacas\".

a) To use the Microsoft Visual C++ 5/6, type

makmake -makework eposerv vc5     // Usually in the first time
makmake epocserv vc5
makmake -makework epoccli vc5     // Usually in the first time
makmake epoccli vc5

then double click on the resultant "*.dsw files, and you should select
"Build/Set Active Configuration/Win32 Debug". To run the emulator, the
executable is "P:\epoc32\release\wins\deb\epoc.exe". You only need to
redo this procedure if the "epocserv.mmp" or "epoccli.mmp" are modified.

For epocserv, remove "compressedfiles.cpp" and "minilzo.c" from the
header files list, because otherwise these files will be compiled twice.

b) To use the MS-DOS command-line, type

makmake -clean epocserv wins       // Usually in the first time
makmake -makework epocserv wins    // Usually in the first time
makmake epocserv wins
nmake -f epocserv.wins > epocserv.wins.log

makmake -clean epoccli wins       // Usually in the first time
makmake -makework epoccli wins    // Usually in the first time
makmake epoccli wins
nmake -f epoccli.wins > epoccli.wins.log

There will be some repetitive warning messages if you compile using MS
Visual C++ 6, they are not important.

Then a Yacas icon will appear on the Extra bar of the Epoc32 Windows
emulator.

Real EPOC32 machine (MARM)
++++++++++++++++++++++++++

To compile Yacas for MARM, i.e., a real EPOC32 machine :

makmake -clean epocserv marm       // Usually in the first time
makmake -makework epocserv marm    // Usually in the first time
makmake epocserv marm
nmake -f epocserv.marm > epocserv.marm.log

makmake -clean epoccli marm       // Usually in the first time
makmake -makework epoccli marm    // Usually in the first time
makmake epoccli marm
nmake -f epoccli.marm > epoccli.marm.log

There will be some repetitive warning messages if you compile using MS
Visual C++ 6, they are not important.

Use the "P:\yacas-1.0.56\epoc\GenSIS.bat" (or "epocbuild.bat" to rebuild
the icons, etc.) to create the SIS file that can be installed on a real
EPOC32 machine. Or you can manually copy only the modified files
"P:\EPOC32\Release\MARM\Rel\Yacas.app",
"P:\EPOC32\Release\MARM\Rel\YacasServer.exe" and
"P:\EPOC32\Release\MARM\Rel\Yacas.rsc" to "?:\System\Apps\Yacas\" of the
EPOC32 machine as a faster solution.

Then a Yacas icon will appear on the Extra bar of the Epoc32 machine.

Yacas community
---------------

If you want to contribute for developing Yacas for EPOC/Symbian, go to

www.RobertoColistete.net/Yacas

to see some future possibilities of development. The main site for Yacas
is the well known

http://yacas.sourceforge.net

Please contact the Yacas authors about comments, developing the source code, 
testing, documenting, etc.