Menu
▾
▴
clisp-devel
|
From: Jack U. <jd...@gm...> - 2007-11-07 03:37:09
|
On Nov 6, 2007 5:24 PM, Elliott Slaughter <ell...@gm...> wrote: > On Nov 6, 2007 3:56 PM, Sam Steingold <sd...@gn...> wrote: > > so what's missing is the src/makemake.in patch that would create > > the installer. > > Not at all sure how to do that... If no one beats me to it, I will have some time in the next couple of days to work on such a patch -- and also a patch for win32msvc/INSTALL that describes how to get NSIS, what makefile target to run, etc. -- Jack Unrue |
|
From: Sam S. <sd...@gn...> - 2007-11-07 17:25:25
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Elliott Slaughter wrote: > And we still need to upload the > install files to the CVS, unless you did it without telling me. (BTW, look at clisp/win32msvc/nsis/ > did you give me write access to the installer subdirectory of the CVS > repo?) I am waiting for the e-mail confirmation from the SF account. Sam. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHMfK9Pp1Qsf2qnMcRAsqWAJ9FGpb8UahmYrtX181a3KxsKWzynQCfcsFO bozTk3PekvXIanKdxUOa7h0= =fMBt -----END PGP SIGNATURE----- |
|
From: Elliott S. <ell...@gm...> - 2007-11-08 06:55:13
|
On Nov 7, 2007 9:15 AM, Sam Steingold <sd...@gn...> wrote: > look at clisp/win32msvc/nsis/ Is the script going to be called directly from this location (clisp/win32msvc/nsis/) when called from makemake.in or whatever? Where will the clisp binary distro be when it is run? (clisp/ ?) I just want to make sure the install script will grab the right files when it is run. -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert |
|
From: Sam S. <sd...@gn...> - 2007-11-08 14:55:30
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Elliott Slaughter wrote: > On Nov 7, 2007 9:15 AM, Sam Steingold <sd...@gn...> wrote: >> look at clisp/win32msvc/nsis/ > > Is the script going to be called directly from this location > (clisp/win32msvc/nsis/) when called from makemake.in or whatever? > Where will the clisp binary distro be when it is run? (clisp/ ?) clisp is built in a "build directory" which is "src" for for msvc and anything at all for normal build systems. e.g., I usually use "build-...." in parallel to src (where "...." stands for configure options, e.g., build-g-gxx-dynmod), while the debian (?) people use /tmp/clisp-build/ (or something) the binary distribution resides in the build directory and is called clisp-<ver>-win32.zip the scripts will be copied to the build directory by makemake. the bottom line is that you can assume that the scripts and the binary distribution are in the same directory. Sam. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHMyNVPp1Qsf2qnMcRAkF6AJ9QUg6V6n3NgXHtRAbU75E80+X5TgCfY5+s uJLuQGFkqeXWsw/ZGTCvMsg= =vD2X -----END PGP SIGNATURE----- |
|
From: Elliott S. <ell...@gm...> - 2007-11-08 18:55:08
|
On Nov 8, 2007 6:55 AM, Sam Steingold <sd...@gn...> wrote: > the bottom line is that you can assume that the scripts and the binary > distribution are in the same directory. Ok. On Nov 6, 2007 3:56 PM, Sam Steingold <sd...@gn...> wrote: > we need to find a way to generate this rtf automatically. > this file is far to important for us to risk having two copies diverge... Got around to writing a ruby script to convert the COPYRIGHT file to the rtf file necessary for the installer. Now that I have a working version, should I convert the script to Lisp? (I'm not sure what languages we can expect the builder to have installed.) The script uses regex's, so whatever I use for the final version needs to regex support. -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert |
|
From: Sam S. <sd...@gn...> - 2007-11-08 20:11:32
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Elliott Slaughter wrote: > On Nov 6, 2007 3:56 PM, Sam Steingold <sd...@gn...> wrote: >> we need to find a way to generate this rtf automatically. >> this file is far to important for us to risk having two copies diverge... > > Got around to writing a ruby script to convert the COPYRIGHT file to > the rtf file necessary for the installer. Now that I have a working > version, should I convert the script to Lisp? (I'm not sure what > languages we can expect the builder to have installed.) The script > uses regex's, so whatever I use for the final version needs to regex > support. yes, please use lisp. also, install.nsi hard-codes strings like "GNU CLISP" and "2.42" which is no good (especially the latter). these strings are available to makemake.in from the top-level version.sh and, generally, from the configure substitution. thus makemake should substitute @VER@ and @NAME@ in install.nsi when copying it to the build directory (using sed or lisp). Sam. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHM21oPp1Qsf2qnMcRAi7MAJ0WzOnHCrIKYifVi+dxGqKZW3Mg+ACgl7/e nKvETsvctQljDJqyAI1xmMc= =MPsd -----END PGP SIGNATURE----- |
|
From: Bruno H. <br...@cl...> - 2007-11-07 02:10:36
|
> > Do I get to add a line with my to the copyright > > notice/license in the installer? Elsewhere? You are of course free, and welcome, to mention your name in the installer, since the installer is your work. Regarding the COPYRIGHT file, it is dedicated to new ports that were a lot of effort (and where the contributions made clisp available out of nothing) or to truly major contributions (such as PCL, which was a major add-on to clisp, before clisp had its own CLOS). Note that the port to Windows is not even mentioned there - because it took "only" 1 or 2 month of work. Bruno |
|
From: Hoehle, Joerg-C. <Joe...@t-...> - 2007-11-09 17:41:06
|
Elliot Slaughter wrote: > Now that I have a working >version, should I convert the [Installer] script to Lisp? Please go ahead. I think it's reasonable to expect that somebody writing "make installer" has a working clisp (or that "make" will build one). That clisp should have the I18N and CHARSET packages, to help convert the UTF-8 COPYRIGHT to ISO-8859-1 (or CP1252?). Maybe also the regex or pcre modules. I.e. a developer creating a windows distribution of clisp supposedly has a working clisp, ready to help in generating files, but not necessarily Ruby, or Python, or Arc, or J.=20 Regards, Jorg Hohle |
|
From: Elliott S. <ell...@gm...> - 2007-11-09 18:39:40
|
On Nov 9, 2007 8:03 AM, Hoehle, Joerg-Cyril <Joe...@t-...> wrote: > Elliot Slaughter wrote: > > Now that I have a working > >version, should I convert the [Installer] script to Lisp? > Please go ahead. > I think it's reasonable to expect that somebody writing "make installer" > has a working clisp (or that "make" will build one). That clisp should > have the I18N and CHARSET packages, to help convert the UTF-8 COPYRIGHT > to ISO-8859-1 (or CP1252?). Maybe also the regex or pcre modules. My script uses the regex module so anyone who tries to build the installer will need regex. Also, I don't think I have any problems with unicode now since I convert the file to rtf format anyways. > I.e. a developer creating a windows distribution of clisp supposedly has > a working clisp, ready to help in generating files, but not necessarily > Ruby, or Python, or Arc, or J. I didn't realize that Arc was available at all. I know that there are applications using it but I as far as I know it is still closed source. Or at least that is what it says on Paul Graham's web page. -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X