Re: Package for development of out-of-tree kernel modules written in Rust

[Miguel Ojeda]

On Wed, Feb 26, 2025 at 3:15 PM NoisyCoil <noisyc...@disroot.org> wrote:
>
> Yeah I'd imagined this could happen. Currently d/rules just copies
> rust/{*.rmeta,*.so} into the destination directory. My guess was that in
> the future they could be placed in subdirectories of rust/, but on a
> second thought I think as subsystems accept Rust they could be located
> kind of anywhere in the build directory? If this is the case, then I

Unknown yet -- my current plan is to propose to generate them all in a
single place (which may be different than their current place) for
simplicity. But if people disagree, I may have to place them all over
the tree.

> think hardcoding can hardly be avoided. One will just have to change the
> hardcoded paths as needed (not ideal, but oh, well; also, absolutely not
> unheard of :-)). I say this mostly because of the *.so files: assuming
> that all *.rmeta files must be installed probably is a good enough
> assumption, but the same is not true for *.so files.

If a single place is better for you, that is another argument that I
can use to push for the thing I mentioned above, so I wouldn't mind to
hear that! :)

> On the other hand, one could maybe use something like `objdump -T
> whatever.so | grep rustc_proc_macro_decls` to discover if a .so file is
> a rust proc macro?

In the case where we are everywhere, I guess I could output a file
easily with the paths of all the needed dependencies, if that would
help.

Thanks for the feedback!

Cheers,
Miguel