Recoding cmake to use BLT

blt/0.7.1/.gitignore

@@ -0,0 +1,2 @@
+*.code-workspace
+*.swp

blt/0.7.1/.gitlab-ci.yml

@@ -0,0 +1,53 @@
+##############################################################################
+# Copyright (c) 2017-2025, Lawrence Livermore National Security, LLC and BLT
+# project contributors. See the LICENSE file for details.
+##############################################################################
+
+variables:
+  PROJECT_ALLOC_NAME: ${CI_PROJECT_NAME}_ci_${CI_PIPELINE_ID}
+  BUILD_ROOT: ${CI_PROJECT_DIR}
+  LLNL_SERVICE_USER: atk
+  CUSTOM_CI_BUILDS_DIR: /usr/workspace/atk/gitlab-runner
+
+stages:
+  - allocate
+  - build
+  - release
+
+####
+# Template
+.build_script:
+  script:
+    #Use pre-existing allocation if any
+    - JOBID=$(if [[ "$SYS_TYPE" == "toss_4_x86_64_ib" ]]; then squeue -h --name=${PROJECT_ALLOC_NAME} --format=%A; fi)
+    - ASSIGN_ID=$(if [[ -n "${JOBID}" ]]; then echo "--jobid=${JOBID}"; fi)
+   #BUILD + TEST
+    - echo -e "section_start:$(date +%s):build_and_test\r\e[0K
+      Build and test ${CI_PROJECT_NAME}"
+    - ${ALLOC_COMMAND} .gitlab/build_and_test.sh
+    - echo -e "section_end:$(date +%s):build_and_test\r\e[0K"
+  artifacts:
+    reports:
+      junit: build/junit.xml
+
+####
+# Template
+.run_project_integration_tests:
+  script:
+    - echo -e "section_start:$(date +%s):run_project_integration_tests\r\e[0K
+      Run project integration tests ${CI_PROJECT_NAME}"
+    - ${ALLOC_COMMAND} .gitlab/run_project_integration_tests.sh
+    - echo -e "section_end:$(date +%s):build_and_test\r\e[0K"
+  artifacts:
+    reports:
+      junit: build/junit.xml
+
+
+# This is where jobs are included
+include:
+  - local: .gitlab/build_lassen.yml
+  - local: .gitlab/build_dane.yml
+  - local: .gitlab/build_tioga.yml
+  # ID token requirement for Gitlab 17.0+
+  - project: 'lc-templates/id_tokens'
+    file: 'id_tokens.yml'

blt/0.7.1/.gitlab/run_project_integration_tests.sh

@@ -0,0 +1,8 @@
+#!/bin/bash
+
+BLT_DIR=`pwd`
+RUNNER_SCRIPT=`pwd`/tests/projects/run_tests.py
+HOST_CONFIG_PATH=`pwd`/host-configs/llnl/$SYS_TYPE/$HOST_CONFIG
+
+cd `pwd`/tests/projects/
+python3 $RUNNER_SCRIPT --run-test $ENABLED_BLT_TESTS --host-config $HOST_CONFIG_PATH --verbose --clean --blt-source-dir $BLT_DIR

blt/0.7.1/.mailmap

