From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Montorsi, Francesco" <fmontorsi@empirix.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] how to compile kernel drivers only
Date: Thu, 30 Jul 2015 15:41:05 +0200 [thread overview]
Message-ID: <2025124.I4vGd0nnt1@xps13> (raw)
In-Reply-To: <3de835af894c404992e45f26bb3e0dd1@bilemail1.empirix.com>
Francesco, please reply below (easier to follow the thread).
2015-07-30 12:48, Montorsi, Francesco:
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > 2015-07-30 12:17, Montorsi, Francesco:
> > > How can I avoid building any app like dump_cfg?
> >
> > In app/Makefile, you'll find the options to disable:
> > DIRS-$(CONFIG_RTE_APP_TEST) += test
> > DIRS-$(CONFIG_RTE_LIBRTE_ACL) += test-acl
> > DIRS-$(CONFIG_RTE_LIBRTE_PIPELINE) += test-pipeline
> > DIRS-$(CONFIG_RTE_TEST_PMD) += test-pmd
> > DIRS-$(CONFIG_RTE_LIBRTE_CMDLINE) += cmdline_test
> > DIRS-$(CONFIG_RTE_LIBRTE_EAL_LINUXAPP) += proc_info
>
> My problem is that I have in app/Makefile:
>
> DIRS-$(CONFIG_RTE_LIBRTE_EAL_LINUXAPP) += dump_cfg
>
> So that I should put
>
> CONFIG_RTE_LIBRTE_EAL_LINUXAPP=n
>
> To disable dump_cfg application build. However, If I do so, the kernel drivers are not built at all and make just says:
>
> make T=x86_64-native-linuxapp-gcc O=x86_64-native-linuxapp-gcc EXTRA_LDFLAGS="" --directory=dpdk-2.0.0 all
> make[1]: Entering directory `/home/hammer/share/CSA-Hamachi-Sprint/HW-Accel/drivers/dpdk/dpdk-2.0.0'
> == Build lib
> == Build lib/librte_compat
> SYMLINK-FILE include/rte_compat.h
> == Build lib/librte_eal
> == Build app
> Build complete
>
> So that
> CONFIG_RTE_LIBRTE_EAL_LINUXAPP=y
> Seems to be a pre-requisite of kernel drivers... or am I missing something?
You're right. You cannot build only kernel drivers.
You are welcome to add a new config option to enable/disable apps.
prev parent reply other threads:[~2015-07-30 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 12:17 Montorsi, Francesco
2015-07-30 12:23 ` Thomas Monjalon
2015-07-30 12:48 ` Montorsi, Francesco
2015-07-30 13:41 ` Thomas Monjalon [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=2025124.I4vGd0nnt1@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=fmontorsi@empirix.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).