[PATCH] examples/pipeline: fix include path for rte_log.h

Dumitrescu, Cristian cristian.dumitrescu at intel.com
Tue Feb 13 18:22:14 CET 2024


Hi David,

> -----Original Message-----
> From: David Marchand <david.marchand at redhat.com>
> Sent: Tuesday, February 13, 2024 4:19 PM
> To: Dumitrescu, Cristian <cristian.dumitrescu at intel.com>
> Cc: dev at dpdk.org; stable at dpdk.org
> Subject: Re: [PATCH] examples/pipeline: fix include path for rte_log.h
> 
> 
> Wrt $Subject, copy/paste code in drivers/net/softnic is broken too.

You're right, let me fix this in V2.

> 
> Some comments on this code:
> - putting compilation commands seems a rather strange idea in C code,
> but at least, why not invoke an external tool/script that makes use of
> existing build framework?

Yes, I am thinking of transitioning the pipeline app from the examples
folder to the apps folder, as it is way more than an example at this point,
and also add a script/tool to generate the C code in a more configurable
way. For now, the examples/pipeline contains just the default way to do
this, but of course a standalone tool would be better. On my ToDo list.
Thanks for providing this input!

> - RTE_INSTALL_DIR is undocumented,

This option is not supposed to be broadly used, but it is there just in case.
When the tool mentioned above will be ready, this will be moved into that
tool.

> - this implementation (passing -I <some_directory>/lib/eal/include) is
> broken with a system-installed dpdk,

Yes, this is expected. For the purpose of the pipeline C code generation,
we need the path to the full DPDK folder, not just the public header files.
There is one internal DPDK internal header file (rte_pipeline_internal.h)
which is needed for code generation purposes, but it should not be
made a public header, as it does not contain the pipeline API that apps
are using.

> 
 
> --
> David Marchand

Regard,
Cristian


More information about the stable mailing list