From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Where does post-build script belong?
Date: Tue, 28 Feb 2012 22:19:30 +0000 [thread overview]
Message-ID: <201202282219.30414.arnout@mind.be> (raw)
In-Reply-To: <4F4D4FE4.3020506@gmail.com>
On Tuesday 28 February 2012 22:06:28 Steve Calfee wrote:
> > I seem to be completely lost. Is board/mycompany/myproduct/skeleton
> > above a post-build script or a custom skelecton (something you set
> > BR2_ROOTFS_SKELETON_CUSTOM_PATH to point to)?
> Hi Grant,
>
> I was not aware of that config option. In fact there are no uses of it
> in the current /board... stuff. What I and what I think others have done
> is create my own mini-skeleton in the board.... directory. I can then
> stick in scripts, etc files and maybe even externally built binaries
> into /usr/bin/ in my local area. Then when the post build script is
> executed I just copy all the files from my skeleton to the target
> skeleton. This will overlay the default stuff (that are duplicates in my
> area) and add any new stuff. After the post-build script the target
> skeleton will get all packaged up as a rootfs for your target system.
>
> Someone else will have to describe what that option is for.
If you ask me, BR2_ROOTFS_SKELETON_CUSTOM_PATH is indeed useless and
should be deprecated.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-02-28 22:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 20:41 [Buildroot] Where does post-build script belong? Grant Edwards
2012-02-20 21:00 ` J.C. Woltz
2012-02-20 21:45 ` Grant Edwards
2012-02-21 8:44 ` Luca Ceresoli
2012-02-21 14:54 ` Grant Edwards
2012-02-28 20:38 ` Arnout Vandecappelle
2012-02-28 21:06 ` Grant Edwards
2012-02-28 21:29 ` Steve Calfee
2012-02-28 21:36 ` Grant Edwards
2012-02-28 22:06 ` Steve Calfee
2012-02-28 22:18 ` Grant Edwards
2012-03-16 21:30 ` Peter Korsgaard
2012-02-28 22:19 ` Arnout Vandecappelle [this message]
2012-02-29 7:41 ` Thomas De Schampheleire
2012-03-16 21:32 ` Peter Korsgaard
2012-02-28 22:18 ` Arnout Vandecappelle
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=201202282219.30414.arnout@mind.be \
--to=arnout@mind.be \
--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