Skip to content
Snippets Groups Projects
Select Git revision
20 results
Search by author
  • Any Author
  • Peter Kokot Peter Kokot petk
  • buildbot buildbot buildbot
2 authors
  1. Nov 11, 2024
    • Brad King's avatar
      FindBoost: Add support for Boost 1.86 · f941fb6c
      Brad King authored 
      Update the list of known versions.

Run the command

    cmake -DBOOST_DIR=/path/to/boost_1_86_0 \
      -P Utilities/Scripts/BoostScanDeps.cmake

to extract dependencies from the 1.86.0 source tree.
They are the same as 1.85's dependencies, so just update
the version check for warning about newer versions.

Fixes: #26433
      f941fb6c
  3. Nov 01, 2024
  5. Oct 31, 2024
    • Ben Boeckel's avatar
      gitlab-ci: remove `dependencies` from jobs · ea31d090
      Ben Boeckel authored 
      Historically, `needs` specifies the jobs which need to complete
successfully and `dependencies` specifies the jobs which provide
artifacts which should be used. Modern GitLab discourages using both as
`needs` now supports an `artifacts` key to say "depend on but do not use
artifacts", so remove `dependencies` and use `needs:artifacts` where
necessary.

See: https://docs.gitlab.com/ee/ci/yaml/#needsartifacts
      ea31d090
    • Ben Boeckel's avatar
      ci: use JSON to transfer environment variables · c1ddff67
      Ben Boeckel authored 
      The `set` command in `cmd` has terrible properties in that there's no
real structure to it. Sensitive sequences in values or variable names
that are escaping sequences can be interpreted at the wrong time or
things like newlines in values are not escaped at all and cause
ambiguities in parsing. Avoid all of that and use PowerShell to use JSON
as a communication mechanism.
      c1ddff67
  7. Oct 19, 2024
  9. Oct 18, 2024
  11. Oct 17, 2024
  13. Oct 15, 2024
  15. Oct 08, 2024
  17. Oct 07, 2024
    • Craig Scott's avatar
      project: Only check non-cache vars when setting project vars · fa07ddfe
      Craig Scott authored and Brad King's avatar Brad King committed 
      The change in commit 86ad7cc8 (project: Only define non-cache vars if
already defined, 2024-09-15, v3.30.4~2^2) was meant to only check for
non-cache variables when deciding whether to set non-cache project
variables for the current call.  However, it erroneously checked for any
variable, including cache variables.  This gives the intended result on
the first run, but on subsequent runs a cache variable will exist that
did not on the first run, leading to different behavior between the two
runs.  Fix the logic to only check for a pre-existing non-cache
variable, as was originally intended.

Fixes: #26355
      fa07ddfe
  19. Sep 27, 2024
  21. Sep 26, 2024
  23. Sep 23, 2024
  25. Sep 20, 2024
    • Craig Scott's avatar
      project: Only define non-cache vars if already defined · 86ad7cc8
      Craig Scott authored and Brad King's avatar Brad King committed 
      In c1ece78d (project: non cache <project> prefix variables are
also created, 2024-08-27), we started explicitly setting the non-cache
variable for <projectName>_SOURCE_DIR, <projectName>_BINARY_DIR,
and <projectName>_IS_TOP_LEVEL in addition to setting them as
cache variables. This changed the behavior when a project name
was used more than once, and the second project call happens in
the same scope or a child scope of the first. Previously, the first
project call would set cache variables, and the second project call
would not overwrite those cache variables. With the change in
c1ece78d, after the second project call the non-cache variables
would mask the cache variables and the project code would see
a different value to what it did before.

Setting the non-cache variable was added to handle the case where
a call to FetchContent_MakeAvailable() would set some non-cache
variables, and it just so happened those matched the same cache
variables that the project() command would set in the project being
fetched. The fetched project would then see a different set of
project-specific variables compared to when it was built standalone.

This commit here narrows the change from c1ece78d such that
the non-cache variable is only set by project() if there was already
a non-cache variable set. This still fixes the motivating problem
c1ece78d was intended to solve, but it avoids changing the variable
values seen by a project that re-uses the same project name in related scopes.

Issue: #26243, #25714
Fixes: #26281
      86ad7cc8
    • Craig Scott's avatar
      Help: State valid scopes for using proj_SOURCE_DIR and proj_BINARY_DIR · 4c152752
      Craig Scott authored and Brad King's avatar Brad King committed 
      Issue: #25714
      4c152752
    • Brad King's avatar
      Merge topic 'cpack-nuget-native' into release-3.30 · 6323fdc9
      Brad King authored and Kitware Robot's avatar Kitware Robot committed 
      
c3588729 CPack/NuGet: Add native0.0 to build dependencies in groups

Acked-by: default avatarKitware Robot <kwrobot@kitware.com>
Merge-request: !9829
      6323fdc9
    • Brad King's avatar
      Merge topic 'FindMatlab-mcr' into release-3.30 · 304c47a7
      Brad King authored and Kitware Robot's avatar Kitware Robot committed 
      
9ceca05e FindMatlab: Search mex and mx libraries for MCR
67e3c6b6 FindMatlab: Cache whether MATLAB root contains MCR or MATLAB
b426ce1d FindMatlab: Add support for MCR distributions without mex.h
cd4782ba FindMatlab: Only consider versioned MCR subdirectory if it exists

Acked-by: default avatarKitware Robot <kwrobot@kitware.com>
Merge-request: !9831
      304c47a7
    • Brad King's avatar
      Merge topic 'ci-xcode-16.0' into release-3.30 · c544ad87
      Brad King authored and Kitware Robot's avatar Kitware Robot committed 
      
cc293b49 ci: Run RunCMake.ExternalProject serially in macos-x86_64 Xcode job
26359076 gitlab-ci: update macOS jobs to use Xcode 16.0

Acked-by: default avatarKitware Robot <kwrobot@kitware.com>
Merge-request: !9830
      c544ad87
  27. Sep 19, 2024
  29. Sep 18, 2024
  31. Sep 17, 2024
  33. Sep 16, 2024
  35. Sep 13, 2024