Not sure if this is an nRF Connect or VS Code or Zephyr or West or some combination of the above, but I'd like to configure the development environment (nRF Connect extension in VS Code) to only use a single processor core on the PC when building. NOTE: I am not talking about the build target having a single or multiple cores, but rather the building itself should only occur on a single core and/or thread so that the build log outputs that stream to the terminal are not interleaved or stepping all over each other.
Specifically, I'm running into the same issue I've had with other build tools in the past where the build "log" is non-deterministic even when building the same source code with the same parameters, making it extremely difficult to compare consecutive "logs" to see what has changed and might be the cause of something breaking. In other IDEs/build environments I've usually been able to tell it to only use a single thread/core (at the expense of speed) but I'm having trouble locating the magic incantation to use for this current setup.
Related question, is there any way to automatically have the build "log" stream to a file so I don't have to manually cut and paste from the terminal window every time? The only solutions I've found online involved setting up custom tasks per build target and even then they sounded like it didn't really work 100%. Is there really nothing built in (and enabled by default) that writes the build log to disk, even as a temporary file?
----------------------------------------
I tried the AI suggestion of adding "-o=-j1" as an extra CMake argument in the build configuration but it appears to not do anything (hallucination? ignored?)
