From: Olivier MATZ <olivier.matz@6wind.com>
To: Daniel Kan <dan@nyansa.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: 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@nyansa.com>
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
prev parent reply other threads:[~2014-01-16 13:57 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
2014-01-14 15:06 ` Hamid Ramazani
2014-01-14 20:40 ` Daniel Kan
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@6wind.com \
--cc=dan@nyansa.com \
--cc=dev@dpdk.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).