[CLN-list] Build CLN for 64 bit windows

[Bruno Haible]

Hi Richard,

> I am trying to build CLN for windows 64 bit. ...
> libtool: compile:  x86_64-w64-mingw32.static-g++ -DHAVE_CONFIG_H -I. 
> -I../autoconf -I../include -I../src -I../include -I../src -g -O2 -MT 
> base/cl_as_exception.lo -MD -MP -MF base/.deps/cl_as_exception.Tpo -c 
> base/cl_as_exception.cc -o base/cl_as_exception.o
> libtool: compile:  x86_64-w64-mingw32.static-g++ -DHAVE_CONFIG_H -I. 
> -I../autoconf -I../include -I../src -I../include -I../src -g -O2 -MT 
> base/cl_condition.lo -MD -MP -MF base/.deps/cl_condition.Tpo -c 
> base/cl_condition.cc -o base/cl_condition.o
> In file included from ./base/cl_sysdep.h:10:0,
>                   from base/cl_alloca.cc:4:
> ../include/cln/intparam.h:26:2: error: #error "Type char * does not fit 
> into a long!!"
>   #error "Type char * does not fit into a long!!"

This is now fixed in the git repository.

64-bit mingw is supported, except for one problem: libtool refuses to build
the shared library.

64-bit MSVC is nearly supported. The currently blocking issue is some
problem with cl_asm.S.

> I'm actually doing this by 
> cross-compiling form linux using M Cross Environment (see www.mxe.cc for 
> more information).

The supported build environments are detailed in the file 'INSTALL.windows'.
Cross-compilation is not supported, but you may succeed in getting it to
work with little effort, given that there are only few AC_TRY_RUN invocations
in the configure script. You do so by presetting some of the cl_cv_* variables
in the environment before launching the configure script.

> I noticed in a thread from eight years ago that this same problem 
> existed back then:

Yeah, we (Richy, Alexey, me) were not very active on this front for
several years. Your mail finally has prompted me to work on this.

> Is it a huge amount of work to fix this?

It was about 2 days of work.

Bruno