On 28/05/16 15:55, Ben Greear wrote:
On 05/27/2016 11:10 PM, David Lang wrote:
On Fri, 27 May 2016, Ben Greear wrote:
On 05/27/2016 02:46 AM, Karl Palsson wrote:
gree...@candelatech.com wrote:
From: Ben Greear <gree...@candelatech.com>
The idea is to be able to allow newbies to easily build images
for common hardware. These images should be user-friendly,
including luci and other tools that may aid debugging and use
of the platform.
Signed-off-by: Ben Greear <gree...@candelatech.com>
---
buildme.sh | 76
+++++++++++++++++++++++++++++++++++
buildme_targets/x86_64/diffconfig.txt | 26 ++++++++++++
2 files changed, 102 insertions(+)
create mode 100755 buildme.sh
create mode 100644 buildme_targets/x86_64/diffconfig.txt
While I've written similar scripts for helping colleagues
bootstrap a build, I'm not entirely convinced that adding more
piles of shell script to the build tree is necessarily an
improvement, if the goal is helping people build an image that
suits them.
My goal is more to have an easy way to build a useful image
that should work for most people. Lots of people and organizations
have their own forks and scripts, and it seems much of the changes
are just
tweaks how to the core project is built. If we can bring some
of this into the main tree maybe that will help everyone work
closer to upstream code.
rather than making a bunch of scripts for specific models, how about
some scripts that will let you build from a downloaded .config (yes,
you can do this manually, but it could be greatly simplified)
Then people can build the latest code from a much larger set of
configs, and tweak a config and then use it over time to build newer
versions.
My idea was to store these configs in the git repo and have an easy
way for users
to find and use them.
The x86_64 is just a starting point. I think there could be a large
amount of different
configs, for different boards, different needs, etc. Basically,
everyone using openwrt has
a unique config...I think a lot of that could be re-used and shared.
Thanks,
Ben
The ImageBuilder should be covering this scenario.
Conor
_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
