nihilist/VeraCrypt
1
0
Fork 0
mirror of https://github.com/veracrypt/VeraCrypt synced 2024-11-27 21:43:29 +01:00
Code Issues Packages Projects Releases Wiki Activity

Readme: remove PKCS#11 headers as requirement since they are included in VeraCrypt source tree.

Browse Source
This commit is contained in:
Mounir IDRASSI 2016-09-20 12:52:58 +02:00
parent 17eeaa43cf
commit 479925f403
No known key found for this signature in database
GPG Key ID: DD0C382D5FCFB8FC
2 changed files with 8 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -48,8 +48,6 @@ Requirements for Building VeraCrypt for Windows:
- Microsoft Windows SDK for Windows 7.1 (configured for Visual C++ 2010) - Microsoft Windows SDK for Windows 7.1 (configured for Visual C++ 2010)
- Microsoft Windows SDK for Windows 8.1 (needed for SHA-256 code signing) - Microsoft Windows SDK for Windows 8.1 (needed for SHA-256 code signing)
- Microsoft Windows Driver Kit 7.1.0 (build 7600.16385.1) - Microsoft Windows Driver Kit 7.1.0 (build 7600.16385.1)
- RSA Security Inc. PKCS #11 Cryptographic Token Interface (Cryptoki) 2.20
header files (available at ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-11/v2-20)
- NASM assembler 2.08 or compatible - NASM assembler 2.08 or compatible
- gzip compressor - gzip compressor
- upx packer (available at http://upx.sourceforge.net/) - upx packer (available at http://upx.sourceforge.net/)
@ -90,17 +88,13 @@ Instructions for Building VeraCrypt for Windows:
directory than '%SYSTEMDRIVE%\WinDDK', create an environment variable directory than '%SYSTEMDRIVE%\WinDDK', create an environment variable
'WINDDK_ROOT' pointing to the DDK installation directory. 'WINDDK_ROOT' pointing to the DDK installation directory.
3) Copy the PKCS #11 header files to a standard include path or create an 3) Open the solution file 'VeraCrypt.sln' in Microsoft Visual Studio 2010.
environment variable 'PKCS11_INC' pointing to the directory where
the PKCS #11 header files are installed.
4) Open the solution file 'VeraCrypt.sln' in Microsoft Visual Studio 2010. 4) Select 'All' as the active solution configuration.
5) Select 'All' as the active solution configuration. 5) Build the solution.
6) Build the solution. 6) If successful, there should be newly built VeraCrypt binaries in the
7) If successful, there should be newly built VeraCrypt binaries in the
'Release' folder. 'Release' folder.
Instructions for Signing and Packaging VeraCrypt for Windows: Instructions for Signing and Packaging VeraCrypt for Windows:
@ -141,10 +135,6 @@ Requirements for Building VeraCrypt for Linux and Mac OS X:
wxWidgets 3.0 library source code (available at http://www.wxwidgets.org) wxWidgets 3.0 library source code (available at http://www.wxwidgets.org)
- FUSE library and header files (available at https://github.com/libfuse/libfuse - FUSE library and header files (available at https://github.com/libfuse/libfuse
and https://osxfuse.github.io/) and https://osxfuse.github.io/)
- RSA Security Inc. PKCS #11 Cryptographic Token Interface (Cryptoki) 2.20
header files (available at ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-11/v2-20).
They are already included in the source tree under the directory PKCS11 but
it is possible to override it using the environment variable 'PKCS11_INC'.
Instructions for Building VeraCrypt for Linux and Mac OS X: Instructions for Building VeraCrypt for Linux and Mac OS X:

18
src/Readme.txt
View File

@ -48,8 +48,6 @@ Requirements for Building VeraCrypt for Windows:
- Microsoft Windows SDK for Windows 7.1 (configured for Visual C++ 2010) - Microsoft Windows SDK for Windows 7.1 (configured for Visual C++ 2010)
- Microsoft Windows SDK for Windows 8.1 (needed for SHA-256 code signing) - Microsoft Windows SDK for Windows 8.1 (needed for SHA-256 code signing)
- Microsoft Windows Driver Kit 7.1.0 (build 7600.16385.1) - Microsoft Windows Driver Kit 7.1.0 (build 7600.16385.1)
- RSA Security Inc. PKCS #11 Cryptographic Token Interface (Cryptoki) 2.20
header files (available at ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-11/v2-20)
- NASM assembler 2.08 or compatible - NASM assembler 2.08 or compatible
- gzip compressor - gzip compressor
- upx packer (available at http://upx.sourceforge.net/) - upx packer (available at http://upx.sourceforge.net/)
@ -90,17 +88,13 @@ Instructions for Building VeraCrypt for Windows:
directory than '%SYSTEMDRIVE%\WinDDK', create an environment variable directory than '%SYSTEMDRIVE%\WinDDK', create an environment variable
'WINDDK_ROOT' pointing to the DDK installation directory. 'WINDDK_ROOT' pointing to the DDK installation directory.
3) Copy the PKCS #11 header files to a standard include path or create an 3) Open the solution file 'VeraCrypt.sln' in Microsoft Visual Studio 2010.
environment variable 'PKCS11_INC' pointing to the directory where
the PKCS #11 header files are installed.
4) Open the solution file 'VeraCrypt.sln' in Microsoft Visual Studio 2010. 4) Select 'All' as the active solution configuration.
5) Select 'All' as the active solution configuration. 5) Build the solution.
6) Build the solution. 6) If successful, there should be newly built VeraCrypt binaries in the
7) If successful, there should be newly built VeraCrypt binaries in the
'Release' folder. 'Release' folder.
Instructions for Signing and Packaging VeraCrypt for Windows: Instructions for Signing and Packaging VeraCrypt for Windows:
@ -141,10 +135,6 @@ Requirements for Building VeraCrypt for Linux and Mac OS X:
wxWidgets 3.0 library source code (available at http://www.wxwidgets.org) wxWidgets 3.0 library source code (available at http://www.wxwidgets.org)
- FUSE library and header files (available at https://github.com/libfuse/libfuse - FUSE library and header files (available at https://github.com/libfuse/libfuse
and https://osxfuse.github.io/) and https://osxfuse.github.io/)
- RSA Security Inc. PKCS #11 Cryptographic Token Interface (Cryptoki) 2.20
header files (available at ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-11/v2-20).
They are already included in the source tree under the directory PKCS11 but
it is possible to override it using the environment variable 'PKCS11_INC'.
Instructions for Building VeraCrypt for Linux and Mac OS X: Instructions for Building VeraCrypt for Linux and Mac OS X: