06/03/2021 01:04, Dmitry Kozlyuk: > DPDK code often relies on functions that are not standard C, > but are found on all platforms, even if by slightly different names. > Some headers provide macros or inline difinitions for such symbols. > However, when placed in public headers, these symbols are unnecessarily > exposed to DPDK consumers. > > Define RTE_BUILD_INTERNAL at build time. > In its presense public headers can provide additional definitions > for internal code, but hide them from external consumers.
Is there a way to split public and internal headers, and avoid playing with RTE_BUILD_INTERNAL?
