dumalogiya
/
openwrt
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
OpenWRT firmware for routers
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
19,255 Commits
2 Branches
0 Tags
653 MiB
Diff 68.3%
C 21%
Makefile 4.7%
Shell 2.3%
Roff 1.6%
Other 2%
 
 
 
 
 
 
v19.07.3_mercusys_ac12_duma
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e53afbbe64'
${ noResults }
Go to file
Jo-Philipp Wich e53afbbe64 introduce a USE_EXTERNAL_LIBC symbol which gets selected by EXTERNAL_TOOLCHAIN || NATIVE_TOOLCHAIN Currently we always assume uClibc if an external toolchain is used, this breaks for non-uClibc toolchains or even vanilla uClibc ones since they do not share the external librpc semantics as OpenWrt. Solve the problem by defining an abstract "EXTERNAL_LIBC" which packages might or might not depend on. 
SVN-Revision: 29689
 		13 years ago
docs kamikaze has been released long ago 14 years ago
include include: calculate md5sum over sorted kernel config symbol list and incorperate it into the kernel metapackage version, make kmods depend on this specific version. The aim of this change is to invalidate kmods which are built against a different kernel config on the opkg metadata level. Manual copying and insmod of custom *.ko files, e.g. for development purpose, is still possible. 13 years ago
package base-files: implement a --force option for sysupgrade to override image checks, useful to upgrade old ar71xx installations to current trunk ones 13 years ago
scripts scripts: add a script for generating fwupgrade config for the OM2P board 13 years ago
target ar71xx: refresh patches 13 years ago
toolchain introduce a USE_EXTERNAL_LIBC symbol which gets selected by EXTERNAL_TOOLCHAIN || NATIVE_TOOLCHAIN Currently we always assume uClibc if an external toolchain is used, this breaks for non-uClibc toolchains or even vanilla uClibc ones since they do not share the external librpc semantics as OpenWrt. Solve the problem by defining an abstract "EXTERNAL_LIBC" which packages might or might not depend on. 13 years ago
tools firware-utils/mktplinkfw: add TL-WR2543N/ND support 13 years ago
.gitignore .gitignore: Ignore Emacs editor generated files 13 years ago
BSDmakefile add missing copyright header 18 years ago
Config.in if CONFIG_BUILD_NLS is selected, compile uClibc with locale support 13 years ago
LICENSE finally move buildroot-ng to trunk 8 years ago
Makefile add a command for printing a cleaned up make target database - will be used to analyze package dependencies at some point 14 years ago
README remove bison requirement (see [10398] & [14900]) 14 years ago
feeds.conf.default Add xorg feed to feeds.conf.default 13 years ago
rules.mk rules.mk: provide a LIBGCC_A variable 13 years ago

README 

This is the buildsystem for the OpenWrt Linux distribution

Please use "make menuconfig" to configure your appreciated
configuration for the toolchain and firmware.

You need to have installed gcc, binutils, patch, bzip2, flex,
make, gettext, pkg-config, unzip, libz-dev and libc headers.

Simply running 'make' will build your firmware.
It will download all sources, build the cross-compile toolchain, 
the kernel and all choosen applications.

You can use scripts/flashing/flash.sh for remotely updating your embedded
system via tftp.

The OpenWrt system is documented in docs/. You will need a LaTeX distribution
and the tex4ht package to build the documentation. Type make -C docs/ to build it.

Building your own firmware you need to have access to a Linux, BSD or MacOSX system.
Cygwin will not be supported because of the lack of case sensitiveness.

Sunshine!
	Your OpenWrt Project
	http://openwrt.org