[clisp-list] Re: Troubles compiling on win32/msvc7

[Hoehle, Joerg-C. <Joe...@t-...>]

Sam Steingold wrote:
>> * Ury Marshak <helz@gjb-olgrf.pbz> [2005-07-12 20:02:12 +0200]:
>> But now that it's built, what's next - there's no "make install" or
>> something along these lines?
>"make distrib" on cygwin and unzip the distribution,
>or just copy "lisp.exe" and "lispinit.mem" somewhere.

Is that all? (it's all I typically use ;), but I always thought a proper distribution would include the files data/unicodexyz.txt and some others, so that the -B and -N options would make sense?


BTW, for MS-VC, I did the missing parts by hand. IIRC, it's all sed commands and luckily only a few files (stdint.h, stdbool.h etc.), and I used Emacs to do the search/replace (lispbibl.d is also easily handled).
"touch cflags.h.stamp" and built.obj is annoying because it needs to be done more than once.

The most annoying thing is that building inside the src dir corrupts it, so that subsequent Linux configure/build mysteriously fail (as I reported long ago). And I haven't yet experience with union-fs and the like, with which the MS build could be kept separate from the clean src directory. Any recommendations? I didn't find a Debian package for union-fs!?!

Regards,
	Jorg Hohle.