Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Standardisation of $(BUILD)/.root name
Date: Wed, 15 May 2013 00:06:23 +0200	[thread overview]
Message-ID: <20130514220623.GA3140@free.fr> (raw)
In-Reply-To: <5192B23A.1050508@mind.be>

Arnout, All,

On 2013-05-14 23:52 +0200, Arnout Vandecappelle spake thusly:
> On 14/05/13 17:07, Thomas Petazzoni wrote:
> >Dear J?r?me Pouiller,
> >
> >On Tue, 14 May 2013 16:30:50 +0200, J?r?me Pouiller wrote:
> >
> >>-$(BUILD_DIR)/.root:
> >>+$(STAMP_DIR)/skeleton-target-installed:
> >>  	mkdir -p $(TARGET_DIR)
> >>  	rsync -a \
> >>  		--exclude .empty --exclude .svn --exclude .git \
> >>  		--exclude .hg --exclude=CVS --exclude '*~' \
> >>  		$(TARGET_SKELETON)/ $(TARGET_DIR)/
> >>  	cp support/misc/target-dir-warning.txt $(TARGET_DIR_WARNING_FILE)
> >>+	mkdir -p $(STAMP_DIR)
> >>  	touch $@
> >
> >I'm generally ok with the idea, but I don't like this mkdir. There is
> >already a mkdir that creates the stamp file directory, in the main
> >Makefile.
> 
>  I don't have an issue with a few redundant mkdir -p calls.

I concur with Thomas: we should ensure the stamp-dir is already created
in a generic way, it's kind of an internal stuff, which should not be
visible to users (I mean: packages, and stuff like that, not actual
persons).

That we need to sprinkle the code with a few 'mkdir' here and ther "just
in case" is an indication we do not fully masterise the chain of events,
and is really not nice.

The fact that the 'mkdir' is needed in the first place is because of this
rulle in the top-level Makefile:

    dirs: [...] $(TARGET_DIR) [...] $(STAMP_DIR)

which will have 'make' run the $(TARGET_DIR) goal before the
$(STAMP_DIR) goal.

This can be solved in two ways: the nice one, and the not-so-nice one:
  - have an additional rule:
        $(TARGET_DIR): $(STAMP_DIR)                 <- the nice way
  - invert the order of goals in the 'dirs' rule    <- the not-so-nice way

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2013-05-14 22:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 11:04 [Buildroot] Target rebuilding Jérôme Pouiller
2013-01-17 13:27 ` Stephan Hoffmann
2013-01-18  9:43   ` Jérôme Pouiller
2013-01-19 16:32 ` Arnout Vandecappelle
2013-05-14 14:30   ` [Buildroot] [PATCH] Standardisation of $(BUILD)/.root name Jérôme Pouiller
2013-05-14 15:07     ` Thomas Petazzoni
2013-05-14 15:27       ` Jérôme Pouiller
2013-05-14 22:23         ` Yann E. MORIN
2013-05-15  6:19           ` Jérôme Pouiller
2013-05-15  6:27             ` Jérôme Pouiller
2013-05-15 21:01               ` Yann E. MORIN
2013-05-15 20:59             ` Yann E. MORIN
2013-05-14 21:52       ` Arnout Vandecappelle
2013-05-14 22:06         ` Yann E. MORIN [this message]

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=20130514220623.GA3140@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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