[dpdk-dev] [PATCH 0/7] Add hierarchical support to make install
Olivier MATZ
olivier.matz at 6wind.com
Tue Sep 22 10:16:43 CEST 2015
Hi Mario,
On 09/18/2015 10:33 PM, Mario Carrillo wrote:
> DPDK package lacks of a mechanism to install libraries, headers
> applications and kernel modules to a file system tree.
>
> This patch set allows to install files according to the next
> proposal:
> http://www.freedesktop.org/software/systemd/man/file-hierarchy.html
>
> By adding a parameter H=1 (hierarchy-file) to makefile system, it is
> possible to do the next steps
>
> make config T=TARGET
> make
> make install H=1
The current "install" target is not designed to work on one
build directory. Instead, it takes as a parameter a list of
config templates, and the build directory is the name of the
target.
Today, we have:
make install T="*-native-linuxapp-gcc"
is somehow equivalent to:
make config T=i686-native-linuxapp-gcc O=i686-native-linuxapp-gcc
make O=i686-native-linuxapp-gcc
make config T=x86_32-native-linuxapp-gcc O=x86_32-native-linuxapp-gcc
make O=x86_32-native-linuxapp-gcc
make config T=x86_64-native-linuxapp-gcc O=x86_64-native-linuxapp-gcc
make O=x86_64-native-linuxapp-gcc
The "install H=1" directive you are adding seems to implicitly be
working on a build directory (modifiable with O=), which is the case
for the "make" command but not for the current "make install".
I'm in favor of having different command names for installing
a binary sdk and for installing the runtime libs in the hierarchical
file system, this to avoid having different behaviors for the same
name.
Regards,
Olivier
More information about the dev
mailing list