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 11:30:57 +0100	[thread overview]
Message-ID: <878wdktkm6.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <16d4c3590912021826v916b813gf6f422634058df54@mail.gmail.com> (Mike Crowe's message of "Wed, 2 Dec 2009 21:26:30 -0500")

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

Hi,

 Mike> Apologies if this is obvious, but I haven't been able to find the
 Mike> right words to search for it:

 Mike> It appears that BR copies my new package from packages/ to
 Mike> build_arm/ and compiles it.

Yes. Notice that the 2009.11 release is out now, and it has a somewhat
different (simpler) build directory layout.

 Mike> However, if I have to do a lot of source code changes, it appears
 Mike> that I should edit the build_arm directory and then sync it back
 Mike> to packages when I have it running.

Yes, if you need to patch something in the package sources, you'll need
to make a patch (quilt is nice for this) and copy it to
package/<something>/. Make sure you name it <something>-*.patch
otherwise it won't be applied.

What exactly is it that you are changing? If you're fixing something
general, then please submit those patches to the package upstream and us
so we can integrate it into buildroot.

 Mike> Is this the right flow?? Are there any instructions or tools to help do this?

It is, but it's pretty uncommon to have to do project specific patching
of the packages.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-12-03 10:30 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 [this message]
2009-12-03 12:40   ` Mike Crowe
2009-12-03 13:13     ` Peter Korsgaard
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=878wdktkm6.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