On 03.07.2017 13:34, Savolainen, Petri (Nokia - FI/Espoo) wrote: >> diff --git a/test/Makefile.inc b/test/Makefile.inc >> index 1ef2a92c..bf31b374 100644 >> --- a/test/Makefile.inc >> +++ b/test/Makefile.inc >> @@ -4,7 +4,7 @@ LIB = $(top_builddir)/lib >> #in the following line, the libs using the symbols should come before >> #the libs containing them! The includer is given a chance to add things >> #before libodp by setting PRE_LDADD before the inclusion. >> -LDADD = $(PRE_LDADD) $(LIB)/libodphelper.la $(LIB)/libodp-linux.la >> +LDADD = $(PRE_LDADD) $(LIB)/libodphelper.la $(LIB)/libodp-linux.la >> $(DPDK_PMDS) > > Application using ODP should only need to add dependency to ODP and helper > libs. It's not scalable if (all) applications need to know which (all) libs > an ODP implementation may use internally. > > I guess this solves some DPDK linking issues, but is there a way to avoid > explicit dependency to ODP lib internals ?
Just to rephrase/emphasize my answer: user applications will use pkg-config file, which contains all necessary data to link with DPDK w/o mentioning it specifically. The only issue is internal linking inside ODP or linking using libtool. -- With best wishes Dmitry
