Do everything as normal user, don’t use root user or sudo!
Do not build in a directory that has spaces in its full path
write all command line commands for build system commands in a terminal window opened in the <buildsystem root> directory, e.g. ~/source/ if you wrote the git clone command in your home folder (default terminal location)

1. Update the sources.
2. Update and install package feeds.
3. Configure the firmware image you want to obtain.
4. Start the build. (automatically compile toolchain, cross-compile sources, package packages, and generate an image ready to be flashed).
5. Proceed with the firmware flashing instructions: Factory install or Sysupgrade –

Typical actions:

1. run make menuconfig and set target;
2. run make defconfig to set default config for build system and device;
3. run make menuconfig and modify set of package;
4. run make download (download all dependency source files before final make, enables multi-core compilation);
5. run scripts/diffconfig.sh >mydiffconfig (save your changes in the text file mydiffconfig);

The build system configuration interface handles the selection of the target platform, packages to be compiled, packages to be included in the firmware file, some kernel options, etc.
Start the build system configuration interface by writing the following command:

make menuconfig

This will update the dependencies of your existing configuration automatically, and you can now proceed to build your updated images.

You will see a list of options. This list is really the top of a tree. You can select a list item, and descend into its tree.

To search for the package or feature in the tree, you can type the “/” key, and search for a string. This will give you its locations within the tree.

For most packages and features, you have three options: y, m, n which are represented as follows:

• pressing y sets the <*> built-in label
  This package will be compiled and included in the firmware image file.
• pressing m sets the <M> package label
  This package will be compiled, but not included in the firmware image file. (E.g. to be installed with opkg after flashing the firmware image file to the device.)
• pressing n sets the < > excluded label
  The source code will not be processed.

When you save your configuration, the file <buildroot dir>/.config will be created according to your configuration.

When you open menuconfig you will need to set the build settings in this order (also shown in this order in menuconfig‘s interface):

1. Target system (general category of similar devices)
2. Subtarget (subcategory of Target system, grouping similar devices)
3. Target profile (each specific device)
4. Package selection
5. Build system settings
6. Kernel modules

Select your device’s Target system first, then select the right Subtarget, then you can find your device in the Target profile‘s list of supported platforms.

• UCI defaults
• Adding a new device
• Creating Packages
• Multicast DNS Daemon
• The Procd System Manager
• RPC daemon
• uBus IPC/RPC System
• netifd (Network Interface Daemon) – Technical Reference
• Vagrant-based automatic setup for a LEDE build environment in a VM
• Including custom files/configurations in a firmware image
• Build for multiple targets from the same build tree (build environments aka config swapping)
• “Hello, world!” for LEDE – Developing your first application
• Building image for UEFI based system
• defining firmware partitions for all DTS targets