Hi Stephen, I am building the dpdk-simple_mp example in meson/ninja. Our application is built in our custom build environment, and we are not using DPDK shared libraries, but are linking to DPDK static libs.
Thanks, Ed -----Original Message----- From: Stephen Hemminger <step...@networkplumber.org> Sent: Tuesday, March 25, 2025 6:20 PM To: Lombardo, Ed <ed.lomba...@netscout.com> Cc: Kompella V, Purnima <kompella.purn...@commscope.com>; users@dpdk.org Subject: Re: tailqs issue External Email: This message originated outside of NETSCOUT. Do not click links or open attachments unless you recognize the sender and know the content is safe. On Tue, 25 Mar 2025 14:39:08 +0000 "Lombardo, Ed" <ed.lomba...@netscout.com> wrote: > Hi Purnima, > I will try your suggestion, but this seems weird. What if I have a 3rd party > application that I want to integrate with our application. This could be > impossible to coordinate this requirement. > > Thanks, > Ed Primary and secondary are tightly coupled. They have to be built from same base, so true 3rd party support would be very difficult. How are you building? Using meson and DPDK process or something custom? I seem to remember there was a issue long ago with shared libraries and build flags where initializers would not get run unless a flag was passed during the shared library link step.