On 2022-05-18, JJ <
jj4p...@gmx.com> wrote:
> On Mon, 16 May 2022 23:49:29 GMT, Charlie Gibbs wrote:
<snip>
>> I've installed MinGW and have successfully compiled and run small
>> test programs, both console and GUI. So far, though, I've not
>> succeeded in getting my suite to compile (although a few of the
>> simplest programs, both console and GUI, do compile and run).
>> The program I'm currently trying to compile is a console program
>> which comes up with the following messages:
<snip>
> You're missing the Windows' DLL import libraries which are available from
> Windows SDK. But I don't know if the LIB files from it, are usable by MingW,
> cause its a *nix origin. If not, you'll need to manually create the import
> library files from the DLLs. FYI, Borland C++ Builder works out of the box,
> because it already include most of the import libraries.
That sounds kind of familiar. I did once manage to build OpenSSL 1.0.1g
with the Borland compiler. I used Borland's implib utility to convert
the OpenSSL DLLs to library files that the Borland linker could use.
(I prefer to link statically.) What puzzles me in this case, though,
is that the error messages I mentioned in my original post disapper
if I include the -mwindows parameter; this suggests that the library
must be there, although -mwindows has other undesirable effects.
I can't find any documentation of the various -l parameters - the
one I did see mentioned, -lws2_32, brings in the socket libraries,
but that isn't too intuitive.
--
/~\ Charlie Gibbs | Microsoft is a dictatorship.
\ / <cgi...@kltpzyxm.invalid> | Apple is a cult.
X I'm really at ac.dekanfrus | Linux is anarchy.
/ \ if you read it the right way. | Pick your poison.