|
Revision tags: v22.03, v22.03-rc4, v22.03-rc3, v22.03-rc2, v22.03-rc1, v21.11, v21.11-rc4, v21.11-rc3, v21.11-rc2, v21.11-rc1, v21.08, v21.08-rc4, v21.08-rc3, v21.08-rc2, v21.08-rc1, v21.05, v21.05-rc4, v21.05-rc3, v21.05-rc2 |
|
| #
11e02702 |
| 05-May-2021 |
Jerin Jacob <[email protected]> |
examples: fix pkg-config override
Move pkg-config override to beginning in the Makefile to allow use PKGCONF variable to detect the libdpdk availability.
Fixes: fda34680eb9a ("examples: remove lega
examples: fix pkg-config override
Move pkg-config override to beginning in the Makefile to allow use PKGCONF variable to detect the libdpdk availability.
Fixes: fda34680eb9a ("examples: remove legacy sections of makefiles") Cc: [email protected]
Signed-off-by: Jerin Jacob <[email protected]> Acked-by: Bruce Richardson <[email protected]>
show more ...
|
|
Revision tags: v21.05-rc1, v21.02, v21.02-rc4, v21.02-rc3, v21.02-rc2, v21.02-rc1 |
|
| #
5a196330 |
| 19-Jan-2021 |
Bruce Richardson <[email protected]> |
examples: warn about broken pkg-config
Since the examples are designed to be built by end-users using Make, we can detect and warn about broken pkg-config on the user's system as part of the build p
examples: warn about broken pkg-config
Since the examples are designed to be built by end-users using Make, we can detect and warn about broken pkg-config on the user's system as part of the build process.
Signed-off-by: Bruce Richardson <[email protected]>
show more ...
|
|
Revision tags: v20.11, v20.11-rc5, v20.11-rc4, v20.11-rc3, v20.11-rc2, v20.11-rc1 |
|
| #
fda34680 |
| 03-Sep-2020 |
Ciara Power <[email protected]> |
examples: remove legacy sections of makefiles
The example app makefiles contained sections using the legacy method of compiling with make. These are no longer needed, and are removed, leaving only t
examples: remove legacy sections of makefiles
The example app makefiles contained sections using the legacy method of compiling with make. These are no longer needed, and are removed, leaving only the section that uses pkg-config for the make build.
Signed-off-by: Ciara Power <[email protected]> Acked-by: Nicolas Chautru <[email protected]>
show more ...
|
|
Revision tags: v20.08, v20.08-rc4, v20.08-rc3, v20.08-rc2, v20.08-rc1 |
|
| #
8549295d |
| 30-Jun-2020 |
Bruce Richardson <[email protected]> |
build/pkg-config: improve static linking flags
Rather than setting -Bstatic in the linker flags when doing a static link, and then having to explicitly set -Bdynamic again afterwards, we can update
build/pkg-config: improve static linking flags
Rather than setting -Bstatic in the linker flags when doing a static link, and then having to explicitly set -Bdynamic again afterwards, we can update the pkg-config file to use -l:libfoo.a syntax to explicitly refer to the static library in question. Since this syntax is not supported by meson's pkg-config module directly, we can post-process the .pc files instead to adjust them.
Once done, we can simplify the examples' makefiles and the docs by removing the explicit static flag.
Signed-off-by: Bruce Richardson <[email protected]> Acked-by: Luca Boccassi <[email protected]> Acked-by: Sunil Pai G <[email protected]> Signed-off-by: Thomas Monjalon <[email protected]>
show more ...
|
|
Revision tags: v20.05, v20.05-rc4, v20.05-rc3, v20.05-rc2, v20.05-rc1, v20.02, v20.02-rc4, v20.02-rc3, v20.02-rc2, v20.02-rc1, v19.11, v19.11-rc4, v19.11-rc3 |
|
| #
69b1bb49 |
| 15-Nov-2019 |
Bruce Richardson <[email protected]> |
examples: hide error for missing pkg-config path flag
Some versions of pkg-config don't support the --path flag, which is not a fatal error when building the apps. Without the flag, the makefile jus
examples: hide error for missing pkg-config path flag
Some versions of pkg-config don't support the --path flag, which is not a fatal error when building the apps. Without the flag, the makefile just cannot track the .pc file of DPDK as a dependency of the build. Therefore, we can ignore the error and suppress it by redirecting to /dev/null the stderr from that call to pkg-config.
Fixes: 22119c4591a0 ("examples: use pkg-config in makefiles") Cc: [email protected]
Signed-off-by: Bruce Richardson <[email protected]> Tested-by: Ferruh Yigit <[email protected]>
show more ...
|
| #
12a652a0 |
| 15-Nov-2019 |
Bruce Richardson <[email protected]> |
examples: fix build with old pkg-config
Not all versions of pkg-config in distros have support for the --define-prefix flag [1], causing errors when building examples manually or with test-meson-bui
examples: fix build with old pkg-config
Not all versions of pkg-config in distros have support for the --define-prefix flag [1], causing errors when building examples manually or with test-meson-builds.sh script [2].
For the former case, we need to remove the hard-coded use of the flag in the Makefiles.
For the latter case, the flag is necessary for builds to succeed, so we skip the tests when it's not present, passing it as part of the pkg-config command if it is supported.
[1] CentOS Linux release 7.7.1908 (Core) pkg-config version 0.27.1
[2] ## Building cmdline Unknown option --define-prefix gmake: Entering directory `...ild-x86-default/install-root/usr/local/share/dpdk/examples/cmdline' rm -f build/cmdline build/cmdline-static build/cmdline-shared test -d build && rmdir -p build || true Unknown option --define-prefix Unknown option --define-prefix gcc -O3 main.c commands.c parse_obj_list.c -o build/cmdline-shared main.c:14:28: fatal error: cmdline_rdline.h: No such file or directory
Fixes: ca9268529d2b ("examples: support relocated DPDK install") Fixes: 7f80a2102bbb ("devtools: test pkg-config file") Cc: [email protected]
Reported-by: Ferruh Yigit <[email protected]> Signed-off-by: Bruce Richardson <[email protected]> Tested-by: Ferruh Yigit <[email protected]>
show more ...
|
|
Revision tags: v19.11-rc2, v19.11-rc1, v19.08, v19.08-rc4, v19.08-rc3, v19.08-rc2, v19.08-rc1 |
|
| #
4131ad5d |
| 03-Jul-2019 |
Bruce Richardson <[email protected]> |
examples: fix pkg-config detection with older make
Make versions before 4.2 did not have support for the .SHELLSTATUS variable, so use another method to detect shell success.
Fixes: 22119c4591a0 ("
examples: fix pkg-config detection with older make
Make versions before 4.2 did not have support for the .SHELLSTATUS variable, so use another method to detect shell success.
Fixes: 22119c4591a0 ("examples: use pkg-config in makefiles") Cc: [email protected]
Signed-off-by: Bruce Richardson <[email protected]> Acked-by: Luca Boccassi <[email protected]>
show more ...
|
| #
f3558ec2 |
| 02-Jul-2019 |
Bruce Richardson <[email protected]> |
examples/vdpa: support build with pkg-config
The vdpa example app did not check for a libdpdk pkg-config file and attempt to build using that. Add support for that method of compile to align the app
examples/vdpa: support build with pkg-config
The vdpa example app did not check for a libdpdk pkg-config file and attempt to build using that. Add support for that method of compile to align the app with the other examples.
Signed-off-by: Bruce Richardson <[email protected]> Acked-by: Luca Boccassi <[email protected]>
show more ...
|
| #
0e34bced |
| 17-Jun-2019 |
David Marchand <[email protected]> |
examples/vdpa: remove trace of legacy linuxapp
This check on Linux environment has been added at a time when we already had switched to using the boolean RTE_EXEC_ENV_LINUXAPP. It was then missed wh
examples/vdpa: remove trace of legacy linuxapp
This check on Linux environment has been added at a time when we already had switched to using the boolean RTE_EXEC_ENV_LINUXAPP. It was then missed when converting to RTE_EXEC_ENV_LINUX.
Fixes: edbed86d1cc3 ("examples/vdpa: introduce a new sample for vDPA") Fixes: 742bde12f3bd ("build/linux: rename macro from LINUXAPP to LINUX") Cc: [email protected]
Signed-off-by: David Marchand <[email protected]> Reviewed-by: Tiwei Bie <[email protected]> Reviewed-by: Xiaolong Ye <[email protected]>
show more ...
|
|
Revision tags: v19.05, v19.05-rc4, v19.05-rc3, v19.05-rc2, v19.05-rc1 |
|
| #
e9c65942 |
| 27-Mar-2019 |
Bruce Richardson <[email protected]> |
examples: detect default build directory
Most examples have in their makefiles a default RTE_TARGET directory to be used in case RTE_TARGET is not set. Rather than just using a hard-coded default, w
examples: detect default build directory
Most examples have in their makefiles a default RTE_TARGET directory to be used in case RTE_TARGET is not set. Rather than just using a hard-coded default, we can instead detect what the build directory is relative to RTE_SDK directory.
This fixes a potential issue for anyone who continues to build using "make install T=x86_64-native-linuxapp-gcc" and skips setting RTE_TARGET explicitly, instead relying on the fact that they were building in a directory which corresponded to the example default path - which was changed to "x86_64-native-linux-gcc" by commit 218c4e68c1d9 ("mk: use linux and freebsd in config names").
Signed-off-by: Bruce Richardson <[email protected]> Acked-by: Ferruh Yigit <[email protected]>
show more ...
|
| #
218c4e68 |
| 06-Mar-2019 |
Bruce Richardson <[email protected]> |
mk: use linux and freebsd in config names
Rather than using linuxapp and bsdapp everywhere, we can change things to use the, more readable, terms "linux" and "freebsd" in our build configs. Rather t
mk: use linux and freebsd in config names
Rather than using linuxapp and bsdapp everywhere, we can change things to use the, more readable, terms "linux" and "freebsd" in our build configs. Rather than renaming the configs we can just duplicate the existing ones with the new names using symlinks, and use the new names exclusively internally. ["make showconfigs" also only shows the new names to keep the list short] The result is that backward compatibility is kept fully but any new builds or development can be done using the newer names, i.e. both "make config T=x86_64-native-linuxapp-gcc" and "T=x86_64-native-linux-gcc" work.
Signed-off-by: Bruce Richardson <[email protected]>
show more ...
|
|
Revision tags: v19.02, v19.02-rc4, v19.02-rc3, v19.02-rc2, v19.02-rc1, v18.11, v18.11-rc5, v18.11-rc4, v18.11-rc3, v18.11-rc2, v18.11-rc1 |
|
| #
edbed86d |
| 28-Sep-2018 |
Xiaolong Ye <[email protected]> |
examples/vdpa: introduce a new sample for vDPA
The vdpa sample application creates vhost-user sockets by using the vDPA backend. vDPA stands for vhost Data Path Acceleration which utilizes virtio ri
examples/vdpa: introduce a new sample for vDPA
The vdpa sample application creates vhost-user sockets by using the vDPA backend. vDPA stands for vhost Data Path Acceleration which utilizes virtio ring compatible devices to serve virtio driver directly to enable datapath acceleration. As vDPA driver can help to set up vhost datapath, this application doesn't need to launch dedicated worker threads for vhost enqueue/dequeue operations.
Signed-off-by: Xiaolong Ye <[email protected]> Acked-by: Xiao Wang <[email protected]> Reviewed-by: Maxime Coquelin <[email protected]>
show more ...
|