Closed joakim-hove closed 10 months ago
Nothing obvious springs to mind. Can you share a small repro with instructions to get a reproduction of the issue?
Nothing obvious springs to mind. Can you share a small repro with instructions to get a reproduction of the issue?
Very good - I will create a small project illustrating the issue; might have to wait until tomorrow though.
No rush, it may take me some time to investigate 👍
Thank you for willingness to look into this - that turned out to more-or-less solve the problem. When I made a minimal example to illustrate the problem that actually worked as it should, so now I am well set up to debug this properly.
Bug Description
I have a rust project consisting of two layered crates:
cmsis-dsp:This crate is based on an external C library. The rust crate is mainly just a wrapper around the cmake based build system of the external project.
dsp: This is a normal rust crate which depends on - and extends the cmsis-dsp crate.
Both the
cmsis-dsp
anddsp
crates are compiled with#![no_std]
, whereas the python wrapper will be used on a normal PC withstd
support.The combination of the
cmsis-dsp
anddsp
crates have been used for several months and work nicely. I now want to create Python wrappers for the dsp crate using PyO3. I have created a new cratedsp-python
withmaturin new
and added a minimal code dependency on thedsp
project. When I try to build the newdsp-python
project the cargo build step fails with a linking error.The code is part of a quite large internal project - but if it is interesting I would certainly be happy to create a minimal project to illustrate the problem.
Steps to Reproduce
See bug description
Backtrace