@@ -0,0 +1,29 @@
+Alan Dayton <dayton8@llnl.gov>                  Alan Dayton <6393677+adayton1@users.noreply.github.com>
+Alex Tyler Chapman <chapman39@llnl.gov>         Alex Tyler Chapman <100869159+chapman39@users.noreply.github.com>
+Alfredo Metere <metal@berkeley.edu>             Alfredo Metere <metere1@llnl.gov>
+Alfredo Metere <metal@berkeley.edu>             metere1llnl <51676123+metere1llnl@users.noreply.github.com>
+Benjamin Curtice Corbett <corbett5@llnl.gov>    Ben Corbett <32752943+corbett5@users.noreply.github.com>
+Brian Manh Hien Han <han12@llnl.gov>            Brian Han <han12@llnl.gov>
+Burl M. Hall <hall53@llnl.gov>                  BurlMHall <47543546+BurlMHall@users.noreply.github.com>
+Daniel Taller <taller1@llnl.gov>                Danny Taller <66029857+dtaller@users.noreply.github.com>
+Geoffrey Oxberry <oxberry1@llnl.gov>            Geoffrey M Oxberry <goxberry@gmail.com>
+Geoffrey Oxberry <oxberry1@llnl.gov>            Geoffrey M. Oxberry <oxberry1@llnl.gov>
+George Zagaris <zagaris2@llnl.gov>              George Zagaris <george.zagaris@gmail.com>
+Jason Burmark <burmark1@llnl.gov>               Jason Burmark <mr.burmark@gmail.com>
+Johann Dahm <johann.dahm@gmail.com>             Johann Dahm <johann.dahm@ibm.com>
+Josh Essman <essman1@llnl.gov>                  Josh Essman <68349992+joshessman-llnl@users.noreply.github.com>
+Keith Healy <healy22@llnl.gov>                  keithhealy <50376825+keithhealy@users.noreply.github.com>
+Kenneth Weiss <kweiss@llnl.gov>                 Kenny Weiss <kennyweiss@users.noreply.github.com>
+Kenneth Weiss <kweiss@llnl.gov>                 Kenny Weiss <kenny@kennyweiss.com>
+Kenneth Weiss <kweiss@llnl.gov>                 Kenneth Weiss <weiss27@llnl.gov>
+Kristi Belcher <belcher6@llnl.gov>              Kristi Belcher <belcher6@corona211.llnl.gov>
+Kristi Belcher <belcher6@llnl.gov>              Kristi Belcher <belcher6@lassen709.coral.llnl.gov>
+Kristi Belcher <belcher6@llnl.gov>              Kristi <belcher6@llnl.gov>
+Marty McFadden <mcfadden8@llnl.gov>             Marty McFadden <mcfadden8@users.noreply.github.com>
+Peter B. Robinson <robinson96@llnl.gov>         robinson96 <robinson96@llnl.gov>
+Peter B. Robinson <robinson96@llnl.gov>         robinspb <manbearkitty@gmail.com>
+Randolph R. Settgast <settgast1@llnl.gov>       Randolph Settgast <rrsettgast@gmail.com>
+Randolph R. Settgast <settgast1@llnl.gov>       Randolph R. Settgast <rrsettgast@gmail.com>
+Randolph R. Settgast <settgast1@llnl.gov>       Randolph Settgast <settgast1@llnl.gov>
+Steve Abbott <stephen.abbott@hpe.com>           Steve Abbott <steve.abt@gmail.com>
+

blt/0.7.1/.readthedocs.yml

@@ -0,0 +1,25 @@
+# .readthedocs.yml
+# Read the Docs configuration file
+# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
+
+# Required
+version: 2
+
+# Set the OS, Python version and other tools you might need
+build:
+  os: ubuntu-22.04
+  tools:
+    python: "3.11"
+  apt_packages:
+    - ghostscript
+    - graphviz
+    - texlive-full
+
+# Optionally set the version of Python and requirements required to build your docs
+python:
+  install:
+    - requirements: docs/requirements.txt
+
+# Build documentation in the docs/ directory with Sphinx
+sphinx:
+  configuration: docs/conf.py

blt/0.7.1/CODE-OF-CONDUCT.md

@@ -0,0 +1,77 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at blt-dev@llnl.gov. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq
+

blt/0.7.1/CONTRIBUTING.md

@@ -0,0 +1,20 @@
+# Contributing to BLT
+
+We welcome contributions to BLT. To do so please submit a pull request through our
+BLT github page at https://github.com/LLNL/blt.
+
+Before submitting a pull request, update `RELEASE-NOTES.md` accordingly.
+
+All contributions to BLT must be made under the BSD License.
+
+Any questions can be sent to blt-dev@llnl.gov.
+
+# Attribution
+
+The BLT project uses git's commit history to track contributions from individual developers. 
+
+Since we want everyone to feel they are getting the proper attribution for their contributions, please add your name to the list below as part of your commit.
+
+# Contributors
+
+Thanks to all of BLT's [contributors](https://github.com/LLNL/blt/graphs/contributors).

blt/0.7.1/LICENSE

@@ -0,0 +1,27 @@
+Copyright (c) 2017-2025, Lawrence Livermore National Security, LLC.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+  list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+  this list of conditions and the following disclaimer in the documentation
+  and/or other materials provided with the distribution.
+
+* Neither the name of the copyright holder nor the names of its
+  contributors may be used to endorse or promote products derived from
+  this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

blt/0.7.1/NOTICE

@@ -0,0 +1,20 @@
+Additional BSD Notice
+
+1. This notice is required to be provided under our contract with the U.S.
+Department of Energy (DOE). This work was produced at Lawrence Livermore
+National Laboratory under Contract No. DE-AC52-07NA27344 with the DOE.
+
+2. Neither the United States Government nor Lawrence Livermore National
+Security, LLC nor any of their employees, makes any warranty, express or
+implied, or assumes any liability or responsibility for the accuracy,
+completeness, or usefulness of any information, apparatus, product, or process
+disclosed, or represents that its use would not infringe privately-owned rights.
+
+3. Also, reference herein to any specific commercial products, process, or
+services by trade name, trademark, manufacturer or otherwise does not
+necessarily constitute or imply its endorsement, recommendation, or favoring by
+the United States Government or Lawrence Livermore National Security, LLC. The
+views and opinions of authors expressed herein do not necessarily state or
+reflect those of the United States Government or Lawrence Livermore National
+Security, LLC, and shall not be used for advertising or product endorsement
+purposes.