Project

General

Profile

Actions
Copy link

Action Item #775

open

Check if migration to Buildroot recommended customizations is warranted

Added by Hammel almost 5 years ago. Updated 10 days ago.

Status:
In Progress
Priority:
Immediate
Assignee:
Hammel
Category:
04 - Root File System
Target version:
3.0 - Corrino
Start date:
06 Jul 2020
Due date:
% Done:

30%

Estimated time:
Severity:
04 - Low

Description

See https://buildroot.org/downloads/manual/manual.html#customize

We might want to change the way we add customizations to the build, if it makes it easier to rebuild.

Actions
Copy link
 #1

Updated by Hammel about 2 years ago

  • Priority changed from High to Urgent
  • Target version changed from 2.0 - Harkonnen to 3.0 - Corrino
Actions
Copy link
 #2

Updated by Hammel almost 2 years ago

  • Priority changed from Urgent to Immediate
  • Severity changed from 02 - High to 04 - Low
Actions
Copy link
 #3

Updated by Hammel over 1 year ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 30

This section of the developer documentation is of interest.

The rest of the options aren't really necessary for PiBox, unless Buildroot makes some incompatible changes upstream. But I'll deal with those if that situation arises.

Actions
Copy link
 #4

Updated by Hammel 10 days ago

It's much simpler to use BR2_ROOTFS_OVERLAY instead of the customize package because there is nothing to remove on rebuilds. The overlay is applied right before making the image files and isn't copied into Buildroot's target tree.

I need to switch to this method from the customize method as it will simplify the makefiles and rebuilds.

Actions
Copy link

Also available in: Atom PDF