John Crispin
b06e5f3bf9
iremap is called with BUILD_DIR and with PKG_BUILD_DIR, never with STAGING_DIR. A header taken from the staging directory therefore reaches __FILE__ and the debug information with its absolute path, and the result depends on the directory the tree was built in. Measured in the published snapshot of lantiq/xway: mt76-connac-lib.ko, mt76x02-lib.ko and mt7925-common.ko hold /builder/shared-workdir/build/staging_dir/target-mips_24kc_musl/usr/include/mac80211/net/cfg80211.h That path is __FILE__ in .rodata, so the strip before the package is built cannot reach it and the module ships it. Map STAGING_DIR as well. Keep the staging_dir element in the replacement: the last element of STAGING_DIR and of BUILD_DIR carry the same name, so the bare name would make the two roots indistinguishable. The map of BUILD_DIR does not change, so only a path that leaks today changes. Verified with the target compiler on a header below a mapped directory: -ffile-prefix-map removes the absolute path from both __FILE__ and the debug information, -fmacro-prefix-map removes it from __FILE__ alone. The shipped half is __FILE__, so both variants cover it. A local build of mt76 also holds nine staging paths, but those are debug information: the build directory copy of mt76-connac-lib.ko is 653456 bytes with 13 debug sections and nine such paths, the shipped copy is 84688 bytes with none. They are named here so that the next reader does not take them for the same defect. Signed-off-by: John Crispin <john@phrozen.org>
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.8+ rsync subversion unzip which
Quickstart
-
Run
./scripts/feeds update -ato obtain all the latest package definitions defined in feeds.conf / feeds.conf.default -
Run
./scripts/feeds install -ato install symlinks for all obtained packages into package/feeds/ -
Run
make menuconfigto select your preferred configuration for the toolchain, target system & firmware packages. -
Run
maketo 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
#openwrton oftc.net.
Developer Community
- Bug Reports: Report bugs in OpenWrt
- Dev Mailing List: Send patches
- Dev Chat: Channel
#openwrt-develon oftc.net.
License
OpenWrt is licensed under GPL-2.0