Add support for a project directory
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 13 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 13 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Buildroot] [PATCH 00/13] Add support for a project directory
Quoted 8 lines · Thomas Petazzoni
Arnout,
Quoted 4 lines · Arnout Vandecappelle
Quoted 3 lines
All what this stuff is adding can already be done with the current Buildroot, by putting the configuration files in a board/something/foo directory, and adjusting the Buildroot configuration.
Quoted 7 lines
Quoted 3 lines
It doesn't even have to be in a board/something/foo directory, it can
easily be out of tree. The only problem is that you have to write down a fairly long path for each of the relevant config options.Come on, it's just something like:
$(TOPDIR)/../myproject/linux.config
Except that I want the flexibility to have the buildroot tree in a different
place (e.g. a shared directory). That said, it's still easy:
$(MYPROJECT_DIR)/linux.config
The issue is that it has to be filled in in many places. I'm just trying
to make it easier. And I'm also trying to establish a default policy, so it's easier for users to understand how to use buildroot.
[snip]
Quoted 2 lines
I still don't get what this patch set adds that you can't do with the existing Buildroot infrastructure.
As I wrote several times already, all of this can already be done with the
current infrastructure (with one exception: 'make savedefconfig' saving to a different file than 'defconfig'). It just provides simpler defaults.
[snip]
Quoted 3 lines
I really would prefer to _document_ how to properly use the existing Buildroot infrastructure to cleanly separate custom stuff from Buildroot, rather than introducing more mechanisms on top of it.
Well, that documentation would be:
- Define all the custom paths to $(PROJECT_DIR)/foo.config
- Write a Makefile that does 'make -C <buildroot_dir> PROJECT_DIR=<project_dir>'
And people will wonder why all those paths aren't already
$(PROJECT_DIR)/foo.config by default.
[snip]
Quoted 4 lines
It's not a question of diffstat. It's a question of "is this mechanism easy to grasp for newcomers and can it be immediately understood" and "does this mechanism adds any value over what Buildroot already provides"?
IMHO, it is.
I could do the following: I write a section in the documentation about
how to save your customization. This section will have two alternatives:
in-tree configuration or out-of-tree configuration. Then I can post a second patch that removes the parts of the out-of-tree documentation that become unnecessary when this patch series is implemented.
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
the most annoying problems are
not solved. So I really do prefer to keep things as it is: people have to use version control systems to keep their changes cleanly separated from the base Buildroot version.Version control doesn't really solve it, in my experience.
Why so?
Mainly because customers for some obscure reason want to use svn.
[snip]
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286540 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