26 (edited by kukodajanos 2011-02-24 22:25:44)

Re: An introduction to Buildroot-ng

Orca wrote:

A simple "make" should suffice. This will compile the toolchain, and the toolchain will then crosscompile the sources into binaries. Then packages will be built. And then the firmware will be built out of the packages. So, as long as you do not already have a current toolchain, let him compile one.

http://wiki.openwrt.org/doc/howto/firmware.compile

Hey!

I know that a simple make is enough, but before in the configuration menu, in menuconfig, you can set this 3 options, and I am not sure, what is the aim of them, which actually I need.

So I am incurious, because i want to upload remotely my firmware to my router, so before I do that, I should modify the firewall option, if I would later access it via ssh.

Maybe somebody has experience?

27 (edited by Orca 2011-02-25 22:30:53)

Re: An introduction to Buildroot-ng

- build OpenWRT Image = this is what you want.
- build OpenWRT SDK   = you do not need that. http://en.wikipedia.org/wiki/SDK
- build OpenWRT Toolchain  = you do not need that either

http://tothszabi.info/

Re: An introduction to Buildroot-ng

I am Ross Mathis. I am health care expert in Onlinecareprost.com. I love travelling and visited 25 countries. We supply eye solutions globally. Women's who want thick, dense and long eyelashes - We are here for you! You can contact on us or email & website
You can contact on us or email & website

Re: An introduction to Buildroot-ng

I am Ross Mathis. I am health care expert in Onlinecareprost.com. We supply eye solutions globally. Women's who want thick, dense and long eyelashes- We are here for you!

Re: An introduction to Buildroot-ng

Hi

31 (edited by ninjaef 2018-02-20 16:39:43)

Re: An introduction to Buildroot-ng

mbm wrote:

...
As an example, if a new kernel is released, a simple change to one of the Makefiles will download the latest kernel, patch it to run on the embedded platform and produce a new firmware image -- there's no work to be done trying to track down an unmodified copy of the existing kernel to see what changes had been made, the patches are already provided and the process ends up almost completely transparent. T...
...

Great writeup.

I'm no expert with OpenWrt and I'm unfamilar with the buildroot architecture on disk, although I read scaprs of pages but some of the links fail (guess this is part of the LEDE merge?)

https://openwrt.org/about/toolchain is blank but I found this...
https://wiki.openwrt.org/doc/techref/buildroot

1. So my question please is what change is needed to backport a later kernel, what option in which .mk

And

2. I have a git repo, accessed using https/http, and would like to know the "good practice" way of using that codebase as a replacement for an existing package. The package in question is kmod-mwlwifi. In other words, how should I use the git repo - a URL ref in a .mk that will override current config, or clone, or download and put source in a specific 'src' or 'dl' directory, or something else...

thanks

OpenReach EchoLife HG612 rev.3B VDSL modem (stock fw)
Linksys WRT3200ACM (various fw images being tried out currently)