Hi. Thanks for the patch. I faced this issue few weeks ago trying to build OVS with DPDK built by meson. However, your patch doesn't fix my case.
You're exporting "PKG_CONFIG_PATH=$with_dpdk/build/meson-private/" assuming that '$with_dpdk/build' is a meson build directory. But it's not true in most cases. More likely that '$with_dpdk' is a custom installation directory created by 'ninja install' with a custom DESTDIR. And it has completely different structure. For example, after execution of the following command: DESTDIR=`pwd`/dpdk_meson_install ninja install pkgconfig file will be placed in: `pwd`/dpdk_meson_install/usr/local/lib/x86_64-linux-gnu/pkgconfig and the path will be different with different architectures and, probably, options passed to ninja. There is no 'meson-private' directory in this case. Also, your code will fail if you'll use 'meson mybuild' instead of 'meson build'. 'build' is just a name and it's not fixed. For example, I'm using different names for different configs/archs. Like 'meson arm-build', 'meson normal-build'. Best regards, Ilya Maximets. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
