Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Zoltan Gyarmati <mr.zoltan.gyarmati@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] custom application
Date: Thu, 26 Sep 2013 22:29:43 +0200	[thread overview]
Message-ID: <52449937.7090206@gmail.com> (raw)
In-Reply-To: <OF3A3A3AC8.25079E91-ON85257BF2.0069E3B1-85257BF2.0069E9F2@LocalDomain>

On 09/26/2013 09:16 PM, 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.
>
> Thanks,
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
Hi,

check out this chapter from the docs:
http://buildroot.uclibc.org/downloads/manual/manual.html#adding-packages
It's make your life easier if you use autotools / cmake or some other
Makefile generator for your application, but also works with
hand-written Makefiles as well. For the development phase personally i
use the local site method to get the source for building, but you also
can go on and wire it directly to your source code repo.
Good luck,

-- 
br, 
Zoltan Gyarmati
mail: mr.zoltan.gyarmati at gmail.com
freenode nick: zgyarmati

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

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

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=52449937.7090206@gmail.com \
    --to=mr.zoltan.gyarmati@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