OpenWrt Forum Archive

Topic: An introduction to Buildroot-ng

The content of this topic has been archived between 25 Apr 2018 and 29 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

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.


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?

(Last edited by kukodajanos on 24 Feb 2011, 23:25)

- build OpenWRT Image = this is what you want.
- build OpenWRT SDK   = you do not need that.
- build OpenWRT Toolchain  = you do not need that either

(Last edited by Orca on 25 Feb 2011, 23:30)

I am Ross Mathis. I am health care expert in 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

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


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?) is blank but I found this...

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


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...


(Last edited by ninjaef on 20 Feb 2018, 17:39)

The discussion might have continued from here.