-
Notifications
You must be signed in to change notification settings - Fork 192
Comparing changes
Open a pull request
base repository: cpp-pm/hunter
base: v0.26.2
head repository: cpp-pm/hunter
compare: v0.26.3
- 13 commits
- 648 files changed
- 1 contributor
Commits on Sep 12, 2025
-
docs: add build_docs.sh script, installing debian packages through apt
Replace the `jenskins.sh` script using pip with `make_docs.sh` script expected to run on Ubuntu. For apt install set non-interactive env variable. Update CI to run on `ubuntu-24.04` instead of `ubuntu-latest`. Remove the files `jenkins.sh` and `requirements.txt`
Configuration menu - View commit details
-
Copy full SHA for 065847f - Browse repository at this point
Copy the full SHA 065847fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 8c6fe77 - Browse repository at this point
Copy the full SHA 8c6fe77View commit details -
Configuration menu - View commit details
-
Copy full SHA for 93d7583 - Browse repository at this point
Copy the full SHA 93d7583View commit details -
Configuration menu - View commit details
-
Copy full SHA for ad1f13e - Browse repository at this point
Copy the full SHA ad1f13eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 7da3888 - Browse repository at this point
Copy the full SHA 7da3888View commit details -
docs: conf.py: remove deprecated get_html_theme_path call (#810)
For Sphinx `v8.1.3` compatibility remove the `get_html_theme_path` call. Fixes: #807
Configuration menu - View commit details
-
Copy full SHA for 5965a8a - Browse repository at this point
Copy the full SHA 5965a8aView commit details -
docs: port foo.rst to foo.md (#808)
I like to write documentation in MarkDown better than in `*.rst`. First step is to have new package documentation in MarkDown. So port the reference `foo.rst` to `foo.md`.
Configuration menu - View commit details
-
Copy full SHA for 16baf8c - Browse repository at this point
Copy the full SHA 16baf8cView commit details -
docs: fix deprecation warning replacing spelling with spelling:word-l…
Configuration menu - View commit details
-
Copy full SHA for d8dee03 - Browse repository at this point
Copy the full SHA d8dee03View commit details
Commits on Sep 15, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 15fa3e1 - Browse repository at this point
Copy the full SHA 15fa3e1View commit details -
libdeflate: add new package with v1.24-p0 (#812)
Need to use a patched version of `libdeflate` as the created CMake config contains absolute paths breaking the caching. Once ebiggers/libdeflate#434 is merged and released we can use pure upstream. Fixes: #804
Configuration menu - View commit details
-
Copy full SHA for edace55 - Browse repository at this point
Copy the full SHA edace55View commit details
Commits on Sep 16, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 2af7b4f - Browse repository at this point
Copy the full SHA 2af7b4fView commit details -
TIFF: update to v4.7.0-p0 (#813)
Unpinn OpenCV 4.10 because TIFF 4.7.0 fixes build issues on Linux. Fixes: #765 Remove old `FindTIFF.cmake` module. Not needed anymore (and probably wasn't needed for a long time). Update to use https://github.com/cpp-pm/libtiff/releases/tag/v4.7.0-p0 hunterized dependencies: - `zlib`: default ON, only dependency available in previous 4.0.2 hunterized version) - `libdeflate`: default: ON, available in Hunter starting with `v0.26.3` #804 - `jpeg`: default OFF, newly hunterized - `lzma`: default OFF, newly hunterized - `zstd`: default OFF, newly hunterized Not hunterized dependencies: - `jbig=OFF` - `lerc=OFF` - `webp=OFF` Update the TIFF example to use use `stdio.h` `remove()` instead of `unlink()`. Fixes: #789
Configuration menu - View commit details
-
Copy full SHA for b923b7d - Browse repository at this point
Copy the full SHA b923b7dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4e67b30 - Browse repository at this point
Copy the full SHA 4e67b30View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.26.2...v0.26.3