You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
build: a build program's compile command goes through a response file when it outgrows the channel
A build program that imports many host modules carries one
`-fmodule-file=<name>=<path>` per module, with absolute paths, and on Windows
`capture_exec` reaches a shell that tolerates 8191 bytes. mcpp-plugins'
all-rules-compile fixture imports fifteen and crossed that line the moment the
collection gained one more module, reporting only
The command line is too long.
build.mcpp failed to compile (exit 1)
which names neither the length nor the cause -- the family mcpp.build.cmdlimits
exists to make legible. The command now goes through `@file` when it is over
the budget that module states, which every driver mcpp supports reads, and the
file stays beside the program for a failed compile to show. Its quoting is
`response_file_body`, exported and covered by a unit case, because the command
it serves cannot be run on a host whose limit it does not cross.
0 commit comments