Re: status update

Daniel Jour <[email protected]>
Newsgroups gmane.lisp.clisp.devel
Message-ID <CACZHyTOuc-o3_Qv6rgSuqqV_JJzyiF75Lv_miYpk+Q8UTyRsRA@mail.gmail.com>
Ok, here comes the final GSoC status report. Unfortunately, I did not
reach the goal of working (building and passing tests) code on the
major platforms.

I made changes to

 * switch the build system to use the autotools. This is not
   complete. The runtime and memory image get build, as well as the
   clisp "-K dispatcher" executable (all on linux). There's still a
   lot of configuration happening inside the source code (which should
   be done by configure), and not all the required configure tests are
   run (testing for termios, for example). More importantly clisp-link
   is missing support for dynamic module generation and is not yet
   used, thus no acutal linking sets are produced (no base,
   full). Also clisp.h is not yet generated.

 * update the gnulib code used by the runtime. This is halfway done,
   depends mostly on solving the configuration related issues above.

 * update the modules to use up to date gnulib code. This is done for
   rawsock and regexp. They also work with "pre-autotools clisp" and
   also on windows, thus these changes could be used on top of the
   current repo state.

 * update the asdf module. This is done.

 * add a new libmagic module. This is mostly done, but only exports a
   limited subset of the available functions.

 * add new gnulib modules to extend the features of rawsock on windows. I
   had to throw away a lot of code here, the WinAPI is not always
   doing what its documentation claims to do.


To continue the switch to autotools needs to be completed. This means
going through the code, determining what configurations are done
(mostly in lispbibl.d, but also other files and the src/m4 directory)
and add them in as appropriate.


Not reaching the goal of a new release is a big disappointment for me,
but I guess the delay due to my illness was just to much to be able to
complete all the work that needed to be done.


I had a lot of fun working on CLISP, and intend to do so in the
future. Thank you all a lot for your help throughout this summer! :)

(On top of all I'm fighting with an unstable internet connection atm,
I put up the autotools work hopefully in some hours)

------------------------------------------------------------------------------
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.