From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] mk: add makefile extention support Date: Thu, 03 Mar 2016 17:33:47 +0100 Message-ID: <1963758.vYVLsiL7TI@xps13> References: <1455039314-86891-1-git-send-email-keith.wiles@intel.com> <9F76ECAC-A0AA-476F-B0E2-A9A35DB896A7@intel.com> <26D5D061-B40F-4A61-B407-4FA6E2CDF83C@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Cc: dev@dpdk.org To: "Wiles, Keith" Return-path: Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by dpdk.org (Postfix) with ESMTP id E55BD2B96 for ; Thu, 3 Mar 2016 17:41:19 +0100 (CET) Received: by mail-wm0-f43.google.com with SMTP id l68so43184965wml.0 for ; Thu, 03 Mar 2016 08:41:19 -0800 (PST) In-Reply-To: <26D5D061-B40F-4A61-B407-4FA6E2CDF83C@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-03-03 14:55, Wiles, Keith: > >>2016-02-28 21:47, Wiles, Keith: > >>> >Hi, > >>> > > >>> >2016-02-09 11:35, Keith Wiles: > >>> >> Adding support to the build system to allow for Makefile.XXX > >>> >> extention to a subtree, which already has Makefiles. These > >>> >> Makefiles could be from the autotools and others places. Using= > >>> >> the Makefile extention RTE_MKFILE_SUFFIX in a makefile subtree= > >>> >> using 'export RTE_MKFILE_SUFFIX=3D.XXX' to use Makefile.XXX in= > >>> >> that subtree. > >>> >>=20 > >>> >> The main reason I needed this feature was to integrate a autot= ool > >>> >> open source projects with DPDK and keep the original Makefiles= . > >>> > > >>> >Sorry I fail to understand why it is needed. > >>> >Are you trying to add autotool in DPDK? I don't think it is a go= od approach. > >>> >The DPDK must provide a pkgconfig interface to be integrated any= where. > >>>=20 > >>> I was not trying to add autotools to DPDK. On a number of times I= wanted to integrate a open source project(s) with DPDK and use DPDK=E2= =80=99s build system, but because the open source project already conta= ined Makefile files you can not use DPDK build system without modify or= moving the original Makefile files. Using this method I can just add a= exported variable and supply my own Makefile.XXX files. > >>>=20 > >>> One case was building FreeBSD source, but I did not want to modif= y FreeBSD Makefiles (or reply on previous built Makefiles as they would= not work on Linux anyway) as I was pulling the source down from freebs= d.org repo. Using a patch to add the Makefiles with a different suffix = allows me to build FreeBSD using DPDK, without having to modify or own = the FreeBSD source. I have had this problem a number of times with open= source code I did not want to modify, but just build within DPDK build= system and adding the support for a different suffix to DPDK provided = a clean way. The change does not effect the correct build system and ju= st allows someone to define a new suffix for a given subtree in the cod= e. > >> > >>Why would you like to have another project inside the DPDK files tr= ee? > >>If you want to integrate the lib inside an existing project, the so= lution > >>is pkgconfig. > > > >The goal for me was to use DPDK build system for that project, inste= ad of using autotools or some other makefile system. In the case of Fre= eBSD code, the FreeBSD build system requires FreeBSD tools to be built = as the =E2=80=98make=E2=80=99 and the Makefiles are very different on a= Linux machine. >=20 > Does anyone find this patch useful, I would hate to see this one die = as it does not effect the current builds, but adds support for using DP= DK build system without having to modify or move the existing Makefiles= . I would hate making the build system even more complicated to use it for something which is not its role. It opens the door to feature requests which are clearly out of its scop= e.