... | @@ -5,11 +5,13 @@ in different ways if you are compiling the unit tests or you are compiling exter |
... | @@ -5,11 +5,13 @@ in different ways if you are compiling the unit tests or you are compiling exter |
|
|
|
|
|
### External code
|
|
### External code
|
|
|
|
|
|
* defining the macro SE_CLASS1 before include any openfpm headers enable security enhancements of class1
|
|
* defining the macro SE_CLASS1 before include any openfpm headers enable security enhancements of class1,
|
|
* define the macro SE_CLASS2 before include any openfpm headers enable security enhancements of class2
|
|
* define the macro SE_CLASS2 before include any openfpm headers enable security enhancements of class2
|
|
* define the macro SE_CLASS3 before include any openfpm headers enable security enhancements of class3
|
|
* define the macro SE_CLASS3 before include any openfpm headers enable security enhancements of class3
|
|
* define the macro
|
|
* define the macro
|
|
|
|
|
|
|
|
for more information visit [here](http://ppmcore.mpi-cbg.de:4567/security-enhancements)
|
|
|
|
|
|
### Unit test
|
|
### Unit test
|
|
|
|
|
|
OpenFPM is in general is only header library with few exceptions, to compile the unit tests there are 4 that can be considered the most important options, in the install script these option are passed with -c "--enable-se-class1 --enable-se-class2 --enable-se-class3 --enable-debug"
|
|
OpenFPM is in general is only header library with few exceptions, to compile the unit tests there are 4 that can be considered the most important options, in the install script these option are passed with -c "--enable-se-class1 --enable-se-class2 --enable-se-class3 --enable-debug"
|
... | | ... | |