John Crispin
a0b036985a
A configure run spends its time on the compiler invocations behind its checks, not on the shell. tools/m4 runs the compiler 633 times and takes 24 seconds. ccache does not help, because it refuses to cache an autoconf conftest compile at all; it counts these separately as "Autoconf compile/link" under its uncacheable calls. A package that sets PKG_CONFIGURE_CACHE or HOST_CONFIGURE_CACHE keeps a config.cache under tmp/, so a package that is cleaned and built again reads the answers instead of running the checks. The configure stage of tools/m4 drops from 24.5 s to 1.5 s. dirclean removes tmp/, so a full reset of the tree starts from cold answers. A package has to opt in, because a cache is only correct for a configure script that keeps its side effects outside the AC_CACHE_VAL body. ncurses appends -D_XOPEN_SOURCE and -D_DEFAULT_SOURCE to CPPFLAGS inside that body, so a cached run restores the value, skips the append, and then fails to compile wcwidth. ncurses_cfg.h is identical in both cases; the difference is in the generated Makefile. The path covers everything else that changes an answer. A target package is keyed on the toolchain directory, which carries the gcc version. A host package is keyed on the version string of the host compiler, because autoconf cannot detect a new compiler behind an unchanged name; gcc 14 turned an implicit function declaration into an error and changed many answers that way. Both are keyed on a hash of the configure arguments and the build flags, and autoconf refuses a cache written with different flags on top of that. A cached program path outlives a wipe of staging_dir, so ac_cv_path_ and ac_cv_prog_ answers are dropped when the cache loads and configure searches PATH again. Without that, a cache written before staging_dir held sed pins /usr/bin/sed for good. A search runs no compiler, so this costs nothing that matters. The cache arrives through a site script rather than --cache-file, so a hand written configure script never sees a new argument. The site script removes the file of the previous arguments, so a different configuration gets a cold cache instead of an autoconf error. It also unsets the variable, and make exports it for the configure stage alone, so a nested configure run keeps its own cache. Set CONFIGURE_CACHE_DIR to keep the cache elsewhere, or to the empty string to run every check again. Host builds now read a site script on Linux as well. Before this change only Darwin had one. CONFIG_SITE holds one path name: autoconf before 2.70 reads the whole value as that one name, so a second path would silence both scripts. It names the cache script alone, and the cache script loads the site script of the architecture from CONFIG_SITE_BASE. 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