Conversation
Run TraceR with a dfly network on the stencil4d-otf example on Travis
…es for stencil4d dfly test
…ode for success/fail
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.
This adds support for building the main TraceR executable with CMake. A first pass has been made at supporting a sphinx doc build target and running the tests using ctest. Building examples has the start of CMake files, but the compiler wrapper for scorep (used for the stencil4d-otf example) has issues during the linking stage, and I think will require upstream support from scorep developers to fix.
There are several other open pull requests (the regression testing one) that should be merged first. There are likely to be some merge conflicts with regression test files that will need resolving once that happens.
Example usage (assuming dependencies are installed to the home directory):
Paths to the install prefixes for dependencies can be given using the ;-separated list as shown above (e.g. for BigSim support, add the install prefix for BigSim/Charm). As an alternative, there are CMake variables that can be set when configuring the project with cmake, such as:
If dependencies are in standard system install locations or set in the right environment variables (e.g.
PATH,LD_LIBRARY_PATH) they should be found automatically without listing the paths.