Thread (4 messages) 4 messages, 2 authors, 2015-07-30

Re: how to compile kernel drivers only

flat view

From: Thomas Monjalon <hidden>
Date: 2015-07-30 13:42:21

Francesco, please reply below (easier to follow the thread).

2015-07-30 12:48, Montorsi, Francesco:
From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] 
quoted
2015-07-30 12:17, Montorsi, Francesco:
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help