I currently provide automated nightly builds of the icestorm toolchain, and I am finally getting around to upstreaming the horrible ugly build system hacks that I've been using. One issue I have with the way arachne-pnr's build system is currently set up is that it does not work well with cross-compiling. Specifically, the build system generates binary chipdb files by executing the just-built arachne-pnr binary. This cannot work if the just-built binary isn't built for the same architecture as the host system. I noticed that the Windows target has a completely different makefile path to deal with this problem. Is it possible to make cross-compiling work better and make Windows less of a special case?
I currently provide automated nightly builds of the icestorm toolchain, and I am finally getting around to upstreaming the horrible ugly build system hacks that I've been using. One issue I have with the way arachne-pnr's build system is currently set up is that it does not work well with cross-compiling. Specifically, the build system generates binary chipdb files by executing the just-built arachne-pnr binary. This cannot work if the just-built binary isn't built for the same architecture as the host system. I noticed that the Windows target has a completely different makefile path to deal with this problem. Is it possible to make cross-compiling work better and make Windows less of a special case?