[Gcl-devel] ANSI and CltL1 installers for Windows

[Mike Thomas]

Hi Camm.

First, I put together an installer for the stable branch (CLtL1) per CVS
today and expect it should be on your download site within 24 hours.  The
file name is "gcl_2.6.1.mingw32_japi_xdr_20040105.zip".

Hopefully the problems Bill had with the system directory and installation
are gone.


Second, rather than building separate installers for ANSI and CLtL1 builds I
would prefer to have both executables in a single installer (with separate
start menu shortcuts etc) until we don't need a CLtL1 build on Windows.

This raises the question of whether there is, or will be in the future,
substantial difference between the "saved_gcl" produced during a CLtL1 build
and the "saved_gcl" produced as an intermediate step in the production of
"saved_ansi_gcl.exe" during a "configure --with-ansi" build.

As it is PCL which is causing instability on Windows, maybe we can provide a
stable ANSI build modulo PCL until that problem is fixed.  That would
hopefully be sufficient (in the interim) for Maxima, ACL2 and Axiom
development on Windows, as I believe they do not require CLOS.

What do you think?


Third, could you please briefly describe the differences between the various
executables you are producing (especially: What is clcs?):

unixport/raw_ansi_gcl.exe  unixport/saved_ansi_gcl.exe
unixport/raw_gcl.exe       unixport/saved_gcl.exe
unixport/raw_pcl_gcl.exe   unixport/saved_pcl_gcl.exe
unixport/raw_pre_gcl.exe   unixport/saved_pre_gcl.exe


Cheers

Mike Thomas.