compiletools 10.2.1__tar.gz → 10.3.0__tar.gz

{compiletools-10.2.1 → compiletools-10.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: compiletools
-Version: 10.2.1
+Version: 10.3.0
 Summary: Tools to make compiling C/C++ projects easy
 Keywords: c++,make,development
 Author: DrGeoff
@@ -75,7 +75,7 @@ C/C++ build tools that requires almost no configuration.
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-05-09
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "compiletools"
-version = "10.2.1"
+version = "10.3.0"
 description = "Tools to make compiling C/C++ projects easy"
 readme = "src/compiletools/README.ct-doc.rst"
 requires-python = ">=3.10"
@@ -133,7 +133,7 @@ include = [
 ]
 
 [tool.bumpversion]
-current_version = "10.2.1"
+current_version = "10.3.0"
 parse = "(?P<major>\\d+)\\.(?P<minor>\\d+)\\.(?P<patch>\\d+)"
 serialize = ["{major}.{minor}.{patch}"]
 search = "{current_version}"

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/CLAUDE.md

@@ -63,7 +63,7 @@ The flow inside one parseargs invocation: `create_parser` → `extract_variant(a
 
 Multi-conf concatenation: `_open_config_files` prepends a `# --- <name> ---` + `# __ct_conf_dir__=<abs/dir>` header pair before each file's body. The parser tracks a `marker_expected` flag flipped on by the segment header and consumed by the next non-blank line — so a user comment that happens to contain the marker string mid-file can't poison subsequent expansions.
 
-Provenance side channel: `(expanded_value, source_file, lineno)` per parsed entry, accumulated in `self._provenance` and exposed via `_ComposingArgumentParser.get_conf_file_provenance()` (returns a shallow copy; the inner tuples are immutable). `_setup_pkg_config_overrides_locked` consumes it at `verbose >= 4` to attribute every emitted `Prepended/Appended pkg-config path: ...` with `(from /abs/conf:N)` / `(from CLI)` / `(auto-discovered: cwd|gitroot)`. The `args.*` shapes are unchanged — provenance is a parallel channel, not a wrapping of the parsed values.
+Provenance side channel: `(expanded_value, source_file_abspath, lineno, pre_expansion_literal)` per parsed entry, accumulated in `self._provenance` and exposed via `_ComposingArgumentParser.get_conf_file_provenance()` (returns a shallow copy; the inner tuples are immutable). Two consumers: `_setup_pkg_config_overrides_locked` at `verbose >= 4` attributes every emitted `Prepended/Appended pkg-config path: ...` with `(from /abs/conf:N)` / `(from CLI)` / `(auto-discovered: cwd|gitroot)`; `apptools._note_shadowed_bare_hook_values` at `verbose >= 1` names the conf file and line of every bare `prebuild-script`/`postbuild-script` value that lost a last-writer-wins contest (a lookup failure there degrades to a breadcrumb note, never an error). The `args.*` shapes are unchanged — provenance is a parallel channel, not a wrapping of the parsed values.
 
 ## `PKG_CONFIG_PATH` ordering: conf-layer priority
 
@@ -89,7 +89,7 @@ Why this is load-bearing (the bug it fixes): the precompile rules deliberately r
 
 ## Magic detection: `MacroState` cache-key details
 
-`MacroState` in `preprocessing_cache.py` separates static compiler built-ins (~388 macros, immutable) from dynamic file `#define`s (variable). Cache keys only hash variable macros — ~80% reduction in key computation cost. Lazy frozenset computation with incremental updates for pure additions (the common case). The build-context portion of the hash also folds in `compiler_identity(args.CXX, anchor_root=...)` (a `realpath|size|mtime_ns` triple resolved via `apptools.compiler_identity`, exposed on `args.flags.compiler_identity`) so an in-place toolchain swap that leaves `args.CXX` unchanged still invalidates per-TU object cache entries (symmetric with the PCH cache key). The realpath segment is routed through `canonicalize_path_for_cache_key` so an in-workspace wrapper script (coverage shim, sccache/distcc wrapper) at e.g. `<gitroot>/tools/cxx-wrapper.sh` doesn't leak its per-checkout prefix into the cache key.
+`MacroState` in `preprocessing_cache.py` separates static compiler built-ins (~388 macros, immutable) from dynamic file `#define`s (variable). Cache keys only hash variable macros — ~80% reduction in key computation cost. Lazy frozenset computation with incremental updates for pure additions (the common case). The build-context portion of the hash also folds in `compiler_identity(args.CXX, anchor_root=...)` (a `realpath|size|mtime_ns` triple resolved via `apptools.compiler_identity`, exposed on `args.flags.compiler_identity`) so an in-place toolchain swap that leaves `args.CXX` unchanged still invalidates per-TU object cache entries (symmetric with the PCH cache key). The realpath segment is routed through `canonicalize_path_for_cache_key` so an in-workspace wrapper script (coverage shim, sccache/distcc wrapper) at e.g. `<gitroot>/tools/cxx-wrapper.sh` doesn't leak its per-checkout prefix into the cache key. The build-context hash also folds a snapshot of the CPATH-family env vars (`INCLUDE_PATH_ENV_VARS`: `CPATH`, `C_INCLUDE_PATH`, `CPLUS_INCLUDE_PATH`, `OBJC_INCLUDE_PATH`; unset ≡ empty, matching `_link_environment_snapshot`) because they change which headers the compiler resolves without appearing in any flag string — ccache hashes the same four, though verbatim: compiletools runs each `os.pathsep` entry through `canonicalize_path_for_cache_key` first, so a gitroot-prefixed entry hashes identically across checkouts. `DirectHeaderDeps` symmetrically appends those directories to its flat include search list (after CPPFLAGS-derived `-I` dirs, CPATH first, mirroring gcc's `-I`-then-`-isystem` staging) so env-only headers are walked and content-hashed into `dep_hash`; the link-side `_LINK_ENVIRONMENT_VARS` list in `backend_command_args.py` is deliberately separate and must stay byte-stable.
 
 ## Naming history
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.cleanup-remote-locks.rst

