DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Venkatesan, Venky" <venky.venkatesan@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Any benefit of using DPDK's makefiles instead of using your own and linking against DPDK library
Date: Tue, 14 Jan 2014 14:55:57 +0100	[thread overview]
Message-ID: <201401141455.57994.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <1FD9B82B8BF2CF418D9A1000154491D973FC5A42@ORSMSX102.amr.corp.intel.com>

Hello Venky,

14/01/2014 14:22, Venkatesan, Venky:
> From: dev [mailto:dev-bounces@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.
> > http://freedesktop.org/wiki/Software/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:
	http://people.freedesktop.org/~dbn/pkg-config-guide.html

-- 
Thomas

  reply	other threads:[~2014-01-14 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  7:02 Daniel Kan
2014-01-14 11:38 ` Thomas Monjalon
2014-01-14 13:22   ` Venkatesan, Venky
2014-01-14 13:55     ` Thomas Monjalon [this message]
2014-01-14 15:06       ` Hamid Ramazani
2014-01-14 20:40       ` Daniel Kan
2014-01-16 14:02         ` Olivier MATZ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201401141455.57994.thomas.monjalon@6wind.com \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=venky.venkatesan@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).