maple/prplos
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
65,344 Commits 1 Branch 0 Tags 238 MiB
C 55.7%
Makefile 17.6%
Perl 7.8%
Shell 6.9%
Roff 6.1%
Other 5.7%
e2109f88b1
Go to file
Paul HENRYS e2109f88b1
image: add defines for imagegenerator 
3 define instructions are created to prepare imagegenerator build
directory, to run binman and run swugenerator.
Those defines can be used with artifacts related variables to build
images with those tools.
A device could typically build images with those tools as such:

  define Device/mydevice
  ...
  IMG_GEN_DIR := $$(wildcard $$(BUILD_DIR_BASE)/hostpkg/imagegenerator-*)
  BINMAN_INPUT_tb341 := $$(IMG_GEN_DIR)/configs/binman/binman_mydevice.dts \
                        $$(KDIR)/u-boot-*/u-boot-nodtb.bin \
                        $$(KDIR)/u-boot-*/u-boot.dtb \
                        $$(KDIR)/vmlinux.gz \
                        $$(KDIR)/tmp/$$(DEVICE_IMG_PREFIX).dtb \
                        $$(BIN_DIR)/$(IMG_PREFIX)-secure-initramfs.cpio.gz \
                        $$(KDIR)/tmp/$$(DEVICE_IMG_PREFIX)-squashfs-fs.rootfs
  SWU_INPUT_tb341 := $$(IMG_GEN_DIR)/configs/swugenerator/sw-description_mydevice
  ARTIFACT/wgrtd159be_b_wav700-image.swu := imagegenerator-init $$(BINMAN_INPUT_mydevice) $$(SWU_INPUT_mydevice) | \
                                            binman binman_mydevice.dts | \
                                            swugenerator sw-description_mydevice
  ARTIFACTS := mydevice-image.swu
  ...
  endef

Implements: PCF-2354
Tracked-by: FEAT-29
Signed-off-by: Paul HENRYS <paul.henrys_ext@softathome.com>
2026-06-23 10:56:32 +02:00
.devcontainer/ci-env
.github CI: labeler: Add stm32 target 2024-11-28 18:49:21 +00:00
.gitlab profiles: mxl_x86_osp_tb341_v2: enable imagegenerator target package 2026-06-23 10:56:21 +02:00
.testbed ci: cdrouter: switch USP testing from STOMP to MQTTv5 as primary MTP 2026-04-21 16:00:15 +01:00
.vscode meta: VS Code: add "Git: Always Sign Off" setting 2024-10-03 17:18:51 +02:00
config image: add the implementation to support the secure initramfs 2026-06-22 18:24:25 +02:00
include image: add defines for imagegenerator 2026-06-23 10:56:32 +02:00
LICENSES
package fstools: drop use of parent_dev 2026-06-23 10:04:20 +02:00
profiles profiles: mxl_x86_osp_tb341_v2: add support for encrypted and signed SMD 2026-06-23 10:56:31 +02:00
scripts scripts: gen-secure-initramfs: convert absolute symlinks into relative ones 2026-06-23 10:04:24 +02:00
target kernel: move kernel-6.6 file to linux/generic directory 2025-07-31 15:27:59 +00:00
toolchain toolchain: glibc: Update glibc 2.38 to recent HEAD 2025-07-27 19:47:26 +02:00
tools tools: checksec.sh: fix build breakage caused by wrong PKG_MIRROR_HASH 2025-07-31 15:30:00 +00:00
.gitattributes
.gitignore ci: cram: add DHCPv4 Force option cram tests 2026-06-02 17:59:31 +01:00
.gitlab-ci.yml ci: release,testbed: OSPv2: make firmware filenames UPDK 9.2.3 compliant 2026-01-29 10:46:42 +00:00
BSDmakefile
Config.in
COPYING
feeds.conf.default feeds.conf.default: pin to latest openwrt-24.10 branch states 2025-07-31 15:29:59 +00:00
Makefile build,base-files: propagate prplOS version into build artifacts 2025-07-31 15:18:10 +00:00
README.md README: replace "MacOSX" with "macOS" 2024-04-01 18:46:30 +02:00
rules.mk build: add comments to makefiles 2024-11-28 18:47:03 +00:00

README.md

OpenWrt logo

OpenWrt Project is a Linux operating system targeting embedded devices. Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developers, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.

Sunshine!

Download

Built firmware images are available for many architectures and come with a package selection to be used as WiFi home router. To quickly find a factory image usable to migrate from a vendor stock firmware to OpenWrt, try the Firmware Selector.

If your device is supported, please follow the Info link to see install instructions or consult the support resources listed below.

An advanced user may require additional or specific package. (Toolchain, SDK, ...) For everything else than simple firmware download, try the wiki download page:

Development

To build your own firmware you need a GNU/Linux, BSD or macOS system (case sensitive filesystem required). Cygwin is unsupported because of the lack of a case sensitive file system.

Requirements

You need the following tools to compile OpenWrt, the package names vary between distributions. A complete list with distribution specific packages is found in the Build System Setup documentation.

binutils bzip2 diff find flex gawk gcc-6+ getopt grep install libc-dev libz-dev
make4.1+ perl python3.7+ rsync subversion unzip which

Quickstart

  1. Run ./scripts/feeds update -a to obtain all the latest package definitions defined in feeds.conf / feeds.conf.default

  2. Run ./scripts/feeds install -a to install symlinks for all obtained packages into package/feeds/

  3. Run make menuconfig to select your preferred configuration for the toolchain, target system & firmware packages.

  4. Run make to build your firmware. This will download all sources, build the cross-compile toolchain and then cross-compile the GNU/Linux kernel & all chosen applications for your target system.

Related Repositories

The main repository uses multiple sub-repositories to manage packages of different categories. All packages are installed via the OpenWrt package manager called opkg. If you're looking to develop the web interface or port packages to OpenWrt, please find the fitting repository below.

  • LuCI Web Interface: Modern and modular interface to control the device via a web browser.

  • OpenWrt Packages: Community repository of ported packages.

  • OpenWrt Routing: Packages specifically focused on (mesh) routing.

  • OpenWrt Video: Packages specifically focused on display servers and clients (Xorg and Wayland).

Support Information

For a list of supported devices see the OpenWrt Hardware Database

Documentation

Support Community

  • Forum: For usage, projects, discussions and hardware advise.
  • Support Chat: Channel #openwrt on oftc.net.

Developer Community

License

OpenWrt is licensed under GPL-2.0