blob: 01f727422ae0f67ec74c4467675c836b9f55b633 [file] [log] [blame]
Paul Bakker7cea7622009-07-11 19:48:38 +00001README for PolarSSL
2
3-- COMPILING
4There are currently three active build systems within the PolarSSL releases:
5 - Make
6 - CMake
7 - Microsoft Visual Studio
8
9The 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.
10
11--- Make
12In order to build the source using Make, just enter at the command line:
13make
14
15--- CMake
16In order to build the source using CMake, just enter at the command line:
17cmake .
18make
19
20There are 3 different active build modes specified within the CMake buildsystem:
21 - Release
22 This generates the default code without any unnecessary information in the binary files.
23 - Debug
24 This generates debug information and disables optimization of the code.
25 - Coverage
26 This generates code coverage information in addition to debug information.
27
28Switching build modes in CMake is simple. For debug mode, enter at the command line:
29cmake -D CMAKE_BUILD_TYPE:String="Debug" .
30
31--- Microsoft Visual Studio
32The 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.
33
34The 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.