Unless I misunderstood the last status of this issue was that it was desired empty stubs that fail at runtime as opposed to conditionally generating exports.
Is this no longer the case? -----Original Message----- From: Thomas Monjalon <[email protected]> Sent: Friday, March 26, 2021 1:40 AM To: Dmitry Kozlyuk <[email protected]>; ranjit.menon <[email protected]>; Kadam, Pallavi <[email protected]>; Harini Ramakrishnan <[email protected]>; [email protected]; Dmitry Malloy <[email protected]> Cc: [email protected]; talshn <[email protected]>; [email protected]; David Marchand <[email protected]>; Tyler Retzlaff <[email protected]>; Omar Cardona <[email protected]> Subject: [EXTERNAL] Re: [dpdk-dev] Handling missing export functions in MSVC linkage 08/06/2020 10:33, David Marchand: > On Mon, Jun 8, 2020 at 2:09 AM Dmitry Kozlyuk <[email protected]> > wrote: > > On Sun, 7 Jun 2020 12:26:56 +0000 > > If you create a .def manually, it will override the generation from > > .map. Of cause, this adds manual work and ideally all .def files should be > > generated. > > On this topic, I just noticed that a patch of mine, that removed > rte_eal_get_configuration() from the stable ABI, missed the > declaration in rte_eal_exports.def. > Probably worth adding a check in devtools/, to avoid further misalignment. The .def file keeps being out of sync. We need a script to avoid forgetting the sync, or/and we must generate this .def from the .map. Ideally the full EAL API (except VFIO) should be implemented for Windows. This situation is waiting for a solution for too much time. Windows maintainers, please solve it.
