Buildroot developer meeting report
Hi all,
Just before ELC-E in Duesseldorf, on October 11 and 12, we had a Buildroot
Developer Meeting (sponsored by Mind, yay!). You can find the report on the wiki:
http://elinux.org/Buildroot:DeveloperDaysELCE2014#Discussion_topics_and_report
Some highlights:
* We mainly used this time to clean up patchwork. We didn't keep exact statistics, but the number of patches was reduced from roughly 350 to roughly 250, and a significant number of patches have been reviewed and/or reposted.
* There were a few important large series that were discussed and eventually applied.
* We have taken a decision on how to deal with atomic operations, with missing license files, with march/mcpu/mtune conflicts, and we have decided to leave the package name out of patch file names. Some of these things have been implemented, some are still to do.
* We discussed the GSoC project which wasn't successful this year. We'll try again next year.
If there is any further point of discussion or a conclusion that you don't
agree with, feel free to start a discussion here on the list or on IRC.
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
Hi Arnout, Everyone,
I'm new to Buildroot and have been evaluating it along with Yocto to replace uClinux/home-brew environment for a new design. ?I noticed in the 'Discussion_topics_and_report' that there was an evaluation of BR2_EXTERNAL. ?Was it determined what was needed? ?I hope this wasn't a foreshadowing that BR2_EXTERNAL might be deprecated. As part of my evaluation, I created a 'doug' directory and mimicked the Buildroot?directory structure as needed. ?All my custom bits were confined to this directory; I didn't pollute the Buildroot tree with irrelevant changes. ?I then use BR2_EXTERNAL to point to 'doug'. ?For example, make BR2_EXTERNAL=doug [defconfig]
set up the environment to point to all the proper locations. ?BR2_EXTERNAL, as is, is a very nice feature!
Thanks and regards,...doug(Doug Kehn)
On Wednesday, October 22, 2014 7:56 AM, Arnout Vandecappelle <[email protected]> wrote:
Hi all,
Just before ELC-E in Duesseldorf, on October 11 and 12, we had a Buildroot
Developer Meeting (sponsored by Mind, yay!). You can find the report on the wiki:
http://elinux.org/Buildroot:DeveloperDaysELCE2014#Discussion_topics_and_report
Some highlights:
* We mainly used this time to clean up patchwork. We didn't keep exact statistics, but the number of patches was reduced from roughly 350 to roughly 250, and a significant number of patches have been reviewed and/or reposted.
* There were a few important large series that were discussed and eventually applied.
* We have taken a decision on how to deal with atomic operations, with missing license files, with march/mcpu/mtune conflicts, and we have decided to leave the package name out of patch file names. Some of these things have been implemented, some are still to do.
* We discussed the GSoC project which wasn't successful this year. We'll try again next year.
If there is any further point of discussion or a conclusion that you don't
agree with, feel free to start a discussion here on the list or on IRC.
Regards,
Arnout
Signature · 16 lines
Arnout Vandecappelle? ? ? ? ? ? ? ? ? ? ? ? ? arnout at mind be Senior Embedded Software Architect? ? ? ? ? ? +32-16-286500 Essensium/Mind? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium? ? ? ? ? BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint:? 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F _______________________________________________ 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/20141024/a731637d/attachment.html>
Doug, All,
On 2014-10-24 19:32 +0000, Doug Kehn spake thusly:
Quoted 4 lines
Hi Arnout, Everyone,
I'm new to Buildroot and have been evaluating it along with Yocto to replace uClinux/home-brew environment for a new design. I noticed in the 'Discussion_topics_and_report' that there was an evaluation ofBR2_EXTERNAL. Was it determined what was needed? I hope this wasn't a foreshadowing thatBR2_EXTERNALmight be deprecated.
No, BR2_EXTERNAL is not deprecated at all. It is a relatively new feature, and at the previous developpers days, some users expressed some concerns about some behaviour of BR2_EXTERNAL, because it was new at that time.
Since those concerns were unfounded, so the topic was only briefly skimmed over in D?sseldorf, and the conclusion was that "everything is OK".
So, you can count on BR2_EXTERNAL for the foreseeable future. :-)
Quoted 5 lines
As part of my evaluation, I created a 'doug' directory and mimicked the Buildroot directory structure as needed. All my custom bits were confined to this directory; I didn't pollute the Buildroot tree with irrelevant changes. I then use
BR2_EXTERNALto point to 'doug'. For example,
make BR2_EXTERNAL=doug [defconfig]
set up the environment to point to all the proper locations.BR2_EXTERNAL, as is, is a very nice feature!
Yup, that's how it is expected to be used. Nice to see you like it! :-)
Regards,
Yann E. MORIN.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
All,
Quoted 4 lines · Arnout Vandecappelle
Hi all,
Just before ELC-E in Duesseldorf, on October 11 and 12, we had a
Buildroot
Quoted 1 line
Developer Meeting (sponsored by Mind, yay!). You can find the report on
the wiki:
Quoted 2 lines
http://elinux.org/Buildroot:DeveloperDaysELCE2014#Discussion_topics_and_report
Quoted 6 lines
Some highlights:
* We mainly used this time to clean up patchwork. We didn't keep exact statistics, but the number of patches was reduced from roughly 350 to
roughly
Quoted 1 line
250, and a significant number of patches have been reviewed and/or
reposted.
Quoted 2 lines
* There were a few important large series that were discussed and
eventually
Quoted 3 lines
applied.
* We have taken a decision on how to deal with atomic operations, with
missing
Related to atomics, has anyone looked at creating a patchset for those updates? If not, I'll take a look and put together a draft. I think I've got a pretty good idea of changes based on the developer meeting mins.
Thanks,
Matt
<snip>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141230/d3b5e44f/attachment.html>