Yes, but please note if anyone comes back to this thread in the future, the exact command changes over time, so make sure to confirm it via the method described above.
No worries, I’m interested in actually digging into ngspice itself (for simulations and tests in XR once the glTF is exported thanks to kicad-cli) so good occasion!
For ref, below full recipe for building on Ubuntu and also Windows Subsystem for Linux (I just tested now on Ubuntu WSL).
Note I wouldn’t recommend WSL building as you’ll probably run into graphical gitches due to WSL as well as slowing it down but it’s fun to build linux on windows.
It looks like the official build instructions have been changed after the last time I have looked at them. Instead of providing lists of dependencies it now refers to nightly packages and their up to date dependency lists which is a good thing.
This way there’s no need to copy/paste/write any dependency list. If the nightly build has been built by someone else already recently, it can be built after running those two commands (unless, of course, the package maintainer has done some mistake).
Because building and linking takes a little while, would it be possible to mention estimations of speed-ups gained by using e.g ninja, or mold? For this process would it become 1% faster? 10%?
I’m not an expert, but first you have to understand that ninja or some other similar build system doesn’t help at the first time build. It’s good for “incremental builds”, i.e. small edit->build cycles. For example, pulling even as often as once a day from the master git branch while development is ongoing results often to almost complete rebuild, and ninja doesn’t probably help much.
The linker has probably more effect. It depends on how many files must be linked. In any case I tried mold and I got a feeling that it reduces the build time considerably – more than changing from pure make to ninja. I have noticed earlier that linking one file may take longer time than compiling.
