Difference between revisions of "Buildroot Mainline integration"

Latest revision as of 19:38, 7 February 2018

Page under construction... Informations on this page are not guaranteed !!

Changes since BR version used in armadeus 3.x

default packages

• uClibc: 0.9.29 -> 0.9.30 -> 0.9.33.2
• gcc: 4.2.1-> 4.4.5 -> 4.7.2
• busybox: 1.6.2 -> 1.20.2 -> 1.21
• U-Boot: 2012.10 -> 2013.04

build directories

• build_arm_xxx/ project_build_xxx/ toolchain_build_arm_xxx/ have been removed and replaced by output/:

build  host  images  stamps  target  toolchain

configs

• buildroot default configs are now stored in buildroot/configs/apfxx_defconfig and no more in buildroot/target/device/armadeus/apfxx/apfxx_defconfig
• uClibc config should be named with version number to not overwrite the old one -->

buildroot/target/device/armadeus/apf27/uClibc-0.9.30.config.arm

• idem for U-Boot config:

buildroot/target/device/armadeus/apf27/apf27-u-boot-2010.03.h

Changes since BR version used in armadeus 4.x

• TBDL

How to use recent BR in armadeus

• checkout a recent clean GIT view and before any other command edit the main Makefile to change the BUILDROOT_VERSION flag from 2013.11 to the wanted BR version.
  • comment line 30
  • uncomment the line 29 and modify it
• then you can use it as old BR:

$ make apf27_defconfig
$ make

• you may need to create a new patches directory:

patches/buildroot/201x.xx/

Patches that could be sent to BR

(Some will require some cleanup)

Instructions

• Patches to port: patches/buildroot/2013.11
• when working on a patch mark it with:
  • ** <span style="color:orange">'''In progress'''</span> ~~~~
  • --> In progress JulienB 14:14, 9 November 2010 (UTC)
• Strike the one that are no more needed:
  • 000-xxxxxxx.patch
• Write OK in bold green and your name (automatic with 4x'~') when corresponding patch has been ported:
  • ** <span style="color:green">'''OK'''</span> ~~~~
  • --> 000-xxxxxxx.patch: OK JulienB 07:06, 21 October 2010 (UTC)
• How to:
  • get a BR git
  • try to apply patch with patch -p1 --dry-run < patch_name.patch
  • when it applies remove --dry-run, commit, generates patch with GIT and send it to BR

Status for BR2013.11 patches

1 to 52

72 to 100

123 to 200

168 to 188

189 to 208

209 to 215

How to send patches to BR

(see the Buildroot - How to contribute page)

• GIT should be installed and configured on your PC like stated here
• clone Buildroot GIT:

 $ git clone git://git.busybox.net/buildroot buildroot_git_dev/ (TBDL)
 $ cd buildroot_git_dev/

• take patch from Armadeus:

 $ cp /path_to_armadeus_bsp/patches/buildroot/2011.05/0xx-name.patch .

• create a branch to work (here my_work):

 $ git branch my_work
 $ git checkout my_work
 Switched to branch 'my_work'
 $ git branch
   master
 * my_work

• try patch:

 $ patch -p1 --dry-run < 0xx-name.patch

• if it works, apply it for real:

 $ patch -p1 < 0xx-name.patch

• list changes:

 $ git status

• do some more changes if needed and then save them:

 ... do changes ...
 $ git add files_changed
 ... test changes ...
 $ git commit -m "Summary of your work"

• generate patch to send to BR:

 $ git format-patch -M master.. -s

• this will give:

 0001-Summary_of_your_work.patch

• send patch to BR (check https://buildroot.org/downloads/manual/manual.html#submitting-patches before ;-) ):

 $ git send-email --from=xxx.xxx@xxx.xx --to=buildroot@busybox.net --smtp-server=smtp.xxx.xx 0001-Summary_of_your_work.patch

• depending on the feedbacks from BR, modify your patch:

 ... do changes ...
 $ git diff
 $ git add files_changed
 $ git commit --amend
 $ git format-patch -M master..my_work -s

• adds version inside [PATCH] ex: [PATCH v2]
• adds comments after ---, ex:

From a2413db058ac3c515337102690ba12a746831f7e Mon Sep 17 00:00:00 2001
From: Julien Boibessot <julien.boibessot@armadeus.com>
Date: Wed, 19 Oct 2011 10:39:26 +0200
Subject: [PATCH v2] Add libmodbus package


Signed-off-by: Julien Boibessot <julien.boibessot@armadeus.com>
---
 Changes since v1:
  - Took Yegor Yefremov remarks about "call AUTOTARGETS' into account.

 Based on previous work of Marek Belisko and comments of Thomas Petazzoni.

 package/Config.in              |    1 +
 package/libmodbus/Config.in    |    8 ++++++++
 package/libmodbus/libmodbus.mk |   11 +++++++++++
 3 files changed, 20 insertions(+), 0 deletions(-)
 create mode 100644 package/libmodbus/Config.in
 create mode 100644 package/libmodbus/libmodbus.mk

diff --git a/package/Config.in b/package/Config.in
......

• retry ;-)

After patch has been accepted

• Delete branch & co:

$ rm xxxx.patch
$ git checkout master
$ git branch -D my_work

$ git branch
* master

Links

• BR online doc