6317642ce6
This is done in order to detect if user wants to build spdk RPMs against DPDK RPMs that might have been installed on the system. This boils down to the following: - if --with-dpdk, with no argument, is detected don't build separate RPM holding DPDK libs since user in this case is most likely interested only in packaging the SPDK so it can coexist with separate DPDK packaging workflow - define install and build requirements for the SPDK RPMs to depend on dpdk-devel RPM Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: I4dd587009da282a114524c74d833fd35ebc5b985 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/8349 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> |
||
|---|---|---|
| .. | ||
| rpm-deps.sh | ||
| rpm.sh | ||
| spdk.spec | ||