From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] mk: add rpath for applications Date: Mon, 02 May 2016 18:10:29 +0200 Message-ID: <2540046.4XauHpbFhJ@xps13> References: <1461947665-1086-1-git-send-email-ferruh.yigit@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Ferruh Yigit Return-path: Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54]) by dpdk.org (Postfix) with ESMTP id E7E1437B7 for ; Mon, 2 May 2016 18:10:31 +0200 (CEST) Received: by mail-wm0-f54.google.com with SMTP id v200so23410020wmv.1 for ; Mon, 02 May 2016 09:10:31 -0700 (PDT) In-Reply-To: <1461947665-1086-1-git-send-email-ferruh.yigit@intel.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" 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. 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. > Patch removes requirement to set LD_LIBRARY_PATH variable when DPDK > compiled as shared library. Yes, this patch could remove export LD_LIBRARY_PATH=$build/lib:$LD_LIBRARY_PATH in scripts/test-null.sh. [...] > +ifeq ($(CONFIG_RTE_BUILD_SHARED_LIB),y) > +LDFLAGS += --rpath=$(RTE_SDK_BIN)/lib > +endif Isn't it -rpath, with a single dash? As it is a variable setting, it should be added before the rules, just after LDLIBS settings.