boringssl/BUILDING

mkdir build
cd build
cmake ..
make

Note that the default build flags in the top-leve CMakeLists.txt are for
debugging - optimisation isn't enabled.

If you'll be building a lot, then installing Ninja[1] is highly recommended.
Wipe out the build directory and recreate it, but using:

cmake -GNinja ..
ninja

If you want to cross-compile then there are example toolchain files for 32-bit
Intel and ARM in util/. Wipe out the build directory, recreate it and run cmake
like this:

cmake -DCMAKE_TOOLCHAIN_FILE=../util/arm-toolchain.cmake -GNinja ..

If you want to build as a shared library you need to tweak the STATIC tags in
the CMakeLists.txts and also define BORINGSSL_SHARED_LIBRARY and
BORINGSSL_IMPLEMENTATION. On Windows, where functions need to be tagged with
"dllimport" when coming from a shared library, you need just
BORINGSSL_SHARED_LIBRARY defined in the code which #includes the BoringSSL
headers.

[1] http://martine.github.io/ninja/
Inital import. Initial fork from f2d678e6e89b6508147086610e985d4e8416e867 (1.0.2 beta). (This change contains substantial changes from the original and effectively starts a new history.) 2014-06-20 20:00:00 +01:00			`mkdir build`
			`cd build`
			`cmake ..`
			`make`

			`Note that the default build flags in the top-leve CMakeLists.txt are for`
			`debugging - optimisation isn't enabled.`

			`If you'll be building a lot, then installing Ninja[1] is highly recommended.`
			`Wipe out the build directory and recreate it, but using:`

			`cmake -GNinja ..`
			`ninja`

			`If you want to cross-compile then there are example toolchain files for 32-bit`
			`Intel and ARM in util/. Wipe out the build directory, recreate it and run cmake`
			`like this:`

			`cmake -DCMAKE_TOOLCHAIN_FILE=../util/arm-toolchain.cmake -GNinja ..`

Add visibility rules. This change marks public symbols as dynamically exported. This means that it becomes viable to build a shared library of libcrypto and libssl with -fvisibility=hidden. On Windows, one not only needs to mark functions for export in a component, but also for import when using them from a different component. Because of this we have to build with \|BORINGSSL_IMPLEMENTATION\| defined when building the code. Other components, when including our headers, won't have that defined and then the \|OPENSSL_EXPORT\| tag becomes an import tag instead. See the #defines in base.h In the asm code, symbols are now hidden by default and those that need to be exported are wrapped by a C function. In order to support Chromium, a couple of libssl functions were moved to ssl.h from ssl_locl.h: ssl_get_new_session and ssl_update_cache. Change-Id: Ib4b76e2f1983ee066e7806c24721e8626d08a261 Reviewed-on: https://boringssl-review.googlesource.com/1350 Reviewed-by: Adam Langley <agl@google.com> 2014-07-31 00:02:14 +01:00			`If you want to build as a shared library you need to tweak the STATIC tags in`
			`the CMakeLists.txts and also define BORINGSSL_SHARED_LIBRARY and`
			`BORINGSSL_IMPLEMENTATION. On Windows, where functions need to be tagged with`
			`"dllimport" when coming from a shared library, you need just`
			`BORINGSSL_SHARED_LIBRARY defined in the code which #includes the BoringSSL`
			`headers.`

Inital import. Initial fork from f2d678e6e89b6508147086610e985d4e8416e867 (1.0.2 beta). (This change contains substantial changes from the original and effectively starts a new history.) 2014-06-20 20:00:00 +01:00			`[1] http://martine.github.io/ninja/`