From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH v3 1/5] mk: remove combined library and related options Date: Wed, 8 Apr 2015 11:26:19 -0700 Message-ID: <20150408112619.14596b65@urahara> References: <1428505645-5578-1-git-send-email-sergio.gonzalez.monroy@intel.com> <1428505645-5578-2-git-send-email-sergio.gonzalez.monroy@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev-VfR2kkLFssw@public.gmane.org To: Sergio Gonzalez Monroy Return-path: In-Reply-To: <1428505645-5578-2-git-send-email-sergio.gonzalez.monroy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 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.