#221 fixed a link failure that only appeared when cross-compiling to riscv64gc-unknown-linux-gnu and linking a cdylib. Nothing in the CI would have caught this and will avoid a regression.
Per @luisschwab's suggestion in #221, the cross-compilation checks should move into their own workflow file with a matrix over target triples, so triples can be added over time. There's a working reference in luisschwab/bdk-floresta#183.
#221 fixed a link failure that only appeared when cross-compiling to
riscv64gc-unknown-linux-gnuand linking acdylib. Nothing in the CI would have caught this and will avoid a regression.Per @luisschwab's suggestion in #221, the cross-compilation checks should move into their own workflow file with a matrix over target triples, so triples can be added over time. There's a working reference in luisschwab/bdk-floresta#183.