Fix build to allow custom boost, llvm and phasar directories.#80
Merged
pdschubert merged 1 commit intosecure-software-engineering:masterfrom Feb 3, 2020
Merged
Conversation
The build was assuming that boost was installed to the default system location and accessible, however for using this as a library I want to use a custom installed boost to match the version of boost used by the application. Most of the changes to CMakeLists are to use find_package to locate the desired boost libraries. I believe this is the preferred way to include boost libraries. Also, this changed to allow llvm to be installed to a specified directory. This change allows the developer to work with multiple different versions for different projects. The bootstrap.sh changes include: - This also includes a change to specify the exact directory for phasar to be installed to. This allows the developer to have multiple installations. - The git submodule init / update was required for a fresh install. I'm guessing this was just accidentally commented out. - Removed the package libmysqlcppconn-dev which isn't necessary to copmile. Perhaps there's another dependency somewhere else, but I specifically removed this because it also pulls in a bunch of other dependencies (notably boost, and I specifically do not want the maintaner's version of boost installed). - Added ability to specify the boost install dir to use. - Added ability to run unit tests (I haven't verified this functionality, but it did work prior to the big merge last week).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The build was assuming that boost was installed to the default system
location and accessible, however for using this as a library I want to
use a custom installed boost to match the version of boost used by the
application. Most of the changes to CMakeLists are to use find_package
to locate the desired boost libraries. I believe this is the preferred
way to include boost libraries.
Also, this changed to allow llvm to be installed to a specified
directory. This change allows the developer to work with multiple
different versions for different projects.
The bootstrap.sh changes include:
to be installed to. This allows the developer to have multiple
installations.
guessing this was just accidentally commented out.
copmile. Perhaps there's another dependency somewhere else, but I
specifically removed this because it also pulls in a bunch of other
dependencies (notably boost, and I specifically do not want the
maintaner's version of boost installed).
functionality, but it did work prior to the big merge last week).