about summary refs log tree commit diff homepage
path: root/scripts/build/patches
AgeCommit message (Collapse)Author
2022-03-17remove LLVM < 6 from build/test scriptsFrank Busse
2020-09-30Fix LLVM 4.0 build patchMartin Nowack
2020-02-13Add patch support for libcxxMartin Nowack
Building older LLVM/libcxx versions under Ubuntu 18.04 requirer patches
2020-02-13Use git repository to build LLVMMartin Nowack
LLVM changed from svn to github. Use the github mirror to have faster build times. Patches were updated to follow the new structure. Patches also support building underr Ubuntu 18.04
2019-09-05build: additional patches for LLVM 3.8-5.0Julian Büning
2019-03-21drop support for LLVM <= 3.7Julian Büning
2019-03-10Updated dependency build system for KLEEMartin Nowack
Provide a single `scripts/build/build.sh` file to build KLEE and its dependencies.
2018-09-06llvm36.patch: fix build for newer glibc/gcc versionsFrank Busse
2018-07-04Extensive updates to the build script for dependencies and dockerMartin Nowack
Building/managing dependencies of KLEE are not easy. This script should change this. Features: * script install different versions in their specific directories This allows: - to have different versions in parallel installed: llvm, solvers - to have different optimization levels installed (Debug, no-debug, assertions, optimized) - to have different versions of instrumentation enabled (address, memory, leakage, undefined behavior) * the script is kept distribution agnostic: assuming basic packages are installed (a compiler), use `scripts/build/ubuntu-dependencies.sh` to install ubuntu specific ones * the script does not install any file into system directories (sudo is not required) files are only installed into a user specified BASE directory The same scripts are used for either local setup (`scripts/build/local_install.sh`) or create a docker image based of your current source folder (`scripts/build/build_docker.sh`) Change the defaults permanently by modifying (`scripts/build/common-defaults.sh`) or change them on the fly by providing them as environment variables on the command line. The same scripts are also used for TravisCI, so we test what we are using.