Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Windows documentation #527

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update Windows documentation #527

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 13 additions & 6 deletions WindowsPort.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,18 +1,25 @@


Compiling PicoTLS with Visual Studio 2017

The source contains a Visual Studio 2017 solution (picotls/picotlsvs/picotlsvs.sln)
which itself contains 5 projects:
which itself contains 10 projects, including:

* Three libraries, picotls.lib and its dependencies cifra.lib and uecc.lib;
* picotls-core, building the core library
* picotls-openssl, the library for the open-ssl backend
* picotls-minicrypto, the library for the minicrypto backend
* picotls-minicrypto-deps, the dependencies for the minicrypto backend
* picotls-bcrypt, implementation of some crypto functions using Windows' bcrypt library
* picotls-fusion, for the AES fusion code

* A test project, testopenssl.exe, which will run on a console and
execute the OpenSSL tests;

* And, an example project, picotlsvs.exe, which will perform a TLS exchange
in memory, and demonstrate how to use PicoTLS in windows.

The code has a dependency on OpenSSL. When building the 32 bit projects (WIN32) it
expects to find:
The example code has a dependency on OpenSSL. When building the 32 bit
projects (WIN32) it expects to find:

* OpenSSL header files under $(OPENSSLDIR)\include

Expand All @@ -28,7 +35,7 @@ You will need also to copy libcrypto.dll to the library that contains your
executable, or to otherwise register that library. Be sure to copy the 32 bit
library or 64 bit library, depending on which type of project you build.

Only two configurations are tested: "X86 Debug" and "X86 Release". The X64 configurations
will compile, but are not tested yet.
The integration tests with Appveyor check four configurarions: "X86 Debug",
"X86 Release", "X64 Debug" and "X64 Release".

Feel free to provide feedback and contribute.
Loading