Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Riko Ho <antonius.riko@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] post-build.sh
Date: Tue, 23 May 2017 12:56:26 +0800	[thread overview]
Message-ID: <2354cca7-62d1-ddce-3ac0-d17dbd6e2091@gmail.com> (raw)

Hallo Thomas,

I read from your book :
http://elinux.org/images/2/2a/Using-buildroot-real-project.pdf
page 24,
=============
Create a post-build script in
board/<company>/<project>/post-build.sh
and tell
Buildroot to run it with the
BR2
ROOTFS
POST
BUILD
SCRIPT
.
I
This script is executed from the Buildroot main directory and
receives the target filesystem directory as argument.
I
Typically, my script does:
I
Tune the
/etc/inittab

/etc/fstab
or
/etc/securetty
files
I
Copy the contents of
board/<company>/<project>/rootfs-additions/
*into the*
*target root filesystem.*
In this directory, I put additional init scripts, configuration files
for network services, or override existing files.
=============================
Is "buildroot/output/target" = target root filesystem ?
So if I have a file "init" to be copied to buildroot/output/target,
1. I put "init" on buildroot/board/<company>/<project>/rootfs-additions
2. Inside post-build.sh, cp 
board/<company>/<project>/rootfs-additions/init buildroot/output/target/.

Please let me know if it's not right way, thanks
-- 
*

/*******/
Sent by Ubuntu LTS 16.04,
??,
Regards,
Riko Ho
/*******/

*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170523/08eec82d/attachment.html>

                 reply	other threads:[~2017-05-23  4:56 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=2354cca7-62d1-ddce-3ac0-d17dbd6e2091@gmail.com \
    --to=antonius.riko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox