dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Olivier MATZ <olivier.matz-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Daniel Kan <dan-nm7580oGLDTQT0dZR+AlfA@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: Any benefit of using DPDK's makefiles instead of using your own and linking against DPDK library
Date: Thu, 16 Jan 2014 15:02:00 +0100	[thread overview]
Message-ID: <52D7E658.7050403@6wind.com> (raw)
In-Reply-To: <BF63A365-B8BD-49CD-9DCE-09D7A47DED02-nm7580oGLDTQT0dZR+AlfA@public.gmane.org>

Hi Dan,

On 01/14/2014 09:40 PM, Daniel Kan wrote:
> 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?

I guess it's because in case of local compilation (called "native"),
these flags can be generated dynamically in mk/rte.toolchain-compat.mk
from gcc or icc compiler version and from the CPUFLAGS variable
(see machine/native/rte.vars.mk).

You can also check this older thread:
http://dpdk.org/ml/archives/dev/2014-January/001053.html

Regards,
Olivier

      parent reply	other threads:[~2014-01-16 14:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  7:02 Any benefit of using DPDK's makefiles instead of using your own and linking against DPDK library Daniel Kan
     [not found] ` <8A452F53-AD44-4C3C-8AB0-AD3342206D46-nm7580oGLDTQT0dZR+AlfA@public.gmane.org>
2014-01-14 11:38   ` Thomas Monjalon
     [not found]     ` <201401141238.30056.thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-01-14 13:22       ` Venkatesan, Venky
     [not found]         ` <1FD9B82B8BF2CF418D9A1000154491D973FC5A42-P5GAC/sN6hlcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-01-14 13:55           ` Thomas Monjalon
     [not found]             ` <201401141455.57994.thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-01-14 15:06               ` Hamid Ramazani
2014-01-14 20:40               ` Daniel Kan
     [not found]                 ` <BF63A365-B8BD-49CD-9DCE-09D7A47DED02-nm7580oGLDTQT0dZR+AlfA@public.gmane.org>
2014-01-16 14:02                   ` Olivier MATZ [this message]

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=52D7E658.7050403@6wind.com \
    --to=olivier.matz-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=dan-nm7580oGLDTQT0dZR+AlfA@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    /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).