Hi Nilesh again,
I checked, and it seems like 'dh_auto_build' calls 'make' with the default target. (I get the same result if I explicitly add ad 'override_dh_auto_build' target.) However, if instead I override the 'dh_auto_test' target to do nothing, then the tests aren't being run at all during the package build phase.
So, it seems like all is good there. The tests are run only when dh explicitly wants to run them.
-- Attila.
Hi Nilesh,
Uhm. Unless I am mistaken, make will run the "make all" rule and in the all rule in your makefile, you've specified "test coverage" etc as seen here[2]. This will hence run at build time, and not just dh_auto_test.Well, if 'dh_auto_build' runs 'make all' (and not simply 'make' with the default target), then this can be easily fixed by providing an override rule that simply calls 'make' (or the equivalent 'make distro') in debian/rules. I'm happy to make the change if you agree.
It will be provided by the native build -- there should be no issue there as such. As such, I don't think it is possible to exclude selected binary packages from cross-compiling, but I might need to think a bit more here.If, as you say, the aarch64 packages are provided by native builds, then there is no issue with the cio_ra.bin file (and the 'supernovas-cio-data' sub-package that provides it). It's only the cross-build setup that cannot produce these.
cheers,
-- A.