From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nishanth Menon Date: Mon, 9 Nov 2015 11:37:13 -0600 Subject: [U-Boot] [PATCH] Makefile: Include vendor common library in include search path In-Reply-To: References: <1446708504-5936-1-git-send-email-nm@ti.com> <563B0603.6040406@ti.com> <563CDEEF.3070403@ti.com> <20151106182348.GA14217@ogun.home> <20151108021845.GI8499@bill-the-cat> <20151108163833.GY8499@bill-the-cat> Message-ID: <5640D9C9.4090803@ti.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 11/09/2015 10:03 AM, Masahiro Yamada wrote: > 2015-11-09 1:38 GMT+09:00 Tom Rini : >> On Sun, Nov 08, 2015 at 09:56:18AM -0600, menon.nishanth at gmail.com wrote: >>> On Sat, Nov 7, 2015 at 8:18 PM, Tom Rini wrote: >>> >>>> Conceptually fine with me. Do we really need a config option for it >>>> tho? >>> >>> I was following the lines of CONFIG_CREATE_ARCH_SYMLINK here. Is there >>> some reason why you'd not want it so? >> >> Masahiro? >> > > Is this an improvement? > > > I am unhappy because I was hoping > we could stop creating symbolic links during building > in a long run. OK. what do we do? option 1: #include "..common/xyz.h" 141 something usage in board files do this for now.. option 2: -I...common (auto generated - original patch) #include "xyz.h" we dont like that since it does not tell us that xyz.h is a board-common header. option 3: #include this needs a soft link which we dont like either. are there any other ways to do this? -- Regards, Nishanth Menon