|Subject:||Re: Prolog: GNU: Command line compiling seems not possible out of the box|
|Date:||Mon, 27 Mar 2023 14:28:52 +0200|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0|
Command-line compilation under windows requires additional tools.
You'll find more information int the file src/WINDOWS in the
source distribution (also here:
provides information about compiling gprolog itself on Windows
(maybe some steps can be avoided to only compile a end-user Prolog
a. Operating system: Microsoft Windows 10 Professional:
b. Clean installation.
c. Given and using only this example file, save as 'helloworld.pro'.
write( 'Hello world' ), nl,halt.
d. It looks like information is missing when trying to compile this GNU Prolog file to an executable .exe.
e. I tried also with the MINGW versionsWindows intel 64 bits auto-install setup (compiled under x86_64 / Windows 10 with MinGW64 gcc under MSys2).but they gave tons of 'reference not found errors' , e.g. when including the gcc.exe path.
f. First tried with the latest 64 bits version from
But that seems to combine Microsoft Visual Studio and MINGW compilation, because getting errors about e.g. 'as.exe' which
is clearly MINGW related and has nothing to do with Microsoft Visual Studio.I saw those errors referring to gcc.exe (thus MINGW) when trying to compile
g. Then I did fall back on the 32 bits version (after uninstalling the 64 bits version)Windows intel 32 bits auto-install setup (compiled under ix86 / Windows 10 with MSVC++).
I got a load of '.lib' files not found (e.g. advapi32.lib, ...) errors, it kept continuing missing different .lib files.At the end I copied some 500 different x86 .lib files into the bin directory of GNU Prolog 32 bits.
Then finally when compiling
it created successfully a file
which when run did show 'Hello world'.
with friendly greetingsKnud van Eeden
|[Prev in Thread]||Current Thread||[Next in Thread]|