I am adding a new package to the container, here are the details.
What new packages does this PR add to the development container?
This does two things:
65 Split the package installation up into multiple steps
64 Install some additional developer tools, ccmake, clang, and clang-tidy in particular
Working around the issue in #66 by running the container by the sha256 hash rather than the tag, I can build ldmx-sw both with GCC and Clang as well as running clang-tidy on the whole codebase.
Check List
[x] I successfully built the container using docker
[x] I was able to build ldmx-sw using this new container build
[x] I was able to test run a small simulation and reconstruction inside this container
# outline of test instructions
cd $LDMX_BASE/ldmx-sw/build
ldmx ctest
cd ..
for c in `ls ldmx-sw/*/test/*.py`; ldmx fire $c; done
One interesting thing I noted though: Our software does not run if you compile it with link time optimization. That's a bit concerning.
[x] I was able to successfully use the new packages. Explain what you did to test them below:
I am adding a new package to the container, here are the details.
What new packages does this PR add to the development container?
This does two things:
65 Split the package installation up into multiple steps
64 Install some additional developer tools, ccmake, clang, and clang-tidy in particular
Working around the issue in #66 by running the container by the sha256 hash rather than the tag, I can build ldmx-sw both with GCC and Clang as well as running clang-tidy on the whole codebase.
Check List
[x] I successfully built the container using docker
[x] I was able to build ldmx-sw using this new container build
[x] I was able to test run a small simulation and reconstruction inside this container
One interesting thing I noted though: Our software does not run if you compile it with link time optimization. That's a bit concerning.
[x] I was able to successfully use the new packages. Explain what you did to test them below: