From: Steve Calfee <stevecalfee@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] which templates are used?
Date: Tue, 12 Apr 2011 09:52:57 -0700 [thread overview]
Message-ID: <4DA48369.3000904@gmail.com> (raw)
In-Reply-To: <201104120801.08028.minimod@morethan.org>
On 04/12/11 06:01, Michael S. Zick wrote:
>> Mine patchrootfs is:
>> #!/bin/bash
>> #
>> # skript which runs before creating rootfs
>> #
>> #
>> MAINDIR=${1}/../../
>> SRCDIR=${MAINDIR}"target/device/beagleboard/skeleton/*"
>> DESTDIR=${1}
>> echo "***************patching some stuff in " ${DESTDIR} from ${SRCDIR}
>> #echo "DESTDIR " ${DESTDIR}
>> #echo "SRCDIR " ${SRCDIR}
>> #ls -l ${SRCDIR} ${SRCDIR}"/etc"
>> cp -rvp ${SRCDIR} ${DESTDIR}
>> echo "end of userdefined script before packing rootfs"
>>
>> So this copies the fs skeleton, recursively from the local directory
>> after every build. The trick is it just overlays the fs in the target,
>> so you only have to add files that are specific or changed in your
>> build. So if you tweak an existing file say in /etc, it will replace
>> that file. If you add a new file (maybe a script) say in /usr/bin it
>> will add that from your local tree into the build. The local skeleton
>> should stay very sparse.
>>
>> There is no way to remove files that are not needed etc, just remove
>> them locally in your skeleton and when buildroot is remade with a clean
>> it will get all sorted out.
>>
>
> Would using rsync with appropriate options instead of cp do that trick?
>
> Mike
Hi Mike,
Maybe, but I think you would have to have an entire tree in your local
directory, my goal was to have as few board specific files as necessary.
I haven't actually found it much of a problem growing litter in the file
system. And if it is I can always do the buildroot "make clean".
Regards, Steve
next prev parent reply other threads:[~2011-04-12 16:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 20:10 [Buildroot] which templates are used? Michael Burghart
2011-04-11 20:52 ` Michael Burghart
2011-04-11 21:14 ` Bjørn Forsman
2011-04-11 23:34 ` Michael J. Hammel
2011-04-12 6:42 ` Patryk Benderz
2011-04-12 17:54 ` Bjørn Forsman
2011-04-11 21:20 ` Daniele Salvatore Albano
2011-04-12 0:06 ` Steve Calfee
2011-04-12 13:01 ` Michael S. Zick
2011-04-12 16:52 ` Steve Calfee [this message]
2011-04-19 20:25 ` Thomas Petazzoni
2011-04-20 16:59 ` Bjørn Forsman
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=4DA48369.3000904@gmail.com \
--to=stevecalfee@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.