Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Help understanding how to develop with buildroot
Date: Thu, 03 Dec 2009 14:13:22 +0100	[thread overview]
Message-ID: <87r5rcryj1.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <16d4c3590912030440j4655c776w9dc54c3f0fe46cab@mail.gmail.com> (Mike Crowe's message of "Thu, 3 Dec 2009 07:40:22 -0500")

>>>>> "Mike" == Mike Crowe <drmikecrowe@gmail.com> writes:

Hi,

 Mike> I'm starting to port our application to an embedded device. ?I
 Mike> think there will be quite a few changes, and it's a fairly large
 Mike> application. ?I believe there may be week(s) changing the
 Mike> application to get it to run in the new environment. ?That's why
 Mike> I wanted to avoid a complete recompile each build.

OK, you can trigger a rebuild of just your package by removing the
correct file (depends on how you integrated it in BR what that file is)
or simply delete the build_arm/<package> directory.

For initial development with lots of compile/test/fix cycles it probably
makes more sense to build your application by hand instead of in BR
though.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-12-03 13:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03  2:26 [Buildroot] Help understanding how to develop with buildroot Mike Crowe
2009-12-03 10:30 ` Peter Korsgaard
2009-12-03 12:40   ` Mike Crowe
2009-12-03 13:13     ` Peter Korsgaard [this message]
2009-12-03 13:24       ` Thomas Petazzoni
2009-12-03 13:33         ` Mike Crowe

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=87r5rcryj1.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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