On 11/25/20, Garrett Dangerfield wrote:
> I got the 20.4.24 tarball and actually managed to compile it on Windows 10
> using cygwin gcc.
Here is my experience with (latest) ECL on Windows 10:
I installed the (free) MSVC compiler (which is the natural choice on
Windows, has fewer dependencies and
You don't call configure on msvc build, check out install file and the manual
Wysłano z aplikacji ProtonMail
Oryginalna wiadomość
26 lis 2020, 17:58, Garrett Dangerfield napisał(a):
> So if I use Visual Studio, will I still use cygwin to do the ./configure?
>
> On Thu, Nov 26
‐‐‐ Original Message ‐‐‐
On Thursday, 26 November 2020 17:51, Garrett Dangerfield
wrote:
> I tried your suggestions and I tried the cygwin patch as well, no luck,
> that's why I tried to pull cygwin out of the equation. Neither seem to be
> producing an EXE that could understand an ext
ECL may be build with cygwin/mingw, then it works with cygwin/mingw runtime.
You may also use
MSVC, then you need to enter the msvc directory and issue nmake (see
documentation for more
precise instructions).
That said, did you try my previous suggestion with passing appropriate flags to
cygwin
Dear Garrett,
the error you get is due to ECL not finding its compiler binary (the
compiler is build as a separate fasl which is loaded on demand). Can you
check whether the file obtained from (translate-logical-pathname
#P"SYS:CMP.NEWEST") exists? What value is the variable
c::*ecl-library-direct
Cygwin allows you to compile linux programs on windows systems by providing the
full set of Linux functions your application might expect to see. It even
converts filenames into a format Linux applications are used to and therefore
uses "/cygdrive/c" instead of "C:\" in pathnames.
Any "real" win