[Fwd: Re: [MAXIMA] Extending functionality]



> From: Ted Hilts
>
>(1-src) The CVS repository only shows a list of the modules -- mostly Lisp files.

The TCL code for xmaxima is in the interfaces/xmaxima subdirectory and subdirectories
of that.

> (2-src)  The download page lays out binanry and source where a clear distinction 
> is made between Linux (in the form of rpm files) and Win16 exe file which self 
> installs.  The only file I can see on the download page which might be used for 
> building the Windows executeable package is "maxima-5.9.3.99rc1.tar.gz" which is 
> the same for both candidate listings.  

Yes.  The source code is common.  Windows installation instructions are in INSTALL.win32.
I updated this in CVS recently.


> (3-src) Is "maxima-5.9.3.99rc1.tar.gz" the source code for building the self installed 
> Windows executeable????

Yes.  See above.


> (4-src) With regards to a Windows build -- how do I go about it -- are there instructions 
> somewhere specific to a Windows build?  

Yes.  See above.

> Could I do the build using CYGWIN?

Yes, using cygwin clisp:
  ./configure
  make
  make check
  make install

At present xmaxima doesn't work on cygwin.  The problem may well be trivial.
I just use cywin maxima for command line stuff and win32 maxima if I want a gui.

> (5-src) I assume I have to uninstall the present version before letting the self 
> installing Windows binary execute?  This gets me back to TCL.  

No.  Multiple versions coexist.

> The present installation came with TCL so I ended up having TCL (from CYGWIN), 
> TCL from  KOMOTO and TCL from an independent install.

Yep, but disk is cheap.


NOTICE
This e-mail and any attachments are private and confidential and may contain privileged information. If you are not an authorised recipient, the copying or distribution of this e-mail and any attachments is prohibited and you must not read, print or act in reliance on this e-mail or attachments.
This notice should not be removed.