With this change, I am able to make -j32 the entire project successfully (which greatly speeds up the build process).
The reason the Makefile isn't parallelizable is that both the linux and windows targets write their .o files to the same directory, causing the linker to try to link ELF64 and PE32 binaries together, which it can't do. The Makefile would need to be restructured so that build output goes to two different places for this Makefile to be parallelizable, but that feels like an unnecessary amount of work given how little improvement parallelizing this Makefile would provide (compared to being able to compile the whole thing with -j now).
With this change, I am able to
make -j32the entire project successfully (which greatly speeds up the build process).The reason the Makefile isn't parallelizable is that both the
linuxandwindowstargets write their.ofiles to the same directory, causing the linker to try to link ELF64 and PE32 binaries together, which it can't do. The Makefile would need to be restructured so that build output goes to two different places for this Makefile to be parallelizable, but that feels like an unnecessary amount of work given how little improvement parallelizing this Makefile would provide (compared to being able to compile the whole thing with-jnow).