Hi,

In the codebase of DPDK I saw that it uses the glibc 
approach<https://developers.redhat.com/blog/2019/08/01/how-the-gnu-c-library-handles-backward-compatibility>
 to mangle symbol names with a library version to maintain different 
implementations of the same function per version.
So that applications which were compiled with different versions of the library 
will link to a proper version of the function that corresponds to the right 
glibc (see doc<https://doc.dpdk.org/guides/contributing/abi_versioning.html>).
This method can't work in Windows with MSVC (at least to the best of my 
knowledge).

How does DPDK solve if in Windows for MSVC? I failed to find the answer.

Thank you,
Arseniy Aharonov

Reply via email to