Go to file
Paul Bakker e2f5040876 Internally split up x509parse_key()
Split up x509parse_key() into a (PEM) handler function and specific
DER parser functions for the PKCS#1 (x509parse_key_pkcs1_der()) and
unencrypted PKCS#8 (x509parse_key_pkcs8_unencrypted_der()) private
key formats.
(cherry picked from commit 65a1909dc6ff7b93f0a231a5a49d98d968c9bcdc)

Conflicts:
	library/x509parse.c
2013-06-25 15:06:50 +02:00
doxygen Prepared for PolarSSL 1.2.6 release 2013-03-11 11:38:44 +01:00
include ssl_parse_certificate() now calls x509parse_crt_der() directly 2013-06-24 19:09:25 +02:00
library Internally split up x509parse_key() 2013-06-25 15:06:50 +02:00
programs Fixed const correctness issues in programs and tests 2013-06-24 19:09:24 +02:00
scripts Added error.h inclusion in error.c template 2013-06-24 19:09:25 +02:00
tests Internally split up x509parse_key() 2013-06-25 15:06:50 +02:00
visualc - Added gcm.c and ssl_cache.c 2012-10-01 20:57:09 +00:00
.gitignore Added proper gitignores for Linux CMake use 2012-11-18 22:56:39 +01:00
ChangeLog PolarSSL 1.2.6 and PolarSSL 1.2.7 changes added to ChangeLog 2013-06-24 19:09:24 +02:00
CMakeLists.txt - Changed default compiler flags to include -O2 2012-10-23 12:12:53 +00:00
DartConfiguration.tcl - Added basic Dart config file 2009-07-08 19:48:13 +00:00
LICENSE - Changed line endings and encodings to unix and utf-8 2011-01-05 14:48:42 +00:00
Makefile - Added uninstall target 2012-11-13 10:28:43 +00:00
README - Fixed texts 2009-10-04 15:15:34 +00:00

README for PolarSSL

-- COMPILING
There are currently three active build systems within the PolarSSL releases:
 - Make
 - CMake
 - Microsoft Visual Studio

The main system used for development is CMake. That system is always the most up-to-date. The others should reflect all changes present in the CMake build system, but some features are not ported there by default.

--- Make
In order to build the source using Make, just enter at the command line:
make

In order to run the tests, enter:
make check

--- CMake
In order to build the source using CMake, just enter at the command line:
cmake .
make

There are 3 different active build modes specified within the CMake buildsystem:
 - Release
   This generates the default code without any unnecessary information in the binary files.
 - Debug
   This generates debug information and disables optimization of the code.
 - Coverage
   This generates code coverage information in addition to debug information.

Switching build modes in CMake is simple. For debug mode, enter at the command line:
cmake -D CMAKE_BUILD_TYPE:String="Debug" .

In order to run the tests, enter:
make test

--- Microsoft Visual Studio
The build files for Microsoft Visual Studio are generated for Visual Studio 6.0 all future Visual Studio's should be able to open and use this older version of the build files.

The workspace 'polarssl.dsw' contains all the basic projects needed to build the library and all the programs. The files in tests are not generated and compiled, as these need a perl environment as well.