Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] custom application
Date: Thu, 26 Sep 2013 23:09:56 +0200	[thread overview]
Message-ID: <5244A2A4.8010206@lucaceresoli.net> (raw)
In-Reply-To: <OF9ADA6F51.A3CB613B-ON85257BF2.0068F0A1-85257BF2.00693830@LocalDomain>

Naitik Amin wrote:
> Hi there,
>
> I recently used buildroot to setup my build environment, to generate 
> uboot, kernel and rootfs. It has been very helpful.
>
> Now I am at a point, where I would like to add my custom application. 
> Does the framework allow to create skeletals for applications ? Which 
> gets compiled and be made part of rootfs by doing top level make.

Of course you can!
The Buildroot manual has a detail explanation of how you can do it.
See section 6.2, "Adding new packages to Buildroot"
(http://buildroot.net/downloads/manual/manual.html#adding-packages).

Luca

  reply	other threads:[~2013-09-26 21:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26 19:09 [Buildroot] custom application Naitik Amin
2013-09-26 21:09 ` Luca Ceresoli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-09-26 19:16 Naitik Amin
2013-09-26 20:29 ` Zoltan Gyarmati

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=5244A2A4.8010206@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --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