From: Nishanth Menon <nm@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Makefile: Include vendor common library in include search path
Date: Mon, 9 Nov 2015 11:37:13 -0600 [thread overview]
Message-ID: <5640D9C9.4090803@ti.com> (raw)
In-Reply-To: <CAK7LNAQd==gvcu1Fi8HcXyBUCdWGUMxkE5Okoryh_dSPs3nOrQ@mail.gmail.com>
On 11/09/2015 10:03 AM, Masahiro Yamada wrote:
> 2015-11-09 1:38 GMT+09:00 Tom Rini <trini@konsulko.com>:
>> 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 <trini@konsulko.com> 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 <board-common/xyz.h>
this needs a soft link which we dont like either.
are there any other ways to do this?
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2015-11-09 17:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 7:28 [U-Boot] [PATCH] Makefile: Include vendor common library in include search path Nishanth Menon
2015-11-05 7:32 ` Nishanth Menon
2015-11-06 0:15 ` Simon Glass
2015-11-06 3:30 ` Nishanth Menon
2015-11-06 4:50 ` Masahiro Yamada
2015-11-06 17:10 ` Nishanth Menon
2015-11-06 18:23 ` Nishanth Menon
2015-11-06 23:58 ` Simon Glass
2015-11-08 2:18 ` Tom Rini
2015-11-08 15:56 ` menon.nishanth at gmail.com
2015-11-08 16:38 ` Tom Rini
2015-11-09 16:03 ` Masahiro Yamada
2015-11-09 17:37 ` Nishanth Menon [this message]
2015-11-09 20:24 ` Simon Glass
2015-11-10 3:25 ` Masahiro Yamada
2015-11-10 14:55 ` Nishanth Menon
2015-11-10 15:34 ` Nishanth Menon
2015-11-12 16:16 ` Simon Glass
2015-11-12 16:22 ` Tom Rini
2015-11-12 16:45 ` Nishanth Menon
2015-11-12 16:56 ` Simon Glass
2015-11-12 17:05 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5640D9C9.4090803@ti.com \
--to=nm@ti.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox