On 28.11.25 14:29, Álvaro Herrera wrote:
>> Another approach I had in mind for some time is to just write out a makefile
>> with the test compile commands, and run that with make -j. Demo patch
>> attached. (I'm not seriously proposing this. For one thing, we probably
>> wouldn't want to introduce a dependency on make. But you could probably
>> write an equivalent ninja.build file.)
>>
>> But this doesn't seem to buy very much. The overhead of the shell script to
>> write out the test files appears to become significant compared the the
>> actual compile commands.
>
> Really? I tried editing the make line to have -j8 (your patch doesn't
> have a -j switch at all there)
Note that the "+" I added to the targets in the top-level GNUmakefile.in
causes the make flags to passed down, so you can run make -jN
headerscheck etc. without having to edit or hardcode the make command
inside the script.
