From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH] mk: add rpath for applications Date: Tue, 3 May 2016 14:24:22 +0100 Message-ID: <5728A686.5040004@intel.com> References: <1461947665-1086-1-git-send-email-ferruh.yigit@intel.com> <2540046.4XauHpbFhJ@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 7D4B42904 for ; Tue, 3 May 2016 15:24:32 +0200 (CEST) In-Reply-To: <2540046.4XauHpbFhJ@xps13> 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 5/2/2016 5:10 PM, Thomas Monjalon wrote: > 2016-04-29 17:34, Ferruh Yigit: >> Add default library output folder to the library search folder. >> >> This is useful for development environment, in production environment >> DPDK libraries already should be in know locations. >=20 > Yes it is useful in dev environment, but can be risky or strange when > packaged for production environment. > Shouldn't we have a switch to avoid a development garbage in production= ? > I suggest to use RTE_DEVEL_BUILD. >=20 Right, I will use RTE_DEVEL_BUILD >> Patch removes requirement to set LD_LIBRARY_PATH variable when DPDK >> compiled as shared library. >=20 > Yes, this patch could remove > export LD_LIBRARY_PATH=3D$build/lib:$LD_LIBRARY_PATH > in scripts/test-null.sh. >=20 Sure, I can update it. > [...] >> +ifeq ($(CONFIG_RTE_BUILD_SHARED_LIB),y) >> +LDFLAGS +=3D --rpath=3D$(RTE_SDK_BIN)/lib >> +endif >=20 > Isn't it -rpath, with a single dash? >=20 It seems both are working, I will convert to single dash. > As it is a variable setting, it should be added before the rules, > just after LDLIBS settings. >=20 OK. I will send an updated version. Thanks for the review, ferruh