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

[Ury M. <ur...@tw...>]

Sam Steingold wrote:

> please try to add
>
>MSVCDIR = "C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7"
>to Makefile.
>
>  
>
With the double quotes around it works.

>>2) same makefile.msvc7, line 1237, the command sed -e '/^#line/....
>>my sed (coming from http://gnuwin32.sourceforge.net/) chokes
>>on the single quotes. Shouldn't they be replaced by double quotes?
>>    
>>
>
>does it work if you do?
>how about
>'/^#line/{n' -e 'ta' -e ':a' -e 's/^%% //' -e 'tb' -e 's/^.*\$\$//' -e ':b' -e '}'
>(suggested by Pascal).
>
>  
>
The new line (suggested by Pascal) does not work for me, says:
syntax error : illegal character '\' in macro

Changing single quotes to double seems to work, although there is one more
place to do the change at line 988 (for some reason it was giving an 
error here, but continuing
the build process). This fix (on line 988) also seems to fix the 
varobject_alignment
problem

After that the make dies with:
        ..\utils\gcc-cccp\cccp -U__GNUC__ -+ -D_M_IX86=500 -D_WIN32 
-I"C:\Progra
m Files\Microsoft Visual Studio .NET 2003\Vc7"/include -D_MSC_VER=1300 
-D_INTEGR
AL_MAX_BITS=64 -I"C:\Program Files\Microsoft Visual Studio .NET 
2003\Vc7"/Platfo
rmSDK/include  -DUNICODE -DDYNAMIC_FFI -DNO_GETTEXT -DNO_SIGSEGV -I. 
encoding.c
 > encoding.i.c
libcharset.h:22: localcharset.h: No such file or directory
NMAKE : fatal error U1077: '..\utils\gcc-cccp\cccp' : return code '0x21'
Stop.

for a quick fix I've added the \libcharset\include directory in the 
makefile, which allowed it to
continue successfully.
But now that it's built, what's next - there's no "make install" or 
something along these lines?

>note that installing cygwin and building clisp with
>$ ./configure --with-mingw --build build-dir
>is much easier than messing with ms tools
>and it produces a native woe32 binary which does not rely on cygwin.
>
>  
>

I tried mingw with msys and it worked, seems to be much easier than MSVC 
build. It
probably should be (at least) mentioned in win32msvc/INSTALL file as an
alternative solution.
BTW, same problem with it - after it's built, how do I install it 
somewhere, keeping
only the runtime files?

Thank you,
Ury