Stream: social
Topic: OpenSSL
Grahame Grieve (Dec 10 2021 at 10:42):
I don't know if anyone wants to help me out here... I'd like to compile openSSL stable branch OpenSSL_1_1_1-stable. It's trivially easy on linux and osx, but bafflingly hard on windows. Is there a c guru who'd like to reduce it down to 'run this batch file', if that's even possible. I'd really like win32 and win64 outputs (I want the .a files the compile produces)
Vassil Peytchev (Dec 10 2021 at 14:35):
compile with what? Microsoft VC++? gcc? I assume you have seen this?
Grahame Grieve (Dec 10 2021 at 21:01):
I have indeed read that several times. It refers to things I don't have and don't know how to have (e.g. "Visual Studio tool x64 Cross Tools Command prompt") because maybe they've been renamed, but then things don't work, and I don't know why, and is it because I have the wrong tool? or the wrong path? These things come with multiple copies of everything...
Grahame Grieve (Dec 10 2021 at 21:05):
I'd rather compile with an open source compiler, but I don't feel strongly about that.
Gino Canessa (Dec 10 2021 at 21:19):
I vaguely recall that I could get it to build, but clearly remember that it was enough of a hassle that I ended up using someone else's binaries*.
I'd recommend pre-builts from https://wiki.openssl.org/index.php/Binaries based on the chain you need.
*edit: many years ago
Grahame Grieve (Dec 10 2021 at 21:24):
I've been doing this with the dlls for many years, but now I want the .a files, and these (rightly) don't get distributed
Vassil Peytchev (Dec 10 2021 at 22:33):
AFAIK gcc can create .a files (essentially static libraries to be linked into an executable), but is that what you need? I thought .a output from gcc is useful only in a Unix-based environment. Are Windows static libraries different?
Grahame Grieve (Dec 10 2021 at 22:43):
there isn't 'a windows static library' - it's compiler specific. The compiler I'm using is based on the gcc toolchain. I know that some compilers don't produce gcc compatible artifacts. I don't know about microsofts VSC
Vassil Peytchev (Dec 10 2021 at 23:14):
Is the gcc-based toolchain that you are using in Windows based on MinGW or on Cygwin?
Grahame Grieve (Dec 10 2021 at 23:14):
I'm not sure. it's free pascal, so native
Vassil Peytchev (Dec 10 2021 at 23:40):
Sounds like free pascal is using the MinGW flavor on gcc - have you tried just providing the Linux .a files to FPC?
Grahame Grieve (Dec 11 2021 at 01:38):
no I haven't, not for windows
Vassil Peytchev (Dec 11 2021 at 05:18):
I found this: https://gist.github.com/udnaan/80c5ad125fc4702309b9 on how to use mingw-w64 on Linux to produce windows binaries.
Adding no-shared to the configuration command produces .a files. Link to the result in PM
Last updated: Apr 12 2022 at 19:14 UTC
