From: Dmytro Milinevskyy <milinevskyy@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] [skeleton] option to define path to custom rootfs skeleton
Date: Wed, 16 Jun 2010 23:25:56 +0300 [thread overview]
Message-ID: <4c1933f7.954fdf0a.3c35.6c7e@mx.google.com> (raw)
Signed-off-by: Dmytro Milinevskyy <milinevskyy@gmail.com>
---
Makefile | 4 ++++
fs/Config.in | 23 +++++++++++++++++++++++
2 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/Makefile b/Makefile
index e0fac17..58a7a72 100644
--- a/Makefile
+++ b/Makefile
@@ -368,6 +368,10 @@ $(STAGING_DIR):
@mkdir -p $(STAGING_DIR)/usr/include
@mkdir -p $(STAGING_DIR)/usr/bin
+ifeq ($(BR2_ROOTFS_SKELETON_CUSTOM),y)
+TARGET_SKELETON=$(BR2_ROOTFS_SKELETON_CUSTOM_PATH)
+endif
+
$(BUILD_DIR)/.root:
mkdir -p $(TARGET_DIR)
if ! [ -d "$(TARGET_DIR)/bin" ]; then \
diff --git a/fs/Config.in b/fs/Config.in
index 6865eea..188e815 100644
--- a/fs/Config.in
+++ b/fs/Config.in
@@ -23,6 +23,29 @@ config BR2_ROOTFS_DEVICE_TABLE
to the makedevs utility to create all the special device
files in the target filesystem.
+choice
+ prompt "Root FS skeleton"
+
+config BR2_ROOTFS_SKELETON_DEFAULT
+ bool "default target skeleton"
+ help
+ Use default target skeleton
+
+config BR2_ROOTFS_SKELETON_CUSTOM
+ bool "custom target skeleton"
+ help
+ Use custom target skeleton.
+
+endchoice
+
+if BR2_ROOTFS_SKELETON_CUSTOM
+config BR2_ROOTFS_SKELETON_CUSTOM_PATH
+ string "custom target skeleton path"
+ default "fs/skeleton"
+ help
+ Path custom target skeleton.
+endif
+
source "fs/cramfs/Config.in"
source "fs/cloop/Config.in"
source "fs/ext2/Config.in"
--
1.7.1
next reply other threads:[~2010-06-16 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 20:25 Dmytro Milinevskyy [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-10 19:58 [Buildroot] [PATCH 2/2] [skeleton] option to define path to custom rootfs skeleton Dmytro Milinevskyy
2010-06-15 7:21 ` Thomas Petazzoni
2010-06-15 8:14 ` Dmytro Milinevskyy
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=4c1933f7.954fdf0a.3c35.6c7e@mx.google.com \
--to=milinevskyy@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.