Difference between revisions of "Buildroot:DeveloperDaysFOSDEM2018"

From eLinux.org
Jump to: navigation, search
(tar archive may differ)
m (Added Arnout (imagine a BR meeting without Arnout :-))
Line 29: Line 29:
# [[User:Jlijssen|Joris Lijssens]]
# [[User:Jlijssen|Joris Lijssens]]
# [[User:angeloc|Angelo Compagnucci]]
# [[User:angeloc|Angelo Compagnucci]]
# [[User:Arnout_Vandecappelle|Arnout Vandecappelle]]
== Meeting agenda ==
== Meeting agenda ==

Revision as of 09:26, 17 January 2018

Buildroot Developers Meeting, 5-6 February 2018, Brussels

The Buildroot Developers meeting is a 2-day event for Buildroot developers and contributors. It allows Buildroot developers and contributors to discuss the hot topics in the Buildroot development, work on patches, and generally meet each other, facilitating further online discussions. Attending the event is free, after registration.

Location and date

The next Buildroot Developers meeting will take place on February 5th and 6th 2018 in Brussels, right after the FOSDEM conference. The meeting will take place in Google offices, located Chaussée d'Etterbeek 180, 1040 Brussels, very close to the Schuman metro station.



We would like to thank our sponsors:

  • Google, providing the meeting location, with Internet connection, but also free lunch and refreshments for the meeting participants.

We are looking for sponsors to sponsor the dinner for the participants, and possibly travel expenses.


  1. Thomas Petazzoni
  2. Yann E. MORIN
  3. Peter Korsgaard
  4. Matt Weber
  5. Sam Voss
  6. Romain Naour
  7. Samuel Martin
  8. Valentin Korenblit
  9. Julien Boibessot
  10. Luca Ceresoli (Monday only)
  11. Thomas De Schampheleire
  12. Joris Lijssens
  13. Angelo Compagnucci
  14. Arnout Vandecappelle

Meeting agenda

Yann wrote: There is no real ordering here, except I tried to put important things that require an urgent fix first, whith other non-ciritical things later...

  • Local archive generation [Yann]
    • archives locally generated (from git/cvs/svn) depend on the tar version
    • http://lists.busybox.net/pipermail/buildroot/2018-January/211222.html
    • options:
      • investigating more those tar issues, and perhaps with the upstream tar folks, find a way of solving them
      • use a different archiving solution, that is more stable (cpio)
      • stop archiving, but then not clear how to support primary_site/backup_mirror
      • build our own tar
  • Namespace collision in package infra [Yann]
    • for example foo and foo-base will collide with variables $(1)_NAME and $(1)_BASE_NAME
    • already hit by:
      • alljoyn <-> alljoyn-base
      • alljoyn-tcl <-> alljoyn-tcl-base
      • perl-xml-sax <-> perl-xml-sax-base
    • so, we need to better separate the package part from the infra part, for example:
      • two underscores as a separator: FOO__NAME and FOO__BASE_NAME
      • a dot: FOO.NAME and FOO.BASE_NAME
  • Top-Level Parallel Build (TLPB) [Thomas]
    • How to trigger it?
      • option in menuconfig
      • automatic via top-level 'make -jN' ?
    • How to handle non-make tools (e.g. meson/ninja or mksquashfs...) that have their own parallel build that does not talk to a job-server?
  • Security Hardening [Adam?]
    • Validation approach post build that things took effect
    • How does it hook in to update the build flags? https://patchwork.ozlabs.org/patch/796080/
      • case to be checked for kernel, bootloaders et al.
    • Internal toolchain build tweaks (some std libs don't inherently get the build flags tacked on)
  • SELinux [Adam]
    • Test case approach(s) for compliance testing
  • LLVM/Clang [Romain/Valentin]
    • A short presentation about LLVM/Clang for Buildroot
  • Merge of staging/ and target/ [Yann]
    • only ever install packages once, in staging/
      • a bit faster
    • generate target/ from staging/
      • target-finalize copies staging/ to target/
      • then resumes with the current cleanups
    • staging contains everything and is not stripped
      • keeps debug symbols and the likes untouched