From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51]) by dpdk.org (Postfix) with ESMTP id BDC535921 for ; Thu, 9 Apr 2015 11:06:49 +0200 (CEST) Received: by wgsk9 with SMTP id k9so90700904wgs.3 for ; Thu, 09 Apr 2015 02:06:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=wixPg5MonPqjbtcJ6qgSrPcmQDdHAw5dehsYf2aXxEo=; b=gAo7cZpTWEChI1t4gjdTVQwA//5dxqWScn+/1gxMpYnCVYoVOPFLlG7AI8Bfd1TVUV U/KrBxFj0Xa9IIHCVy91BM+6aI/WeSmGQDXpcwq46Z5haw4W7Wl1+OIFNDuoV8kVmoVg UmBAOaSApjdsER+W+Ju8IaXUsIkFDd4HIR++1hf//L173KtJM1dwZI1CiSTU7qas947O p0NR54FV6YtPIazMR91MJtiLyuy39N0anrGEVrQgfSkAEYH6h5XfGbR+wRO1n/T3yLo6 qc3S7OOVsLWCT/vWb0nkYvd1T0SORaO9xwV5KWwmpg7DHao0jiAx+sNm8+YIVBmCpu5T ryjQ== X-Gm-Message-State: ALoCoQmc9A6/bSCbrVZOn1Y8NPNLMce/Bx4nrMjjbNtfrYp8dy1AgJiopoO33oUliOLzVNIXgydY X-Received: by 10.180.104.137 with SMTP id ge9mr4521458wib.24.1428570409648; Thu, 09 Apr 2015 02:06:49 -0700 (PDT) Received: from avi.cloudius ([212.143.139.214]) by mx.google.com with ESMTPSA id ge8sm19164671wjc.32.2015.04.09.02.06.48 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Apr 2015 02:06:48 -0700 (PDT) Message-ID: <55264127.2020604@cloudius-systems.com> Date: Thu, 09 Apr 2015 12:06:47 +0300 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: "Gonzalez Monroy, Sergio" , Stephen Hemminger References: <1428505645-5578-1-git-send-email-sergio.gonzalez.monroy@intel.com> <1428505645-5578-2-git-send-email-sergio.gonzalez.monroy@intel.com> <20150408112619.14596b65@urahara> <55263955.1070707@intel.com> In-Reply-To: <55263955.1070707@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v3 1/5] mk: remove combined library and related options X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Apr 2015 09:06:50 -0000 On 04/09/2015 11:33 AM, Gonzalez Monroy, Sergio wrote: > On 08/04/2015 19:26, Stephen Hemminger wrote: >> On Wed, 8 Apr 2015 16:07:21 +0100 >> Sergio Gonzalez Monroy wrote: >> >>> Currently, the target/rules to build combined libraries is different >>> than the one to build individual libraries. >>> >>> By removing the combined library option as a build configuration option >>> we simplify the build pocess by having a single point for >>> linking/archiving >>> libraries in DPDK. >>> >>> This patch removes CONFIG_RTE_BUILD_COMBINE_LIB build config option and >>> removes the makefiles associated with building a combined library. >>> >>> The CONFIG_RTE_LIBNAME config option is kept as it will be use to >>> always generate a linker script that acts as a single combined library. >>> >>> Signed-off-by: Sergio Gonzalez Monroy >>> >> No. We use combined library and it greatly simplfies the application >> linking process. >> > After all the opposition this patch had in v2, I did explain the > current issues > (see http://dpdk.org/ml/archives/dev/2015-March/015366.html ) and this > was the agreed solution. > > As I mention in the cover letter (also see patch 2/5), building DPDK > (after applying this patch series) will always generate a very simple > linker script that behaves as a combined library. > I encourage you to apply this patch series and try to build your app > (which links against combined lib). > Your app should build without problem unless I messed up somewhere and > it needs fixing. Is it possible to generate a pkgconfig file (dpdk.pc) that contains all of the setting needed to compile and link with dpdk? That will greatly simplify usage. A linker script is just too esoteric.