Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Where does post-build script belong?
Date: Tue, 28 Feb 2012 20:38:53 +0000	[thread overview]
Message-ID: <201202282038.54757.arnout@mind.be> (raw)
In-Reply-To: <ji0b7n$2hl$1@dough.gmane.org>

On Tuesday 21 February 2012 14:54:47 Grant Edwards wrote:
[snip]
> I don't want to replace the default skeleton.  I want to add some
> files to it, and possible modify a few.  The documentation describes
> two ways to do that:
> 
>   1) package/customize
> 
>   2) post-build script
> 
> I'm told 1) is now depricated, so I'm switching to 2).
> 
> Where under board/mycompany/myproduct do you put "extra" files that
> will be added to the standard skeleton?

 I put it in board/mycompany/myproduct/skeleton.  Although 
rootfs-additions would be a better name than skeleton.


 I would like to add a feature to buildroot to simplify out-of-tree
additions (rootfs files, patches, config files, extra packages, ...).
I'll send out an RFC for that soonish.


 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

  reply	other threads:[~2012-02-28 20:38 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 [this message]
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
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=201202282038.54757.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