ECL 10.4.1
in [Lisp]
|
From: "Antti "Andy" Ylikoski" on 13 May 2010 11:40 4.4.2010 17:46, Juanjo kirjoitti: > Announcement of ECL > =================== > > ECL stands for Embeddable Common-Lisp. The ECL project aims to produce > an > implementation of the Common-Lisp language which complies to the ANSI > X3J13 > definition of the language. > > The term embeddable refers to the fact that ECL includes a lisp to C > compiler, > which produces libraries (static or dynamic) that can be called from C > programs. Furthermore, ECL can produce standalone executables from > your lisp > code and can itself be linked to your programs as a shared library. > > ECL supports the operating systems Linux, FreeBSD, NetBSD, OpenBSD, > Solaris (at > least v. 9), Microsoft Windows and OSX, running on top of the Intel, > Sparc, > Alpha and PowerPC processors. Porting to other architectures should be > rather > easy. > > ECL is currently hosted at Common-Lisp.net and SourceForge. The home > page of > the project is http://ecls.sourceforge.net, and in it you will find > source code > releases, a CVS tree and some useful documentation. > > Known issues > ============ > > - The Mingw port does not work with the stable version of the Boehm- > Weiser > garbage collector. Users will have to download a more recent version > and > build and install it in an accessible location for ECL to compile. > > - The OpenBSD port does not support multithreaded builds because the > latest > stable version that runs on it does not contain all the required > functionality. > > Changes since last release > ========================== > > See file src/CHANGELOG or browse it online > > http://ecls.cvs.sourceforge.net/viewvc/ecls/ecl/src/CHANGELOG?view=markup Could it be possible to have the Windows binaries there in a downloadable form? I can download, unzip and un-tar the source files -- but I cannot build them into a LISP binary. Of course the abovementioned is simply caused by my ignorance -- but anyway the binaries would be very nice to have there at the site. kind regards, Antti Ylikoski Helsinki, Finland, the EU
From: Juanjo on 13 May 2010 13:49 On May 13, 5:40 pm, "Antti \"Andy\" Ylikoski" <antti.yliko...(a)gmail.com> wrote: > Could it be possible to have the Windows binaries there in a > downloadable form? I have so far refrained from producing Windows binaries for several reasons: * Legal/responsibility issues due to binaries. * In particular sensitivity to viruses -- I do not own / pay for a Windows virus scanner. * Lack of a true Windows development platform: all i have are virtual images which may or may not be safe. * The most stable binary is the one that is built using MSVC, but this has license issues of its own. That said, it would be nice if somebody with less scrupuli produced a distributable image. Juanjo
From: D Herring on 13 May 2010 22:20 On 05/13/2010 01:49 PM, Juanjo wrote: > * In particular sensitivity to viruses -- I do not own / pay for a > Windows virus scanner. FWIW, I've used AVG Free for several years. http://free.avg.com/ It seems comparable to the others. - Daniel P.S. One of my first introductions to public domain, open source software was an antivirus floppy for the Atari 1040 ST. The authors saw the obvious conflict of interest in the antivirus industry. Thus they were trying to provide free cures so people didn't have to pay protection money.
From: "Antti "Andy" Ylikoski" on 14 May 2010 14:44 13.5.2010 20:49, Juanjo kirjoitti: > On May 13, 5:40 pm, "Antti \"Andy\" Ylikoski" > <antti.yliko...(a)gmail.com> wrote: >> Could it be possible to have the Windows binaries there in a >> downloadable form? > > I have so far refrained from producing Windows binaries for several > reasons: > > * Legal/responsibility issues due to binaries. > * In particular sensitivity to viruses -- I do not own / pay for a > Windows virus scanner. > * Lack of a true Windows development platform: all i have are virtual > images which may or may not be safe. > * The most stable binary is the one that is built using MSVC, but this > has license issues of its own. > > That said, it would be nice if somebody with less scrupuli produced a > distributable image. > > Juanjo > OK, thank you. Could you perhaps include in the site the instructions how to build the source code into a Windows ECL + SLIME + (possibly) GNU Emacs system? I certainly could build the system for myself with some simple and concise instructions concerning how to do it. regards, Antti Ylikoski Helsinki, Finland, the E.U.
From: Juanjo on 16 May 2010 16:41 On May 14, 8:44 pm, "Antti \"Andy\" Ylikoski" <antti.yliko...(a)gmail.com> wrote: > 13.5.2010 20:49, Juanjo kirjoitti: > > > > > > > On May 13, 5:40 pm, "Antti \"Andy\" Ylikoski" > > <antti.yliko...(a)gmail.com> wrote: > >> Could it be possible to have the Windows binaries there in a > >> downloadable form? > > > I have so far refrained from producing Windows binaries for several > > reasons: > > > * Legal/responsibility issues due to binaries. > > * In particular sensitivity to viruses -- I do not own / pay for a > > Windows virus scanner. > > * Lack of a true Windows development platform: all i have are virtual > > images which may or may not be safe. > > * The most stable binary is the one that is built using MSVC, but this > > has license issues of its own. > > > That said, it would be nice if somebody with less scrupuli produced a > > distributable image. > > > Juanjo > > OK, thank you. > > Could you perhaps include in the site the instructions how to build the > source code into a Windows ECL + SLIME + (possibly) GNU Emacs system? > > I certainly could build the system for myself with some simple and > concise instructions concerning how to do it. Hmm, you mean something simpler than this: http://ecls.sourceforge.net/new-manual/pr01s06.html#preface.msvc ? Since the appearance of Visual Studio 2010 you can use the first set of build steps which would read Instal Microsoft Visual Studio 2010 and unpack ECL Open a Visual Studio terminal session. Change to the msvc directory in the ECL source tree Run nmake to build ECL Run nmake install prefix=d:\Software\ECL where the prefix is the directory where you want to install ECL. The last step "Optionally, if you want to build a self-installing executable, you can install NSIS and run nmake windows-nsi" is probably not working because I have not updated the list of installable files in some time, but it should be easy to fix. As for Slime, well, I am not that familiar with Windows + Emacs. Juanjo
|
Pages: 1 Prev: Google Adsense Account Approval Tricks Next: make-instance without initialize-instance |