staging/lynxis/include/package.mk, branch reboot

build: use -iremap feature to replace FILE absolute path names in packages with ones relative to $(BUILD_DIR)

2016-01-25T15:49:31Z

improves reproducible builds Signed-off-by: Felix Fietkau SVN-Revision: 48489

build: use directory name instead of PKG_NAME for staging files and package metadata

2016-01-04T01:33:32Z

Signed-off-by: Felix Fietkau SVN-Revision: 48110

buildroot: move hardening options into separate file

2015-06-20T17:37:18Z

Signed-off-by: Steven Barth SVN-Revision: 46070

package.mk: replicate SSP and relro in both CFLAGS and LDFLAGS

2015-06-18T10:48:28Z

Signed-off-by: Steven Barth SVN-Revision: 46035

include: clean package staging dir files before configure

2015-05-26T09:17:13Z

This is required to allow packages to ship libraries with a different API. Previously the linker would favor the old shared libraries in STAGING_DIR instead of the just compiled ones in PKG_BUILD_DIR. Avoid that problem by clearing the package staging files right after prepare. Signed-off-by: Jo-Philipp Wich SVN-Revision: 45759

build: include variant name in STAMP_INSTALLED

2015-04-03T18:33:25Z

Signed-off-by: Felix Fietkau SVN-Revision: 45253

include: remove trailing whitespaces

2015-03-29T07:29:18Z

Signed-off-by: Luka Perkov SVN-Revision: 45127

build: clean up sitefiles, make them per-arch

2015-03-28T13:38:34Z

Signed-off-by: Felix Fietkau SVN-Revision: 45090

build: define STAMP_CONFIGURED recursively

2015-03-21T21:47:53Z

Defining STAMP_CONFIGURED statically caused it not to reflect changes to PKG_CONFIG_DEPENDS made after including package.mk, like the additional options added by feeds.mk for all packages. Furthermore, as STAMP_CONFIGURED_WILDCARD was already defined recursively, the patsubst in its definition would never match, and in consequence, the stamps were never removed. This caused packages not to be rebuilt when they should have been. Signed-off-by: Matthias Schiffer SVN-Revision: 44927

build: explicitly unexport CONFIG_SITE

2015-01-18T00:37:18Z

On systems with CONFIG_SITE in the environment (e.g. OpenSUSE) make will export the CONFIG_SITE set in include/package.mk by default. This will cause host builds to get the target site configuration, leading to all kinds of weirdness (wrong pointer size, wrong endianess). Fix this by explicitly unexporting CONFIG_SITE. The explicit export for the target builds overrides the unexport, so the target builds will still correctly get the site config. Signed-off-by: Matthias Schiffer SVN-Revision: 44019