Hi Sergio, 2015-01-12 16:33, Sergio Gonzalez Monroy: > This patch series updates the DPDK build system.
Thanks for proposing such rework. We need discussions on that topic. So I ask some questions below. > Following are the goals it tries to accomplish: > - Create a library containing core DPDK libraries (librte_eal, > librte_malloc, librte_mempool, librte_mbuf and librte_ring). > The idea of core libraries is to group those libraries that are > always required for any DPDK application. How is it better? Is it only to reduce dependencies lines? > - Remove config option to build a combined library. Why removing combined library? Is there people finding it helpful? > - For shared libraries, explicitly link against dependant > libraries (adding entries to DT_NEEDED). OK, good. > - Update app linking flags against static/shared DPDK libs. > > Note that this patch turns up being quite big because of moving lib > directories to a new subdirectory. > I have ommited the actual diff from the patch doing the move of librte_eal > as it is quite big (6MB). Probably a different approach is preferred. Why do you think moving directories is needed? Thanks -- Thomas
