[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: LuaSec install
- From: Philipp Janda <siffiejoe@...>
- Date: Mon, 18 May 2015 18:18:33 +0200
Am 18.05.2015 um 16:32 schröbte steve donovan:
I see that the Windows package manager Chocolatey has OpenSSL
(Interesting idea - actually not having to download dodgy files or
compile big packages.)
No idea where it puts the resulting libraries and headers, however
Chocolatey is for applications and not for libraries, so it is possible
that there are no header files installed by this package (also the
description says: "Installs the most commonly used essentials of Win32
OpenSSL v1.0.2a (Recommended for users by the creators of OpenSSL)."
However, there is also a full package here, which probably includes
header files and libraries since it is intended for software developers
("Installs Win32 OpenSSL v1.0.2a (Recommended for software developers by
the creators of OpenSSL).").
Both versions apparently use the MSVC 2008 runtime.
For development packages you usually look in the NuGet gallery. There
are multiple versions available, linking to different C runtime
libraries. Header files usually are installed in a
`build/native/include` subdirectory in the downloaded package, similarly
import libraries can be found in subdirectories like
`build/native/lib/Win32/Release` (DLLs are in separate `.dist` packages
with similar directory layouts).
If you use MinGW instead of a MS compiler, I'd recommend the
win-builds package manager, which can install OpenSSL (and a bunch of
other libraries), linked to the old `MSVCRT.DLL`. Include files and
libraries are in Unix-like `include` and `lib` directories.
(I have spent some time evaluating different package managers for use
with LuaRocks on Windows).