Community maintained packages for difos.
Currently only xml2-config is installed, for both the normal libxml2 package as well as the host package. The problem with that is that due to multilib considerations the build host may have xml2-config installed with a host triplet prefix, like x86_64-pc-linux-gnu-xml2-config (and xml2-config as a symbolic link to it). Gentoo for instance sets it up like this. Packages may actually search for a prefixed xml2-config before searching for xml2-config. An example would be Asterisk: checking for x86_64-pc-linux-gnu-xml2-config... /usr/bin/x86_64-pc-linux-gnu-xml2-config This then introduces wrong information into the build, for instance bad includes: ~/tmp/openwrt $ /usr/bin/x86_64-pc-linux-gnu-xml2-config --cflags -I/usr/include/libxml2 When the intention is to use OpenWrt's own (host) libxml2 one would like to see this output used instead: ~/tmp/openwrt $ ./staging_dir/hostpkg/bin/xml2-config --cflags -I/home/sk/tmp/openwrt/staging_dir/hostpkg/include/libxml2 This commit addresses this by installing xml2-config with a suitable prefix and creating a symbolic link xml2-config. This is done for both the host package and the normal package. The latter also needs this fix because the target may use the same triplet as the host system (for instance x86_64 cross-compiling for x86_64). Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net> |
||
---|---|---|
.circleci | ||
.github | ||
.keys | ||
admin | ||
devel | ||
fonts/dejavu-fonts-ttf | ||
ipv6/tayga | ||
kernel | ||
lang | ||
libs | ||
multimedia | ||
net | ||
sound | ||
utils | ||
.travis.yml | ||
.travis_do.sh | ||
CONTRIBUTING.md | ||
LICENSE | ||
README.md |
OpenWrt packages feed
Description
This is the OpenWrt "packages"-feed containing community-maintained build scripts, options and patches for applications, modules and libraries used within OpenWrt.
Installation of pre-built packages is handled directly by the opkg utility within your running OpenWrt system or by using the OpenWrt SDK on a build system.
Usage
This repository is intended to be layered on-top of an OpenWrt buildroot. If you do not have an OpenWrt buildroot installed, see the documentation at: OpenWrt Buildroot – Installation on the OpenWrt support site.
This feed is enabled by default. To install all its package definitions, run:
./scripts/feeds update packages
./scripts/feeds install -a -p packages
License
See LICENSE file.
Package Guidelines
See CONTRIBUTING.md file.