Commit 0dafc2fc authored by Erick's avatar Erick

.

parent 835212eb
......@@ -54,9 +54,9 @@ libffi - a portable foreign function interface library
+++++++++++++++++++++++++++++++++++
The GC, PCRE and GMP libraries provided with STklos are only used if there
are no identical (or higher) versions of these libraries already
installed on the system at configuration time.
The GC, PCRE, LIBFFI and GMP libraries provided with STklos are only
used if there are no identical (or higher) versions of these libraries
already installed on the system at configuration time.
This file contains a set of informations for compiling STklos on
various architectures.
Version 1.0 is known to compile with the standard invocation
configure && make && sudo make install
......@@ -9,13 +7,14 @@ on the following architectures
- MacOS 10.5+ (gcc-4.x 32 and 64 bits)
- FreeBSD 8.x (gcc-4.x 32 bits)
======================================================================
======================================================================
All the informations given below are for old versions (pre-1.0) of
STklos. They are here for the record.
This file contains a set of informations for compiling STklos on
various architectures.
If you experience a new port or confirm/infirm/add informations which
are specified here please send a mail to Erick Gallesio
......
-*- outline -*-
S T k l o s ( v e r s i o n 0 . 9 8 )
S T k l o s ( v e r s i o n 1 . 0 0 )
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
Erick Gallesio
......@@ -9,20 +9,26 @@
* Purpose
STklos is a free Scheme System (nearly) conform to R5RS. The aim of this
implementation is to be fast as well as light. The implementation is
based on an ad-hoc Virtual Machine. STklos can also be compiled as a
library, so that one can easily embed it in an application.
STklos is a free Scheme system compliant with the languages features
defined in R5RS. The aim of this implementation is to be fast as well
as light. The implementation is based on an ad-hoc Virtual
Machine. STklos can also be compiled as a library and embedded in an
application.
The salient points of STklos are:
* efficient and powerful object system based on CLOS providing
- Multiple Inheritance,
- Generic Functions,
- Multi-methods
- an efficient MOP (Meta Object Protocol)
* an efficient and powerful object system based on CLOS providing
o Multiple Inheritance,
o Generic Functions,
o Multi-methods
o an efficient MOP (Meta Object Protocol)
* a simple to use module system
* implements the full tower of numbers defined in R5RS
* easy connection to the GTK+ toolkit
* a full tower of numbers implementation, as defined in R5RS,
* easy connection to the GTK+ toolkit,
* a Perl compatible regular expressions thanks to the PCRE package,
* easily extensible with its ScmPkg mechanism,
* it implements properly tail recursive calls.
* History
......@@ -37,12 +43,10 @@ designed and should be easily embedded in an application (it was not
completely the case with STk).
Whereas STk used the Tk toolkit, STklos used the GTK+ graphical
toolkit. This choice was dictated by the low activity around Tk (no
new widgets for several years) and by, on contrary, the effervescence
around GTK+. STklos is not completely compatible with STk but it
should be easy to port old STk graphical applications (provided that
they use objects). The GTK+ extension can be loaded at run time and
does not require a special interpreter as it was the case with STk.
toolkit. STklos is not completely compatible with STk but it should be
easy to port old STk graphical applications (provided that they use
objects). The GTK+ extension can be loaded at run time and does not
require a special interpreter as it was the case with STk.
* SRFI Support
......@@ -54,27 +58,34 @@ SRFIs. Any help on implementing other SRFIs on STklos is welcome.
* Supported architectures
STklos is known to work on the following architectures:
- Linux 2.2/ 2.4 / 2.6 (i386/gcc)
- Linux 2.4 (itanium/gcc)
- Linux 2.2 (Alpha/egcs)
- FreeBSD 6.2 (i386/gcc)
- Win XP (i386/gcc(Cygwin))
- Mac OS-X (ppc/apple gcc & intel/apple gcc)
- Solaris 8 (ultrasparc/gcc)
- Irix 6.5.20 (Octane, mips R10,000)
- Open Darwin 7.0 (PPC/gcc)
This is clearly not sufficient and port to other architectures should
be done, but any help in this area is really welcome. More
informations on supported platforms is available in the PORTING-NOTES
file in the distribution.
* Linux 1.6.x (i386/gcc 32 and 64bits)
* Mac OS X 10.5+ (i386/gcc 32 and 64 bits)
* FreeBSD 8.x (i386/gcc 32 bits and probably 64 bits)
Previous versions of STklos have run on various architectures. All
these ports are pretty old now, but if a port worked a day on a given
architecture, it should be not too hard to port recent version of
STklos on it. The old ports were effective on:
* Win-NT/Win-XP (i386/gcc(Cygwin))
* Linux >= 2.2 (i386/gcc and alpha/gcc)
* FreeBSD 4.2 (i386/gcc)
* Mac OS X (ppc & Intel/gcc)
* Solaris 8 (ultrasparc/gcc)
* Irix 6.5.20 (Octane, mips R10,000)
* Open Darwin 7.0 (PPC/gcc)
More informations on supported platforms is available in the
PORTING-NOTES file in the distribution.
* Project Home
STklos home page is is located at http://stklos.net
The project is also hosted on Source Forge http://sourceforge.net/projects/stklos.
--
......
-*- outline -*-
THIS IS VERY OBSOLETE AND SHOULD BE REWRITTEN.
* THINGS TO DO (NEXT RELEASES PLAN)
** Version 0.99
- Terminate canvas implementation
- Add new widgets that exist in 0.51 and have not been ported back
- Add GTk2 support
- Add STk Posix support
- autoload (and syntax-autoload) and modules as in STk?
- Use packages in all the library to hide functions which
should not be exported. Use a scheme similar to STk, such as
if a user redefines a standard function, it will not break
the library itself.
- Tree widget
- ...
************************************************************************
* THINGS TO DO (BY CATEGORY)
** STUFF TO PORT FROM STk
- when-port-readable ...
- ...
** COMPILER
- Add goto optimisations
- better handling of undefined symbols when compiling a module.
** MISC
- Use packages in all the library to hide functions which should not be
exported. Use a scheme similar to STk, such as if a user redefines a
standard function, it will not break the library itself.
- Make an interactive help command. Everything is ready for that.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment