Repository navigation
Requirements
- http://www.cmake.org/cmake/resources/software.html
- For iOS build download and install patched cmake version
This environment variable will point to working directory of hunter package manager. This is where all
downloaded archives and installed libraries will reside. It's recommended to use environment variable, but
also see alternatives.
For UNIX-family (Linux, Mac, Cygwin) users it propably
will be export HUNTER_ROOT=/path/to/hunter/root in .bashrc file, for Windows users:
Control Panel -> System -> Advanced System Settings -> Environment Variables. Do not forget to restart
all terminals/CMake-GUIs to apply changes in both cases. Note that all libraries will be installed in
two variants: Debug and Release. Check that there are enough disk space available (directory can
easily exceed 1 GB).
For example windows (VS 64/32 + cygwin):
- HUNTER_ROOT (> 5 GB)
- HUNTER_ROOT/Downloads (~ 100 MB)
- HUNTER_ROOT/Base/Build (~ 1 GB)
- HUNTER_ROOT/Base/Source/Boost (> 2 GB) # boost builds in-source
- HUNTER_ROOT/Base/Install (> 1 GB)
Projects that uses different toolchains can be build in one HUNTER_ROOT directory if each toolchain
define HUNTER_INSTALL_TAG variable.
For example if clang_libstdcxx
and gcc toolchain used:
- HUNTER_ROOT/Base/Install/clang_libstdcxx
- HUNTER_ROOT/Base/Install/gcc
For each build *_Dir variables will be modified so standard find_package command will pick appropriate
include directories and libraries:
find_package(Boost REQUIRED ...)
include_directories(${Boost_INCLUDE_DIR})
# HUNTER_ROOT/Base/Install/clang_libstdcxx/include for clang_libstdcxx toolchain
# HUNTER_ROOT/Base/Install/gcc/include for gcc toolchain
target_link_libraries(... PUBLIC ${Boost_LIBRARIES})
# HUNTER_ROOT/Base/Install/clang_libstdcxx/lib/libboost_... for clang_libstdcxx toolchain
# HUNTER_ROOT/Base/Install/gcc/lib/libboost_... for gcc toolchain- Download archive, unpack it and set
POLLY_ROOTenvironment variable. Unix-style:
> POLLY_VERSION="0.4.4"
> wget "https://github.com/ruslo/polly/archive/v${POLLY_VERSION}.tar.gz"
> tar xf "v${POLLY_VERSION}.tar.gz"
> export POLLY_ROOT="`pwd`/polly-${POLLY_VERSION}"
> export PATH="${POLLY_ROOT}/bin:${PATH}" # If you want to use build.py script
Now toolchains can be used:
> cmake -H. -B_builds -DCMAKE_TOOLCHAIN_FILE=${POLLY_ROOT}/sanitize_address.cmake
...
-- [polly] Used toolchain: Clang address sanitizer / c++11 support
...
> cmake --build _builds
...
clang++ -std=c++11 -fsanitize=address ...
...
Or using build.py script (generate and build, see build.py --help for all options):
> build.py --toolchain sanitize_address --verbose
...
-- [polly] Used toolchain: Clang address sanitizer / c++11 support
...
clang++ -std=c++11 -fsanitize=address ...
...
Feel free to open new issue if you want to ask any questions.
- HOME
- Packages
- Android-Apk
- Android-Modules
- Android-SDK
- ArrayFire
- Assimp
- Async++
- Avahi
- BZip2
- Boost
- Boost.compute
- Boost.process
- CLAPACK
- Comet
- CppNetlib.URI
- CsvParserCPlusPlus
- Eigen
- Expat
- GPUImage
- GSL
- GTest
- GMock
- Igloo
- IntSizeof
- Jpeg
- JsonSpirit
- LLVM (Clang)
- Leathers
- Libssh2
- Lua
- MySQL-client
- nlohmann::json
- OpenCV
- OpenSSL
- PNG
- Poco C++
- PostgreSQL
- Protobuf
- Qt
- Qt-Android-CMake
- QtQmlManager
- RapidJSON
- Sugar
- TIFF
- Washer
- WTL
- ZeroMQ
- ZMQPP
- ZLIB
- rabbitmq-c
- sparsehash
- ccv
- cereal
- convertutf
- crashpad
- cvmatio
- dest
- dlib
- eos
- flatbuffers
- fmt
- freetype
- glm
- glog
- half
- hdf5
- ios_sim
- irrXML
- libyuv
- log4cplus
- minizip
- odb-pgsql
- odb-mysql
- ogles_gpgpu
- openddlparser
- poly2tri
- polyclipping
- spdlog
- szip
- thread-pool-cpp
- tinydir
- websocketpp
- msgpack
- wxWidgets
- xgboost
Don't see packages you need? Feel free to leave a package request.