Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Help understanding how to develop with buildroot
@ 2009-12-03  2:26 Mike Crowe
  2009-12-03 10:30 ` Peter Korsgaard
  0 siblings, 1 reply; 6+ messages in thread
From: Mike Crowe @ 2009-12-03  2:26 UTC (permalink / raw)
  To: buildroot

Hi folks,

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

It appears that BR copies my new package from packages/ to build_arm/ and
compiles it.  However, if I have to do a lot of source code changes, it
appears that I should edit the build_arm directory and then sync it back to
packages when I have it running.

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

TIA
Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20091202/b912d7dd/attachment.htm>

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Buildroot] Help understanding how to develop with buildroot
  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
  0 siblings, 1 reply; 6+ messages in thread
From: Peter Korsgaard @ 2009-12-03 10:30 UTC (permalink / raw)
  To: buildroot

>>>>> "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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Buildroot] Help understanding how to develop with buildroot
  2009-12-03 10:30 ` Peter Korsgaard
@ 2009-12-03 12:40   ` Mike Crowe
  2009-12-03 13:13     ` Peter Korsgaard
  0 siblings, 1 reply; 6+ messages in thread
From: Mike Crowe @ 2009-12-03 12:40 UTC (permalink / raw)
  To: buildroot

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

Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20091203/58093b4e/attachment.htm>

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Buildroot] Help understanding how to develop with buildroot
  2009-12-03 12:40   ` Mike Crowe
@ 2009-12-03 13:13     ` Peter Korsgaard
  2009-12-03 13:24       ` Thomas Petazzoni
  0 siblings, 1 reply; 6+ messages in thread
From: Peter Korsgaard @ 2009-12-03 13:13 UTC (permalink / raw)
  To: buildroot

>>>>> "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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Buildroot] Help understanding how to develop with buildroot
  2009-12-03 13:13     ` Peter Korsgaard
@ 2009-12-03 13:24       ` Thomas Petazzoni
  2009-12-03 13:33         ` Mike Crowe
  0 siblings, 1 reply; 6+ messages in thread
From: Thomas Petazzoni @ 2009-12-03 13:24 UTC (permalink / raw)
  To: buildroot

Le Thu, 03 Dec 2009 14:13:22 +0100,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :

> 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.

See also http://buildroot.org/buildroot.html#rebuilding_packages for
details.

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Buildroot] Help understanding how to develop with buildroot
  2009-12-03 13:24       ` Thomas Petazzoni
@ 2009-12-03 13:33         ` Mike Crowe
  0 siblings, 0 replies; 6+ messages in thread
From: Mike Crowe @ 2009-12-03 13:33 UTC (permalink / raw)
  To: buildroot

Perfect!  That's exactly what I needed guys, thank you!

On Thu, Dec 3, 2009 at 8:24 AM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Le Thu, 03 Dec 2009 14:13:22 +0100,
> Peter Korsgaard <jacmet@uclibc.org> a ?crit :
>
> > 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.
>
> See also http://buildroot.org/buildroot.html#rebuilding_packages for
> details.
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers and embedded Linux development,
> consulting, training and support.
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20091203/dca19768/attachment.htm>

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2009-12-03 13:33 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2009-12-03 13:24       ` Thomas Petazzoni
2009-12-03 13:33         ` Mike Crowe

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox