Re: Compilation on Windows 8 with Visual Studio 2013

[<Joe...@t-...>]

Hi,

Loïc Maury wrote:
> however I'am blocked at CLisp/src when I do nmake (after copied
> win32msvc to src\makefile, and follow steps).

> cl @CPPFLAGS@ -I/gllib  -G5 -Os -Oy -Ob1 -Gs -Gf -Gy -U__GNUC__ -DANSI 
> -D_M_IX86=500 -D_WIN32 -I"C:\\Program Files (x86)\\Microsoft Visual 
> Studio 12.0\\VC"/include -DENABLE_UNICODE @INCTERMCAP@ -DDYNAMIC_FFI -DNO_GETTEXT
> -I.   ..\utils\comment5.c /Fecomment5.exe
Sam>PPS. You might want to consider mingw instead.

Isn't there an ancient Makefile.MSVC5 or MSVC6 in the repository? Maybe that's
a useful base for the base clisp (pun intended).

Rationale: I used it -- over a decade ago -- to build CLISP with MSVC98 (yeah).

However, I can't remember the details, I guess I cheated a little bit and ran
configure first from a Linux machine, with the MS-Windows HD exported over
Samba, so as to generate the basic files like comment5.c, config.h, eval.c
etc.  Then I returned to the MS-Windows machine and had MSVC compile and link
the .c files.  Well, given comment5.exe, ansidecl.exe etc., perhaps MSVC was
able to generate eval.c from eval.d on its own after all.  I definitely
never installed MingW or cygwin on the MS-Windows machine.

Note that I only ever built the base lisp.exe -- without any modules except
the dynamic FFI. These days, I believe the build system creates a separate
executable named clisp.exe that dispatches to the various subdirectories in
which the varying lisp.exe were built including whatever modules (among those
that need C code) were additionally compiled (witness the difference between
the base and the full linking set). The grunge work that the scripts in the
current repository do may be limited to support for MingW or cygwin or UNIX,
I don't know.

Regards,
	Jörg.