- Files adapted from other projects carry both licences: StrongPixelSet.cpp,
SpotExtractorGPU.cu and the four GEMMI-derived structure_refinement files
"GPL-3.0-only AND MPL-2.0"; FFBIDXIndexerCPU.cpp, LMSolver.{h,cpp} and
xds-plugin/plugin.* "GPL-3.0-only AND BSD-3-Clause"; fpga/hls/parallel_stream.h
"CERN-OHL-S-2.0 AND Apache-2.0"; fpga/hls/icmp.cpp and ip_header_checksum.h
(HPCN UAM, with PSI modifications) "CERN-OHL-S-2.0 AND BSD-3-Clause".
- writer/H5FDpoison_sec2.{c,h} and tests/enospc_shim.c: "OR HDF5" is not an
SPDX id; now "OR LicenseRef-HDF5", with the text named (licenses/hdf5.txt).
The poison driver wraps the stock sec2 driver rather than copying it (only
the H5FD_class_t initialiser layout matches H5FDsec2.c), so the files stay
dual-licensed (OR), not derived (AND).
- 151 first-party files without a tag (CMake, shell, Python, frontend, docs
JS, a few C++) get one: GPL-3.0-only, CERN-OHL-S-2.0 for fpga/, fpga/hls/
and fpga/scripts/, with the copyright line of the neighbouring files and the
year the file was added. Generated and vendored code is not touched;
fpga/pcie_driver/postinstall.sh and preuninstall.sh are left untagged, as
they say they are taken from a blog post.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UqXYdJDrM65gxsCn2PrbfK
35 lines
1.6 KiB
Bash
Executable File
35 lines
1.6 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# SPDX-FileCopyrightText: 2026 Filip Leonarski, Paul Scherrer Institute <filip.leonarski@psi.ch>
|
|
# SPDX-License-Identifier: GPL-3.0-only
|
|
# CMake, pinned, from Kitware's own download host.
|
|
#
|
|
# Shared by all four build images (docker/*/Dockerfile). The build context is docker/, so each
|
|
# Dockerfile reaches this with COPY common/. Version inputs come from that Dockerfile's ARGs.
|
|
#
|
|
# The distro CMake is deliberately NOT installed: the four base images ship three different
|
|
# versions (EL8 3.26.5, EL9 3.31.8, Jammy 3.22, Noble 3.28.3), and they move under us at every
|
|
# base-image refresh. That spread is what makes a configure fail on one image and pass on the
|
|
# next -- policy defaults and FetchContent behaviour both depend on it. One pinned CMake
|
|
# everywhere removes the whole class of problem, and it is the only such tool the build cannot
|
|
# pin from inside the repository.
|
|
#
|
|
# cmake.org rather than the GitHub release asset: the images already fetch everything else from
|
|
# GitHub, and GitHub throttles unauthenticated downloads by TLS fingerprint.
|
|
set -eux
|
|
|
|
: "${CMAKE_VERSION:?set CMAKE_VERSION}"
|
|
: "${CMAKE_SHA256:?set CMAKE_SHA256}"
|
|
|
|
series=${CMAKE_VERSION%.*}
|
|
tarball=cmake-${CMAKE_VERSION}-linux-x86_64.tar.gz
|
|
|
|
cd /tmp
|
|
curl -fLO "https://cmake.org/files/v${series}/${tarball}"
|
|
echo "${CMAKE_SHA256} ${tarball}" | sha256sum -c -
|
|
mkdir -p "/opt/cmake-${CMAKE_VERSION}"
|
|
tar -xzf "${tarball}" -C "/opt/cmake-${CMAKE_VERSION}" --strip-components=1
|
|
rm -f "${tarball}"
|
|
|
|
# The Dockerfile puts /opt/cmake-$CMAKE_VERSION/bin on PATH; check the pin took.
|
|
test "$("/opt/cmake-${CMAKE_VERSION}/bin/cmake" --version | head -1)" = "cmake version ${CMAKE_VERSION}"
|