Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot-reg
Date: Tue, 6 Mar 2012 18:27:36 +0100	[thread overview]
Message-ID: <20120306182736.5f41bcc9@skate> (raw)
In-Reply-To: <CAOka8SzMY_oqW+wBT5PBUh1+nYhs_aooZaybMPFaNjpK+dDAbw@mail.gmail.com>

Hello,

For community support to Buildroot, I'd prefer if you asked the
Buildroot mailing list instead. Since your e-mail does not contain any
confidential information specific to your project, I took the freedom
of directly copying the Buildroot list for this reply. Please keep the
list in Cc for this discussion.

Le Tue, 6 Mar 2012 22:49:06 +0530,
saketha rama <ramasaketha@gmail.com> a ?crit :

>       I just found your PPT titled  "Using buildroot for real
> projects" .

Good. Just a detail: this document is not a PPT. PPT is a proprietary
file format that works only with the Microsoft Powerpoint proprietary
software, which I don't use. The document "Using Buildroot for real
projects" that you have found is a PDF generated with LaTeX.

> I have a great difficulty creating my customised rootfs
> for beaglebone embedded system using buildroot. It is said in your
> ppt that the buildroot/fs/skeleton will decide the rootfs structure,
> but after I change the skeleton also nothing is changed in my rootfs.

The skeleton is copied into the target directory (which will become the
contents of your root filesystem) at the *beginning* of the Buildroot
build process. Therefore, if you make changes to the skeleton, you must
do a "make clean; make" invocation to force Buildroot to restart the
build from scratch.

Of course, since this is practical at all, I do not recommend using the
skeleton mechanism to customize the root filesystem contents. I rather
recommend:

 *) Creating Buildroot packages if what you need to add to the root
 filesystem are additional libraries or applications ;

 *) Use the post-build script mechanism to add configuration files or
 scripts to the root filesystem. Since this post-build script is
 executed at the end of *every* build, it doesn't carry the same
 problem as the "customize skeleton" solution.

See slides 23 and 24 of the presentation "Using Buildroot for real
projects".

Do not hesitate to get back to us if you need more details about those
mechanisms,

Best regards,

Thomas Petazzoni
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

           reply	other threads:[~2012-03-06 17:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAOka8SzMY_oqW+wBT5PBUh1+nYhs_aooZaybMPFaNjpK+dDAbw@mail.gmail.com>]

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=20120306182736.5f41bcc9@skate \
    --to=thomas.petazzoni@free-electrons.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