Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: William Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Allowing target to modify fs
Date: Tue, 11 May 2010 10:37:17 +0100	[thread overview]
Message-ID: <4BE9254D.4050301@carallon.com> (raw)

Hi All,

I am trying to update one of our projects to the latest snapshot in git. 
I am having a problem following the new file system building changes.

The problem I have is that previously I had a target that was making 
changes to the target fs (Which perhaps may not be correct but that's a 
side issue). The problem is that in the top level makefile the target is 
included after the fs include so it is added to TARGETS after the step 
to build the fs. This means it runs after the fs has already been built.

I see there is the option to run a script to modify the target in 
BR2_ROOTFS_POST_BUILD_SCRIPT but what I really want is to be able to 
ensure a make target runs before the fs is built.

What would be the best way to solve this? I was thinking about doing 
something similar to $(KERNEL_COND_PATCHES) which allows a target to 
specify additional patches for linux. Something similar could be done with:

diff --git a/Makefile b/Makefile
index 2a70a5b..cf929b9 100644
--- a/Makefile
+++ b/Makefile
@@ -400,7 +400,7 @@ $(TARGET_DIR): $(BUILD_DIR)/.root
  erase-fakeroots:
         rm -f $(BUILD_DIR)/.fakeroot*

-target-finalize:
+target-finalize: $(TARGET_COND_TARGETS)
  ifeq ($(BR2_HAVE_DEVFILES),y)
         ( scripts/copy.sh $(STAGING_DIR) $(TARGET_DIR) )
  else

What does anyone think?

Will

-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Development Manager                      Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

                 reply	other threads:[~2010-05-11  9:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4BE9254D.4050301@carallon.com \
    --to=will_wagner@carallon.com \
    --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