Re: Package for development of out-of-tree kernel modules written in Rust
On Fri, Apr 4, 2025 at 11:00 AM Bastian Blank <waldi@debian.org> wrote:
>
> C macros are read by the preprocessor shipped in the compiler. The
> preprocessor changes it's behaviour depending on the input files.
> However you don't recompile the preprocessor depending on the kernel
> config.
I am aware of how C macros are traditionally handled, thank you, but
that is not what I was asking. My question was in relation to yours:
What the heck is this good for, where config dependency would be useful?
It is pretty easy to see why it would be useful -- for instance, we
would have less (and thus more readable) generated code, as well as
faster macros too.
> The root issue is: libmacros.so, the output file, must be independent
> from the kernel config.
That is not the root issue. That is a constraint you have.
And I don't see why you say it is a "must" -- we could have a way to
rebuild the required proc macros that out-of-tree modules need on the
fly, for instance, if we end up supporting that use case.
Cheers,
Miguel
Reply to: