Age | Commit message (Collapse) | Author |
|
Rename the variable name to PKG_HASH and use a
256 Bit SHA checksum to verify the integrity of
distfiles. While there do some housekeeping and
remove old packages.
|
|
to avoid namespace collisions in some packages, rename TOPDIR.
Sorry you need to make cleandir && make prereq && make
|
|
|
|
|
|
|
|
|
|
update. library is split out from mesa-lib
|
|
|
|
|
|
when C++ compiler is disabled by user, do not allow to
compile packages , which require a C++ compiler.
Older libtool unnecessary checks for c++ tools, so
regenerate autotool stuff.
|
|
- libtool do not pass -fstack-protector while linking,
but this is required to successfully link libraries or
executables with SSP
- pass LDFLAGS for non-libtool packages
|
|
|
|
Make configuration of new targets cheap.
Just add a new file in target/arch/sys-enabled/foo.
See other files for syntax. While doing runtime tests
with the new infrastructure I've updated a lot of other
stuff:
- gcc 4.5.2
- uClibc 0.9.32-rc1 (NPTL)
- strongswan, php, miredo, parted, util-linux-ng, e2fsprogs
I promise, this is the last big fat commit this year ;)
|
|
you can now choose between specific embedded systems like PC Engines
ALIX boards, Foxboard, .. or between generic architecture support like
x86, x86_64, mips, ...
This does reduce the overhead of duplicate configuration files in target
directory. Now qemu, toolchain and ibm x40 support is combined in one target
directory target/x86. Distinguishing between hardware profiles happens
via menu based configuration. (CPU choice for kernel, CFLAGS for package
building, ..). We will see if this is the right direction.
|
|
use hardware profiles, instead of extra target dirs.
fix dependencies.
|
|
packages to latest stable upstream version
|
|
depmaker and pkgmaker is replaced by C programs. scan-pkgs.sh will be replaced
by another mechanism. scan-pkgs.sh is needed to recognize package flavour changes,
so that a package is rebuild.
Generation of meta-data is a lot faster now.
Fix or add new PKG variables to fulfill the needs of the new programs.
Documentation will follow as soon as it is stable.
|
|
|
|
|
|
|
|
|