From mboxrd@z Thu Jan 1 00:00:00 1970 From: Panu Matilainen Subject: Re: [PATCH v4 6/7] mk: Add rule for installing sdk files Date: Mon, 19 Oct 2015 17:00:35 +0300 Message-ID: <5624F783.5060506@redhat.com> References: <1442608390-12537-1-git-send-email-mario.alfredo.c.arevalo@intel.com> <1444076406-30141-1-git-send-email-mario.alfredo.c.arevalo@intel.com> <1444076406-30141-7-git-send-email-mario.alfredo.c.arevalo@intel.com> <56215084.9060201@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit To: Olivier MATZ , Mario Carrillo , dev@dpdk.org Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 7F4055A53 for ; Mon, 19 Oct 2015 16:00:37 +0200 (CEST) In-Reply-To: <56215084.9060201@6wind.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 10/16/2015 10:31 PM, Olivier MATZ wrote: > Hi Panu, > > On 10/05/2015 10:20 PM, Mario Carrillo wrote: >> Add hierarchy-file support to the DPDK makefiles, scripts, >> examples, tools, config files and headers. >> >> When invoking "make install-sdk" makefiles, scripts, >> examples, tools, config files will be installed in: >> $(DESTDIR)/$(SDK_DIR) >> and headers will be installed in: >> $(DESTDIR)/$(INCLUDE_DIR) >> >> Where SDK_DIR=/usr/share/dpdk and INCLUDE_DIR=/usr/include/dpdk >> by default. >> >> You can overrite SDK_DIR and INCLUDE_DIR vars. >> This hierarchy is based on: >> http://www.freedesktop.org/software/systemd/man/file-hierarchy.html >> >> Signed-off-by: Mario Carrillo > > I don't know if it's feasible, but I think it would be great here > to be able to install a SDK that is usable to build external > applications. > > I mean, doing something like that: > > make install-sdk DESTDIR=/tmp/sdk > cd /path/to/examples/helloworld > make RTE_SDK=/tmp/sdk/usr/share/dpdk > > Else, what is the purpose of installing the sdk? Its possible (been there), it just needs some additional symlinks and such, at least for lib/ and include/. However at that point the contents become arch-dependent (due to the lib symlink) meaning it cannot go into /usr/share. - Panu - > Regards, > Olivier >