> -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Wednesday, May 20, 2015 4:05 PM > To: Richardson, Bruce > Cc: dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH v2 02/19] drivers: create drivers and > drivers/net directory > > 2015-05-15 16:56, Bruce Richardson: > > Add a new top-level "drivers" directory to which all PMDs will be > > moved for easier maintenance of both lib folder and drivers > > themselves. This new directory is a dependency of all the apps in the > > app folder, so the makefiles for each app are updated. > > Why drivers are a dependency of every apps? > Some of them don't even include rte_ethdev.h.
Good point. I just got a broken build initially in the apps with missing dependencies, so I made the change so that dependencies were the same as before. Looking at things, I imagine test-pmd and test-pipeline depend upon the drivers since they do packet IO, and the test app will depend on it as it has unit tests for the bond-ethdev driver. Dump-cfg and the test-acl app should not have a dependency on the driver, I imagine. It appears that the cmdline-test app is missing a DEPDIRS-y line, but it probably should depend on the libs, right? /Bruce