Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update wind-utils submod #1277

Merged
merged 10 commits into from
Jul 31, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ jobs:
spack -e e4s-build add cmake && \
spack -e e4s-build install && \
quick-create-dev -s nalu-wind@master+tioga+hypre && \
spack manager external ${EXAWIND_MANAGER}/environments/e4s-build --exclude nalu-wind gmake && \
spack manager external ${EXAWIND_MANAGER}/environments/e4s-build --exclude nalu-wind && \
spack install && \
spack cd -b nalu-wind && \
spack build-env nalu-wind ctest -j $(nproc) -L unit --output-on-failure \
Expand Down Expand Up @@ -81,7 +81,7 @@ jobs:
spack -e e4s-build add cmake && \
spack -e e4s-build install && \
quick-create-dev -s nalu-wind@master+tioga+hypre~trilinos-solvers && \
spack manager external ${EXAWIND_MANAGER}/environments/e4s-build --exclude nalu-wind gmake && \
spack manager external ${EXAWIND_MANAGER}/environments/e4s-build --exclude nalu-wind && \
spack install && \
spack cd -b nalu-wind && \
spack build-env nalu-wind ctest -j $(nproc) -L unit --output-on-failure \
Expand Down
2 changes: 1 addition & 1 deletion docs/source/user/build_spack.rst
Original file line number Diff line number Diff line change
Expand Up @@ -230,6 +230,6 @@ Inside the container you can directly load the pre-installed version of Nalu-Win

spack load nalu-wind

`Spack-Manager <https://github.com/sandialabs/spack-manager>`_ is used generate the container and is pre-installed in the container. Additional development of the code can be done through the Spack-Manager's developer tools. A quick-start guide for these tools is available `here <https://sandialabs.github.io/spack-manager/user_profiles/developers/developer_workflow.html>`_. This workflow is how the CI builds are generated in GitHub actions.
`ExaWind-Manager <https://github.com/Exawind/exawind-manager>`_ is used generate the container and is pre-installed in the container. Additional development of the code can be done through the Exawind-Manager's developer tools.

If you are uncomfortable using spack for development then you can also set up your own build workflow in more of a "roll-your-own" development environment using CMake and just utilize the pre-installed TPL's that are available in the container through spack. This really comes down to your development preferences and your comfort level with CMake.
Loading