2026.10.1.3: a source for every tool a build uses, declared, programmable and observable (#755) by speak-agent · Pull Request #758 · mcpp-community/mcpp

feat: a source for every tool a build uses, declared, programmable and observable

speak-agent

committed

ef6b450

fix: the toolchain stamp formats its numbers explicitly, and the design record carries front matter

speak-agent

committed

d7da9cc

fix: the stated tools of a toolchain are a named struct, not a std::pair specialization

speak-agent

committed

e28609f

fix: the new lookups use a predicate, not a projection by pointer-to-member

speak-agent

committed

6193d62

docs: a toolchain named by path is recorded beside the build, and mcpp.lock is not claimed to hold it

speak-agent

committed

1143154

test: config.toml's overrides are read by a function a test can call

speak-agent

committed

23c5843

build: a build program's compile command goes through a response file when it outgrows the channel

speak-agent

committed

d2ba022

test: the response file's quoting, the part of it a host cannot demonstrate

speak-agent

committed

eb386f6

platform: which() resolves a name the shell answers for itself

speak-agent

committed

89ed2cd

build: the response file is written in the grammar its driver reads

speak-agent

committed

02df8c3

docs: the design record states where the response-file path is covered

speak-agent

committed

f1cf90d

docs: the project's own statement is the root manifest, or the workspace manifest where a member is built

speak-agent

committed

7819a28

manifest: a key this engine does not know says which engine the package needs

speak-agent

committed

a5728dd

docs: the release notes carry the three fixes the other platforms asked for

speak-agent

committed

77b632f

build: the GNU response file doubles backslashes, because the tokenizer escapes them inside quotes too

speak-agent

committed

49abb10

toolchain: a stated linker reaches the link on every shape, and gcc says it cannot

speak-agent

committed

cb91861

docs: the toolchain page states that a stated linker is clang's, and its gcc example no longer states one

speak-agent

committed

3fa5533

tests: the counterexample for a gcc tree that states a linker

speak-agent

committed

2939d65

sources: an override's path resolves the executable suffix the host appends itself

speak-agent

committed

136eb2a

tests: the new fixtures write host spellings into the manifests they generate

speak-agent

committed

51b66ce

Navigation Menu

2026.10.1.3: a source for every tool a build uses, declared, programmable and observable (#755) - #758

2026.10.1.3: a source for every tool a build uses, declared, programmable and observable (#755)#758
speak-agent merged 20 commits into
mainfrom
feat/build-sources

Commits on Oct 1, 2026

feat: a source for every tool a build uses, declared, programmable and observable

fix: the toolchain stamp formats its numbers explicitly, and the design record carries front matter

fix: the stated tools of a toolchain are a named struct, not a std::pair specialization

fix: the new lookups use a predicate, not a projection by pointer-to-member

docs: a toolchain named by path is recorded beside the build, and mcpp.lock is not claimed to hold it

test: config.toml's overrides are read by a function a test can call

build: a build program's compile command goes through a response file when it outgrows the channel

test: the response file's quoting, the part of it a host cannot demonstrate

platform: which() resolves a name the shell answers for itself

build: the response file is written in the grammar its driver reads

docs: the design record states where the response-file path is covered

docs: the project's own statement is the root manifest, or the workspace manifest where a member is built

manifest: a key this engine does not know says which engine the package needs

docs: the release notes carry the three fixes the other platforms asked for

build: the GNU response file doubles backslashes, because the tokenizer escapes them inside quotes too

toolchain: a stated linker reaches the link on every shape, and gcc says it cannot

docs: the toolchain page states that a stated linker is clang's, and its gcc example no longer states one

tests: the counterexample for a gcc tree that states a linker

sources: an override's path resolves the executable suffix the host appends itself

tests: the new fixtures write host spellings into the manifests they generate