On Sat, Dec 27, 2025 at 01:15:49AM +0900, Simon Richter wrote: > Hi, > > I'm trying to improve the nextpnr packaging a bit. > > This package builds binaries and a database that has been pre-indexed for > faster runtime access. Currently, the database is built together with the > binaries, and packaged as arch-dependent, which is a bit wasteful -- two > copies (little/big endian) would be sufficient here, and not building the > database saves quite a bit of time. > > However, if I build the database as arch-indep, I can no longer run the > tests from dh_auto_test in arch-specific builds, as these depend on the > database, and the database is no longer built then. > > A horrible hack would be to select one architecture (probably amd64) that is > responsible for building the database, and declare a build dependency for > all other architectures if not using the nocheck profile.
What about this: Have one or two new source packages which create new binary packages called for example nextpnr-db-bigendian and nextpnr-db-littleendian, both arch:all so that they can be installed by everybody who needs them, but they can only be built on a compatible autobuilder. Is there a way to express that in the control file? (AFAIK, cross compilers used to use arch:all packages to "transfer" stuff between one architecture and another one, so this would not be a new trick). Thanks.
