[dpdk-dev] Any benefit of using DPDK's makefiles instead of using your own and linking against DPDK library
dan at nyansa.com
Tue Jan 14 21:40:04 CET 2014
I think in general, developers are pretty particular about their makefiles and build framework. This is especially true if you have an existing application; migrating it to use dpdk’s build framework is rather cumbersome and likely a non-starter for bigger complex projects. Hence, separating application build from dpdk build will be very useful in many situations. The main trick is to extract the appropriate compilation flags that can be readily consumed by the application build system. As an application developer, nothing is simper than just having some header files, a library file, and some necessary compilation flags. If tools like pkg-config or others can facilitate that process, then we could consider it. But even a simple script that can be give me flags that I can provide to my own build system would already suffice.
On a similar note, is there any particular reason why many macros such as RTE_MACHINE_XXX are passed as flags to the compiler instead of being defined in rte_config.h?
On Jan 14, 2014, at 5:55 AM, Thomas Monjalon <thomas.monjalon at 6wind.com> wrote:
> Hello Venky,
> 14/01/2014 14:22, Venkatesan, Venky:
>> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Thomas Monjalon
>>> 14/01/2014 08:02, Daniel Kan:
>>>> I already have existing makefiles for my current application. I would
>>>> like to integrate dpdk into the application. ’m wondering if there is
>>>> any benefit to use dpdk’s makefiles instead of using your own makefile
>>>> and linking against the library (e.g. libintel_dpdk.a). Thanks.
>>> DPDK makefiles have 2 benefits:
>>> - provide a framework
>>> - automatically set CFLAGS and LDFLAGS according to your configuration
>>> If you don't need a framework, I think it's better to extract compilation
>>> flags with something like pkg-config.
>>> A patch for a such feature would be welcome :)
>> One other thing to think about - as we add more functionality into DPDK
>> (e.g. new libraries for other packet functions), we integrate them into
>> the DPDK framework. If you extract compilation flags and setup your own
>> makefile, you would have to do this re-integration every time you want to
>> pick up a new release. The same applies to newer files added etc. etc.
>> That is the downside.
> I disagree.
> If the Makefile of the application, use a DPDK script or pkg-config to read
> the flags from a generated file, the integration is done only once.
> This guide explains the logic and how to implement it:
More information about the dev