From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC] Makefile: Create empty <config.h> if this header file is not needed by board
Date: Sun, 10 Mar 2013 15:56:34 +0100 [thread overview]
Message-ID: <20130310145634.GP1906@pengutronix.de> (raw)
In-Reply-To: <1362913680.690644667@f363.mail.ru>
On Sun, Mar 10, 2013 at 03:08:00PM +0400, Alexander Shiyan wrote:
> > Patch creates empty <config.h> if this header is not needed by board.
> > This will allow to remove many empty config.h files from boards.
> >
> > Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
> > ---
> > Makefile | 17 +++++++++++------
> > 1 file changed, 11 insertions(+), 6 deletions(-)
> >
> > diff --git a/Makefile b/Makefile
> > index b5819fc..e8d9984 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -898,13 +898,18 @@ include/asm:
> > $(Q)$(check-symlink)
> > $(Q)$(create-symlink)
> >
> > +define symlink-config-h
> > + if [ -f $(srctree)/$(BOARD)/config.h ]; then \
> > + $(kecho) ' SYMLINK $@ -> $(BOARD)/config.h'; \
> > + ln -fsn $(srctree)/$(BOARD)/config.h $@; \
> > + else \
> > + $(kecho) ' CREATE $@'; \
> > + echo -n > $@; \
> > + fi
How does git incorporate with this? I think git just ignores empty files
like these, right?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-03-10 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 18:30 Alexander Shiyan
2013-03-10 11:08 ` Alexander Shiyan
2013-03-10 14:56 ` Sascha Hauer [this message]
2013-03-10 15:01 ` Re[2]: " Alexander Shiyan
2013-03-10 23:24 ` Sascha Hauer
2013-03-11 16:10 ` Re[2]: " Alexander Shiyan
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=20130310145634.GP1906@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=shc_work@mail.ru \
/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