ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
3884539699
Spdk/rpmbuild/spdk.spec

166 lines
4.3 KiB
RPMSpec
Raw Normal View History

rpmbuild: Fix Requires section This particular section must be defined in one place hence the %{requirements_list} cannot be passed down later on. This requires reordering of the .spec a bit. Most notably, all global macros are now defined at the very beginning so then Requires section can be build properly. Also, use %() to expand the macro which holds the requirements as bare "Requires: %{foo}" is not valid. Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: I69430f73d10204325fc825ecc392506f261ebaf1 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/8347 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2021-06-15 16:57:36 +00:00
# Global macros
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
%define debug_package %{nil}
%{!?deps:%define deps 1}
%{!?dpdk:%define dpdk 0}
%{!?dpdk_build_path:%define dpdk_build_path "dpdk/build"}
%{!?dpdk_path:%define dpdk_path "dpdk"}
%{!?requirements:%define requirements 0}
rpmbuild: Handle bare --with-dpdk argument 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>
2021-06-15 17:04:38 +00:00
%{!?build_requirements:%define build_requirements 0}
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
%{!?shared:%define shared 0}
configure: Allow to define custom libdir location This is done mainly to align the final location with the one listed in the .pc files created for each lib. Signed-off-by: Michal Berger <michallinuxstuff@gmail.com> Change-Id: I99d6875c9e26f8202723dd6d73bd865b6478bcf9 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/12978 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Dong Yi <dongx.yi@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2022-06-08 12:43:12 +00:00
%{!?libdir:%define libdir /usr/local/lib}
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
rpmbuild: Fix Requires section This particular section must be defined in one place hence the %{requirements_list} cannot be passed down later on. This requires reordering of the .spec a bit. Most notably, all global macros are now defined at the very beginning so then Requires section can be build properly. Also, use %() to expand the macro which holds the requirements as bare "Requires: %{foo}" is not valid. Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: I69430f73d10204325fc825ecc392506f261ebaf1 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/8347 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2021-06-15 16:57:36 +00:00
# Spec metadata
Name: spdk
Version: %{version}
Release: %{release}
Summary: Storage Performance Development Kit
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
# This is a minimal set of requirements needed for SPDK apps to run when built with
# default configuration. These are also predetermined by rpmbuild. Extra requirements
# can be defined through a comma-separated list passed via $requirements when building
# the spec.
Requires: glibc
Requires: libaio
Requires: libgcc
Requires: libstdc++
Requires: libuuid
Requires: ncurses-libs
Requires: numactl-libs
Requires: openssl-libs
Requires: zlib
%if %{requirements}
rpmbuild: Fix Requires section This particular section must be defined in one place hence the %{requirements_list} cannot be passed down later on. This requires reordering of the .spec a bit. Most notably, all global macros are now defined at the very beginning so then Requires section can be build properly. Also, use %() to expand the macro which holds the requirements as bare "Requires: %{foo}" is not valid. Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: I69430f73d10204325fc825ecc392506f261ebaf1 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/8347 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2021-06-15 16:57:36 +00:00
Requires: %(echo "%{requirements_list}")
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
%endif
scripts: move python modules to python directory Up until now, importing an SPDK RPC python module was just a matter of `import rpc`. It's fine until there's another module called `rpc` installed on the system, in which case it's impossible to import both of them. Therefore, to avoid this problem, all of the modules were moved to a separate directory under the "spdk" namespace. The decision to move to a location under a separate directory was motivated by the fact that a directory called scripts/spdk would look pretty confusing. Moreover, it should make it also easier to package these scripts as a python package. Other than moving the packages, all of the imports were updated to reflect these changes. Files under python now use relative imports, while those under scripts/ use the "spdk" namespace and have their PYTHONPATH extended with python directory. Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: Ib43dee73921d590a551dd83885e22870e72451cf Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9692 Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2021-09-21 13:21:31 +00:00
BuildRequires: python3-devel
rpmbuild: Handle bare --with-dpdk argument 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>
2021-06-15 17:04:38 +00:00
%if %{build_requirements}
BuildRequires: %(echo "%{build_requirements_list}")
%endif
rpmbuild: Fix Requires section This particular section must be defined in one place hence the %{requirements_list} cannot be passed down later on. This requires reordering of the .spec a bit. Most notably, all global macros are now defined at the very beginning so then Requires section can be build properly. Also, use %() to expand the macro which holds the requirements as bare "Requires: %{foo}" is not valid. Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: I69430f73d10204325fc825ecc392506f261ebaf1 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/8347 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2021-06-15 16:57:36 +00:00
License: BSD
URL: https://spdk.io
Source: spdk-%{version}.tar.gz
%description
The Storage Performance Development Kit (SPDK) provides a set of tools and libraries for
writing high performance, scalable, user-mode storage applications. It achieves high
performance by moving all of the necessary drivers into userspace and operating in a
polled mode instead of relying on interrupts, which avoids kernel context switches and
eliminates interrupt handling overhead.
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
%prep
rpmbuild: Pass $MAKEFLAGS to make {clean,install} This can speed up these commands by passing, .e.g, -j N args as per default defined in rpm.sh. Signed-off-by: Michal Berger <michal.berger@intel.com> Change-Id: Ia64d3c0a0eef18e449e3020f31eaae8dd4caf483 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/14797 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: <sebastian.brzezinka@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by: Krzysztof Karas <krzysztof.karas@intel.com>
2022-09-30 08:46:57 +00:00
make clean %{make} &>/dev/null || :
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
%setup
%build
%if %{deps}
./scripts/pkgdep.sh --docs --pmem --rdma --uring
%endif
# Rely mainly on CONFIG
./configure --disable-unit-tests --disable-tests %{configure}
make %{make}
rpmbuild: Pass $MAKEFLAGS to make {clean,install} This can speed up these commands by passing, .e.g, -j N args as per default defined in rpm.sh. Signed-off-by: Michal Berger <michal.berger@intel.com> Change-Id: Ia64d3c0a0eef18e449e3020f31eaae8dd4caf483 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/14797 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: <sebastian.brzezinka@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by: Krzysztof Karas <krzysztof.karas@intel.com>
2022-09-30 08:46:57 +00:00
make DESTDIR=%{buildroot} install %{make}
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
# Include DPDK libs in case --with-shared is in use.
%if %{dpdk}
mkdir -p %{buildroot}/usr/local/lib/dpdk
cp -a %{dpdk_build_path}/lib/* %{buildroot}/usr/local/lib/dpdk/
# Special case for SPDK_RUN_EXTERNAL_DPDK setup
autobuild: Adjusting crypto build for latest DPDK (21.11) Details of the changes here: https://github.com/dpdk/dpdk/commit/918fd2f1466b0e3b21a033df7012a77a83665582. They mainly target the aesni_mb driver which was moved to ipsec_mb and bump the minimal supported version of the ipsec to v1.0. Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ica3b4fd66684751939159511845eb6ac6f7d5205 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/10003 Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot
2021-10-26 11:55:21 +00:00
[[ -e %{dpdk_path}/intel-ipsec-mb ]] && find %{dpdk_path}/intel-ipsec-mb/ -name '*.so*' -exec cp -a {} %{buildroot}/usr/local/lib/dpdk/ ';'
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
[[ -e %{dpdk_path}/isa-l/build/lib ]] && cp -a %{dpdk_path}/isa-l/build/lib/*.so* %{buildroot}/usr/local/lib/dpdk/
%endif
rpmbuild: Don't copy binaries from build/bin build/examples make install already does that for us - from build/examples some subset of binaries is selected but in the rpm scope it should be enough. Signed-off-by: Michal Berger <michal.berger@intel.com> Change-Id: I3045711fc3daead9c255fc586600abe5796bc783 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/14798 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: <sebastian.brzezinka@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by: Krzysztof Karas <krzysztof.karas@intel.com>
2022-09-30 08:48:59 +00:00
# Try to include extra binaries that were potentially built
docker: Add docker-compose for building basic SPDK containers This suite can be used to deploy containers with the following functionality (more details in README.md): - storage-target - proxy-container - traffic-generator This will run simple fio test as per fio.conf against nvmf controller provided by initiator-container. Similar task can be performed directly from initiator-container as well. Each container includes SPDK installation with most common tools, e.g. rpc.py, available under $PATH. This allows for something like: docker-compose exec storage-target rpc.py nvmf_get_subsystems Note that SPDK environment heavily depends on a running kernel hence all the containers need to be privileged. That said, to make sure containers are not affecting the host too much, some tasks must be done prior running them. This includes: - loading proper kernel modules (like nvme-fabrics, etc.) - allocating hugepages and having at least one hugetlbfs mount available under /dev/hugepages base_build is created as docker multi-stage build. This is done in order to decrease the size of the final image. The SPDK RPMs are built inside a base image and then copied over to the main image (+ fio binary) - this leaves all the dependencies inside the intermediate image instead of the final one. The resulted difference in size may look similar to the following (it may differ depending on the docker version etc.): no multi-stage build: spdk_base == 1.04GB multi-stage build: spdk_base == 261MB Signed-off-by: Michal Berger <michalx.berger@intel.com> Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: I825bd0d0bb4071bd9d44b6a0749c033894899ae0 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9055 Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Monica Kenguva <monica.kenguva@intel.com> Reviewed-by: Xiaodong Liu <xiaodong.liu@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com>
2021-08-03 07:16:49 +00:00
[[ -e build/fio ]] && cp -a build/fio %{buildroot}/usr/local/bin/fio
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
# And some useful setup scripts SPDK uses
mkdir -p %{buildroot}/usr/libexec/spdk
mkdir -p %{buildroot}/etc/bash_completion.d
mkdir -p %{buildroot}/etc/profile.d
mkdir -p %{buildroot}/etc/ld.so.conf.d
scripts: move python modules to python directory Up until now, importing an SPDK RPC python module was just a matter of `import rpc`. It's fine until there's another module called `rpc` installed on the system, in which case it's impossible to import both of them. Therefore, to avoid this problem, all of the modules were moved to a separate directory under the "spdk" namespace. The decision to move to a location under a separate directory was motivated by the fact that a directory called scripts/spdk would look pretty confusing. Moreover, it should make it also easier to package these scripts as a python package. Other than moving the packages, all of the imports were updated to reflect these changes. Files under python now use relative imports, while those under scripts/ use the "spdk" namespace and have their PYTHONPATH extended with python directory. Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: Ib43dee73921d590a551dd83885e22870e72451cf Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9692 Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2021-09-21 13:21:31 +00:00
mkdir -p %{buildroot}%{python3_sitelib}
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
cat <<-EOF > %{buildroot}/etc/ld.so.conf.d/spdk.conf
configure: Allow to define custom libdir location This is done mainly to align the final location with the one listed in the .pc files created for each lib. Signed-off-by: Michal Berger <michallinuxstuff@gmail.com> Change-Id: I99d6875c9e26f8202723dd6d73bd865b6478bcf9 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/12978 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Dong Yi <dongx.yi@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2022-06-08 12:43:12 +00:00
%{libdir}
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
/usr/local/lib/dpdk
EOF
cat <<-'EOF' > %{buildroot}/etc/profile.d/spdk_path.sh
PATH=$PATH:/usr/libexec/spdk/scripts
PATH=$PATH:/usr/libexec/spdk/scripts/vagrant
PATH=$PATH:/usr/libexec/spdk/test/common/config
export PATH
EOF
cp -a scripts %{buildroot}/usr/libexec/spdk/scripts
scripts: move python modules to python directory Up until now, importing an SPDK RPC python module was just a matter of `import rpc`. It's fine until there's another module called `rpc` installed on the system, in which case it's impossible to import both of them. Therefore, to avoid this problem, all of the modules were moved to a separate directory under the "spdk" namespace. The decision to move to a location under a separate directory was motivated by the fact that a directory called scripts/spdk would look pretty confusing. Moreover, it should make it also easier to package these scripts as a python package. Other than moving the packages, all of the imports were updated to reflect these changes. Files under python now use relative imports, while those under scripts/ use the "spdk" namespace and have their PYTHONPATH extended with python directory. Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: Ib43dee73921d590a551dd83885e22870e72451cf Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9692 Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2021-09-21 13:21:31 +00:00
cp -a python/spdk %{buildroot}%{python3_sitelib}
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
ln -s /usr/libexec/spdk/scripts/bash-completion/spdk %{buildroot}/etc/bash_completion.d/
# We need to take into the account the fact that most of the scripts depend on being
# run directly from the repo. To workaround it, create common root space under dir
# like /usr/libexec/spdk and link all potential relative paths the script may try
# to reference.
# setup.sh uses pci_ids.h
ln -s /usr/local/include %{buildroot}/usr/libexec/spdk
%files
/etc/profile.d/*
/etc/bash_completion.d/*
/usr/libexec/spdk/*
/usr/local/bin/*
scripts: move python modules to python directory Up until now, importing an SPDK RPC python module was just a matter of `import rpc`. It's fine until there's another module called `rpc` installed on the system, in which case it's impossible to import both of them. Therefore, to avoid this problem, all of the modules were moved to a separate directory under the "spdk" namespace. The decision to move to a location under a separate directory was motivated by the fact that a directory called scripts/spdk would look pretty confusing. Moreover, it should make it also easier to package these scripts as a python package. Other than moving the packages, all of the imports were updated to reflect these changes. Files under python now use relative imports, while those under scripts/ use the "spdk" namespace and have their PYTHONPATH extended with python directory. Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: Ib43dee73921d590a551dd83885e22870e72451cf Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9692 Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2021-09-21 13:21:31 +00:00
%{python3_sitelib}/spdk/*
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
%package devel
Summary: SPDK development libraries and headers
%description devel
SPDK development libraries and headers
%files devel
/usr/local/include/*
%if %{shared}
configure: Allow to define custom libdir location This is done mainly to align the final location with the one listed in the .pc files created for each lib. Signed-off-by: Michal Berger <michallinuxstuff@gmail.com> Change-Id: I99d6875c9e26f8202723dd6d73bd865b6478bcf9 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/12978 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Dong Yi <dongx.yi@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2022-06-08 12:43:12 +00:00
%{libdir}/lib*.so
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
%endif
%package libs
Summary: SPDK libraries
%description libs
SPDK libraries
%files libs
/etc/ld.so.conf.d/*
configure: Allow to define custom libdir location This is done mainly to align the final location with the one listed in the .pc files created for each lib. Signed-off-by: Michal Berger <michallinuxstuff@gmail.com> Change-Id: I99d6875c9e26f8202723dd6d73bd865b6478bcf9 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/12978 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Dong Yi <dongx.yi@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2022-06-08 12:43:12 +00:00
%{libdir}/lib*.a
%{libdir}/pkgconfig/*.pc
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
%if %{shared}
configure: Allow to define custom libdir location This is done mainly to align the final location with the one listed in the .pc files created for each lib. Signed-off-by: Michal Berger <michallinuxstuff@gmail.com> Change-Id: I99d6875c9e26f8202723dd6d73bd865b6478bcf9 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/12978 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Dong Yi <dongx.yi@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2022-06-08 12:43:12 +00:00
%{libdir}/lib*.so.*
rpmbuild: Add script for building .rpm packages out of the SPDK repo For now this is kept at its very basics. Dependencies are handled via pgkdep, they are not explicitly defined by the .rpm itself. Currently, up to four .rpm packages are being built: spdk spdk-devel spdk-libs spdk-dpdk-lib Together they include all binaries|libs|header files + some setup scripts which are commonly used throughout the repo. Installation paths are hardcoded to: /usr/local/{bin,lib{,/dpdk},include}: - binaries - libraries - header files /usr/libexec/spdk: - scripts /etc: - configuration files Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ic5f067c4e7b8da3d697ee469bc9c794d5a0a035b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6436 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-02-16 15:07:33 +00:00
%endif
%post libs
ldconfig
%if %{dpdk}
%package dpdk-libs
Summary: DPDK libraries
%description dpdk-libs
DPDK libraries
%files dpdk-libs
/usr/local/lib/dpdk
%post dpdk-libs
ldconfig
%endif
%changelog
* Tue Feb 16 2021 Michal Berger <michalx.berger@intel.com>
- Initial RPM .spec for the SPDK
Reference in New Issue Copy Permalink