Closed plaes closed 4 weeks ago
As I recall, the issue is that cargo publish
wants all inputs to the build to be under the directory of the package. We want to be able to publish these packages on crates.io eventually, so that is important. If there is a way to use a common third_party directory and use it from both packages, that would be great.
Let's close for now as this is something that depends on unimplemented feature from Cargo.
At least in current main, we have two sets of same submodules:
51f8f89612c8330c0116479cfe3a2cb04c390e2b nrf-mpsl-sys/third_party/arm/CMSIS_5 (5.9.0-dev-172-g51f8f8961)
075e9e711383bb3babfae4249fd59c8c8d882f72 nrf-mpsl-sys/third_party/nordic/nrfx (v3.6.0)
37e2ac22b6a6d9d9a62c95e8dc2c102d4371c62e nrf-mpsl-sys/third_party/nordic/nrfxlib (v2.7.0)
51f8f89612c8330c0116479cfe3a2cb04c390e2b nrf-sdc-sys/third_party/arm/CMSIS_5 (5.9.0-dev-172-g51f8f8961)
075e9e711383bb3babfae4249fd59c8c8d882f72 nrf-sdc-sys/third_party/nordic/nrfx (v3.6.0)
37e2ac22b6a6d9d9a62c95e8dc2c102d4371c62e nrf-sdc-sys/third_party/nordic/nrfxlib (v2.7.0)
Would it be feasible to use single set?