On Wed, Oct 14, 2026 at 09:21:53PM +0200, Robin Jarry wrote: > Some libraries are only used either for internal apps/examples (cmdline) > or by a specific mempool driver (stack). > > Everywhere they are used, an explicit dependency is already recorded in > meson. There is no reason to always enable them. > No objection to this, however, I actually have a more complete RFC almost ready to send for the next release, which goes even further than this by doing initial dependency analysis on all components and using that to compute the minimum set to enable. Specifically, if we assume the minimal set is EAL + whatever is needed to build the always needed basic infrastructure drivers, the RFC finishes by computing the lib "always_enable" set as being the dependencies of "bus/pci,bus/vdev,mempool/ring". [As for why that set of minimal drivers - if we omit them, lots of things in DPDK won't function, and we cannot guarantee that any other components selected will depend on them. For example, nothing else depends on mempool/ring so if we want working mempools we have to have it in the enable list]
I'll try and get the RFC out this week to at least get the conversation started in advance of 27.03 opening up. /Bruce