@@ -8,7 +8,7 @@ Legacy helper for pruning stale lockdir directories remotely
 
 :Author: drgeoffathome@gmail.com
 :Date:   2025-11-26
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.create-documentation.rst

@@ -8,7 +8,7 @@ Generate man(1) pages from the reStructuredText source tree
 
 :Author: drgeoffathome@gmail.com
 :Date:   2025-11-26
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-backends.rst

@@ -8,7 +8,7 @@ Build backend architecture and selection guide
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-04-02
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 7
 :Manual group: developers
 
@@ -330,9 +330,20 @@ backends accept it consistently.
   empty files at target paths whose recipes have no real prerequisites
   in CAS-only mode, corrupting the cache.  Use ``--use-mtime=True`` if
   you need to mark a build up-to-date without running it.
-* System / ``/usr/include`` headers are not in the cache key (matches
-  ccache/sccache contract).  An in-place compiler swap usually changes
-  ``compiler_identity`` and invalidates the cache implicitly.
+* System / ``/usr/include`` headers are not in the cache key (ccache
+  and sccache likewise exclude default system headers).  An in-place
+  compiler swap usually changes ``compiler_identity`` and invalidates
+  the cache implicitly.
+* The ``CPATH`` / ``C_INCLUDE_PATH`` / ``CPLUS_INCLUDE_PATH`` /
+  ``OBJC_INCLUDE_PATH`` values ARE in the compile cache key (ccache
+  hashes the same four, though verbatim — compiletools first
+  canonicalizes each path entry so a gitroot-prefixed entry hashes
+  identically across checkouts), and headers found via those
+  directories are walked and content-hashed into ``dep_hash`` like any
+  ``-I`` header.  One residual gap: the header walk keeps a single
+  flat search list for C and C++ alike, so a basename present in both
+  a ``C_INCLUDE_PATH`` dir and a ``CPLUS_INCLUDE_PATH`` dir with
+  differing content may hash the copy the compiler does not use.
 
 CHOOSING A BACKEND
 ==================

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-build-docs.rst

@@ -8,7 +8,7 @@ Build the compiletools documentation site locally.
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-05-04
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-build-dynamic-library.rst

@@ -8,7 +8,7 @@ Produce a shared object from a root source file with zero boilerplate
 
 :Author: drgeoffathome@gmail.com
 :Date:   2025-11-26
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-build-static-library.rst

@@ -8,7 +8,7 @@ Generate a static library from a root source file in one shot
 
 :Author: drgeoffathome@gmail.com
 :Date:   2025-11-26
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-build.rst

@@ -8,7 +8,7 @@ One-command Make-specific wrapper around ct-findtargets + make
 
 :Author: drgeoffathome@gmail.com
 :Date:   2025-11-26
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-cache-report.rst

@@ -8,7 +8,7 @@ Summarize occupancy and detect duplication across the CAS directories
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-06-11
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-cake.rst

@@ -9,7 +9,7 @@ Swiss army knife for building a C/C++ project
 :Author: drgeoffathome@gmail.com
 :Date:   2026-05-09
 :Copyright: Copyright (C) 2011-2016 Zomojo Pty Ltd
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 
@@ -283,11 +283,60 @@ Both options accept a **shell command string** (executed via ``/bin/sh
 so output appears live. Both abort ct-cake with a non-zero exit on the
 first script that fails. Neither runs on ``--clean`` / ``--realclean``.
 
-Each option may be given multiple times. Like other ``action="append"``
-options, the entries **accumulate** across all configuration layers
-(bundled < system < venv < user < project < cwd < env < CLI) — a
-project's ``ct.conf`` listing one script plus a variant ``.conf``
-listing another yields both, in declaration order.
+Each option may be given multiple times on the command line, and CLI
+values combine with conf-file values. In conf files, however, the bare
+``prebuild-script`` / ``postbuild-script`` keys follow the same
+last-writer-wins rule as every other non-``append-``/``prepend-`` key:
+when two conf or env layers in the hierarchy (bundled < system < venv
+< user < project < cwd < env) both set the bare key, the
+higher-priority layer **replaces** the lower one (CLI is the
+exception: bare CLI values combine with the surviving conf value, as
+above). That makes the bare key the right
+spelling for a deliberate per-project override — including
+``prebuild-script = []`` to suppress a globally-configured hook, or a
+JSON list (``prebuild-script = ["./gen_a.sh", "./gen_b.sh"]``) to set
+several scripts at once. Because a replaced hook simply never runs —
+there is no error at the point of damage — ct-cake emits a stderr
+note at ``-v`` and above for every conf-file hook value that lost a
+bare-key contest (whether to a higher layer, an environment variable,
+or a later line in the same conf file), naming the conf file and line
+it came from.
+
+To **accumulate** hooks across layers instead — a repo-wide generator
+in ``ct.conf.d/ct.conf`` plus a per-variant hook, both running — use
+the accumulating key spelling::
+
+    # ct.conf.d/ct.conf (repo-wide layer)
+    append-PREBUILD-SCRIPT = ./tools/gen_appinfo.sh appinfo.cpp
+
+    # ct.conf.d/asan.conf (variant layer, adds a second hook)
+    append-PREBUILD-SCRIPT = ./tools/gen_asan_suppressions.sh
+
+``append-PREBUILD-SCRIPT`` / ``prepend-PREBUILD-SCRIPT`` (and the
+``POSTBUILD`` twins) merge into the bare-key list the same way the
+other ``append-``/``prepend-`` conf keys compose: prepend entries land
+leftmost, append entries land rightmost, lower layers before higher
+ones, and entries already present in the list are not duplicated
+(each group is deduped against the list accumulated so far — the
+bare-key base for ``prepend-`` entries, base plus prepend
+contributions for ``append-`` entries — but never against other
+entries of its own group: the same script appended in two layers runs
+twice). Note the asymmetry with
+suppression: ``prebuild-script = []`` clears only bare-key values;
+entries contributed via ``append-``/``prepend-`` in any layer cannot
+be suppressed by a higher layer. Use the bare key for
+globally-configured hooks that individual projects may need to opt
+out of.
+Conf keys are case-sensitive — the accumulating forms must be spelled
+with the uppercase option name (``append-PREBUILD-SCRIPT``, not
+``append-prebuild-script``; the lowercase form is silently ignored).
+
+An environment variable (e.g. ``PREBUILD_SCRIPT``) overrides
+conf-file values per the standard hierarchy (environment variables >
+config files > defaults). Bare CLI values sit outside that override
+chain for these keys: as noted above, ``--prebuild-script`` combines
+with whatever value survived the env/conf contest rather than
+replacing it.
 
 Worked example (the generated-implementation-file pattern recommended
 above; full runnable version under ``examples-end-to-end/appinfo``)::
@@ -542,12 +591,29 @@ exist", a few classical Make/Ninja workflows behave differently:
 
 * **System / ``/usr/include`` headers are not in the cache key.**
   A glibc upgrade between CI runs will silently reuse cached objects
-  built against the prior glibc. This matches the ccache / sccache
-  contract but surprises users coming from full-rebuild CI. If you
-  need glibc-version sensitivity in the cache key, fold it into the
-  ``compiler_identity`` triple (in practice, an in-place compiler
-  swap usually changes ``compiler_identity`` and invalidates the
-  cache implicitly).
+  built against the prior glibc. ccache and sccache likewise exclude
+  default system headers, but this surprises users coming from
+  full-rebuild CI. If you need glibc-version sensitivity in the cache
+  key, fold it into the ``compiler_identity`` triple (in practice, an
+  in-place compiler swap usually changes ``compiler_identity`` and
+  invalidates the cache implicitly).
+
+* **Include-path environment variables ARE in the compile cache key.**
+  ``CPATH``, ``C_INCLUDE_PATH``, ``CPLUS_INCLUDE_PATH``, and
+  ``OBJC_INCLUDE_PATH`` participate in the per-TU
+  ``macro_state_hash`` (ccache hashes the same four, though verbatim —
+  compiletools first canonicalizes each path entry, so a
+  gitroot-prefixed entry hashes identically across checkouts rather
+  than keying the cache to one workspace), and headers found via those
+  directories are walked and content-hashed into ``dep_hash`` like any
+  ``-I`` header — editing a header reachable only via ``CPATH``, or
+  changing the value of one of these vars, invalidates cached objects.
+  One residual gap: the header walk keeps a single flat search list
+  for C and C++ alike, so a basename present in both a
+  ``C_INCLUDE_PATH`` dir and a ``CPLUS_INCLUDE_PATH`` dir with
+  differing content may hash the copy the compiler does not use — an
+  edit to the compiler-resolved header in that shadowing scenario is
+  not guaranteed to invalidate.
 
 * **Linker-time environment variables ARE in the link key.**
   ``SOURCE_DATE_EPOCH``, ``LD_LIBRARY_PATH``, ``LIBRARY_PATH``, and
@@ -984,7 +1050,7 @@ Detection trips on whether ``gtest/gtest.h``, ``doctest/doctest.h``
 transitive header set. A test that pulls in two framework headers
 at once is rejected with an error naming both — disambiguate by
 fixing the include paths. A test that matches none runs normally
-and produces no XML; a warning is emitted at ``--verbose=1``.
+and produces no XML; a warning is emitted at ``-v`` and above.
 
 The XML argv is appended *after* the exe_path so prefix tools like
 ``valgrind --quiet`` (passed via ``--TESTPREFIX``) forward the XML

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-cas-publish.rst

@@ -8,7 +8,7 @@ Atomically publish a CAS artefact at a stable user-facing path
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-05-09
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-check-venv.rst

@@ -8,7 +8,7 @@ Verify that the ct-cake on PATH imports the same compiletools as the venv
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-05-09
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-cleanup-locks.rst

@@ -8,7 +8,7 @@ Clean up stale lock directories from file locking
 
 :Author: drgeoffathome@gmail.com
 :Date:   2025-10-16
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 
@@ -214,7 +214,7 @@ TROUBLESHOOTING
 ===============
 **Locks not being removed**
 
-- Check lock age with ``--verbose 2``
+- Check lock age with ``-vv``
 - Verify locks are older than ``--min-lock-age``
 - For remote locks, verify SSH connectivity
 - Check permissions on lockdir

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-commandline.rst

@@ -9,7 +9,7 @@ This document describes the command line arguments that are common across ct-* p
 :Author: drgeoffathome@gmail.com
 :Date:   2017-07-06
 :Copyright: Copyright (C) 2011-2016 Zomojo Pty Ltd
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-compilation-database.rst

@@ -8,7 +8,7 @@ Generate compile_commands.json for clang tooling and IDE integration
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-05-09
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-config.rst

@@ -9,7 +9,7 @@ Helper tool for examining ct-* configuration
 :Author: drgeoffathome@gmail.com
 :Date:   2016-08-16
 :Copyright: Copyright (C) 2011-2016 Zomojo Pty Ltd
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 
@@ -374,10 +374,16 @@ hierarchy is used to overwrite the final value
 
 Conf files are read in low-to-high priority order:
 ``ct.conf (bundled→cwd) < axis_1 (bundled→cwd) < axis_2 < ... < composite_override < --config``.
-Scalar keys (``CC``, ``CXX``, …) follow last-writer-wins. Append-style
+Scalar keys (``CC``, ``CXX``, …) follow last-writer-wins — as do
+list-valued keys without the prefix (``pkg-config``,
+``prebuild-script``, ``postbuild-script``). Append-style
 keys (``append-CFLAGS``, ``append-CXXFLAGS``, ``append-LDFLAGS``,
-``append-INCLUDE``, ``append-pkg-config-path``, …) accumulate across the
-entire stack: every contributing conf file's value is preserved, and
+``append-INCLUDE``, ``append-PKG-CONFIG-PATH``, ``append-PKG-CONFIG``,
+``append-PREBUILD-SCRIPT``, ``append-POSTBUILD-SCRIPT``, …) accumulate
+across the entire stack. Conf keys are case-sensitive: the key must
+match the CLI option's spelling exactly (minus the leading dashes), so
+lowercase forms like ``append-prebuild-script`` are silently ignored.
+Accumulation means: every contributing conf file's value is preserved, and
 matching ``--append-*`` / ``--prepend-*`` CLI flags accumulate on top
 of the conf-file values (CLI tokens land after conf tokens in the
 joined flag string, so the compiler's "last occurrence wins" rule

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-cppdeps.rst

@@ -9,7 +9,7 @@ C/C++ dependency analysis using the preprocessor
 :Author: drgeoffathome@gmail.com
 :Date:   2022-06-05
 :Copyright: Copyright (C) Geoffery Ericksson
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-create-makefile.rst

@@ -8,7 +8,7 @@ Generate Makefile from compiletools magic
 
 :Author: drgeoffathome@gmail.com
 :Date:   2024-11-24
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-debug-pcm-hash-inputs.rst

@@ -8,7 +8,7 @@ Dump the inputs that drive a C++20 module BMI's ``<cas-pcmdir>/<cmd_hash>/`` pat
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-05-31
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-doc.rst

@@ -19,7 +19,7 @@ C/C++ build tools that requires almost no configuration.
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-05-09
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-fetch.rst

@@ -8,7 +8,7 @@ Clone, update, or report the //#GIT= external repositories a build depends on
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-07-01
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-filelist.rst

@@ -9,7 +9,7 @@ Determine header and source dependencies of a C/C++ file by following headers an
 :Author: drgeoffathome@gmail.com
 :Date:   2017-07-06
 :Copyright: Copyright (C) 2011-2016 Zomojo Pty Ltd
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-findtargets.rst

@@ -9,7 +9,7 @@ Find executable and test targets in a C/C++ project
 :Author: drgeoffathome@gmail.com
 :Date:   2018-04-17
 :Copyright: Copyright (C) 2011-2018 Zomojo Pty Ltd
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-git-sha-report.rst

@@ -8,7 +8,7 @@ Report git blob SHA hashes for files in the repository
 
 :Author: drgeoffathome@gmail.com
 :Date:   2024-11-24
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-gitroot.rst

@@ -9,7 +9,7 @@ Display the git repository root directory
 :Author: drgeoffathome@gmail.com
 :Date:   2017-09-28
 :Copyright: Copyright (C) 2011-2016 Zomojo Pty Ltd
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-headertree.rst

@@ -9,7 +9,7 @@ Create a tree of header dependencies starting at the given C/C++ file
 :Author: drgeoffathome@gmail.com
 :Date:   2018-07-26
 :Copyright: Copyright (C) 2011-2018 Zomojo Pty Ltd
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-jobs.rst

@@ -9,7 +9,7 @@ Determine optimal parallel job count for builds
 :Author: drgeoffathome@gmail.com
 :Date:   2017-04-28
 :Copyright: Copyright (C) 2011-2016 Zomojo Pty Ltd
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-list-backends.rst

@@ -8,7 +8,7 @@ List available build backends
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-03-31
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-list-variants.rst

@@ -9,7 +9,7 @@ List available build variants
 :Author: drgeoffathome@gmail.com
 :Date:   2016-08-16
 :Copyright: Copyright (C) 2011-2016 Zomojo Pty Ltd
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-lock-helper.rst

@@ -8,7 +8,7 @@ Helper for file locking during concurrent compilation
 
 :Author: drgeoffathome@gmail.com
 :Date:   2024-01-01
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-magicflags.rst

@@ -9,7 +9,7 @@ Show the magic flags / magic comments that a file exports
 :Author: drgeoffathome@gmail.com
 :Date:   2018-02-23
 :Copyright: Copyright (C) 2011-2018 Zomojo Pty Ltd
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-otel.rst

@@ -8,7 +8,7 @@ Export ct-cake build timing as OpenTelemetry (OTLP) traces and metrics
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-05-27
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-pytest-monitor.rst

@@ -8,7 +8,7 @@ Run pytest with crash-survivable diagnostics (Termux/OOM friendly)
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-05-04
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-release.rst

@@ -8,7 +8,7 @@ Automated version bump + build + publish for compiletools
 
 :Author: drgeoffathome@gmail.com
 :Date:   2025-11-26
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-timing-report.rst

@@ -8,7 +8,7 @@ Analyze and display build timing reports
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-04-06
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-trim-cache.rst

@@ -8,7 +8,7 @@ Trim stale entries from the object, PCH, PCM, and linker-artefact CAS directorie
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-06-11
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-venv-install-rhel8.rst

@@ -8,7 +8,7 @@ One-command compiletools dev bootstrap for RHEL 8 / CentOS 8 / Rocky 8
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-05-07
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-venv-install-termux.rst

@@ -8,7 +8,7 @@ One-command compiletools dev bootstrap for Termux (Android, aarch64)
 
 :Author: drgeoffathome@gmail.com
 :Date:   2026-05-03
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.ct-watch-build.rst

@@ -8,7 +8,7 @@ Continuous rebuild helper that watches sources with inotify
 
 :Author: drgeoffathome@gmail.com
 :Date:   2025-11-26
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers
 

{compiletools-10.2.1 → compiletools-10.3.0}/src/compiletools/README.profile-ct-cake-worktree.rst

@@ -8,7 +8,7 @@ Safely profile ct-cake performance using temporary git worktrees
 
 :Author: drgeoffathome@gmail.com
 :Date:   2025-11-26
-:Version: 10.2.1
+:Version: 10.3.0
 :Manual section: 1
 :Manual group: developers