buildroot/package/gob2, branch 2016.02

gob2: add a hash file

2015-12-12T13:30:28+00:00

Signed-off-by: Vicente Olivert Riera Signed-off-by: Thomas Petazzoni

gob2: remove deprecated target package

2015-01-25T23:02:58+00:00

It's been deprecated for a year now so remove the target variant. Also rename patch to new naming convention. Signed-off-by: Gustavo Zacarias Acked-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

gob2: bump to version 2.0.20

2014-01-16T08:08:22+00:00

Signed-off-by: Jerzy Grzegorek Signed-off-by: Peter Korsgaard

gob2: rename patches to add sequence numbers

2014-01-16T08:08:16+00:00

Signed-off-by: Jerzy Grzegorek Signed-off-by: Peter Korsgaard

gob2: bump to version 2.0.19

2014-01-14T22:05:37+00:00

Signed-off-by: Jerzy Grzegorek Signed-off-by: Peter Korsgaard

deprecated handling: introduce BR2_DEPRECATED_SINCE_xxxx_xx

2014-01-10T14:03:53+00:00

In order to keep better track of when a feature got deprecated, and hence when it can be removed, a new set of symbols BR2_DEPRECATED_SINCE_xxxx_xx is introduced. These symbols are automatically selected when BR2_DEPRECATED is selected, and thus are transparent to the user. A deprecated feature will no longer depend on BR2_DEPRECATED directly, but rather on the appropriate BR2_DEPRECATED_SINCE_xxxx_xx. If that symbol does not yet exist, it has to be created in Config.in. When removing a deprecated feature, one should also check whether this was the last feature using the BR2_DEPRECATED_SINCE_xxxx_xx symbol, in which case the latter can be removed from Config.in. A followup patch will make sure the overview is added to the list of deprecated features in the manual, so that a buildroot core developer can easily determine which features to remove in a given development cycle. Signed-off-by: Thomas De Schampheleire Acked-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

package: deprecate some more development tools

2013-12-27T18:54:05+00:00

Since some time, we have removed the support to build a toolchain for the target, and therefore the support for several development tools on the target. This commit deprecates a few additional development tools: m4, bison, flex and gob2. For flex, we retain the ability to build libfl, we only deprecated the ability to build the flex binary itself. The original motivation for this patch is that m4 is causing build issues in some configurations, but there isn't really much incentive to fix this package for the target, since it is not really useful for embedded Linux systems. Bison, Flex and Gob2 are deprecated because they are reverse dependencies of m4. Signed-off-by: Thomas Petazzoni Acked-by: "Yann E. MORIN"

libglib2: needs MMU support

2013-11-22T11:14:33+00:00

Fixes http://autobuild.buildroot.net/results/2e0/2e032c6e44e10f2912935715741c3680a19b9b51/ Signed-off-by: Thomas De Schampheleire Signed-off-by: Peter Korsgaard

Config.in files: add missing dependencies to toolchain option comments

2013-11-10T22:59:57+00:00

When a package A depends on config option B and toolchain option C, then the comment that is given when C is not fulfilled should also depend on B. For example: config BR2_PACKAGE_A depends on BR2_B depends on BR2_LARGEFILE depends on BR2_WCHAR comment "A needs a toolchain w/ largefile, wchar" depends on !BR2_LARGEFILE || !BR2_WCHAR This comment should actually be: comment "A needs a toolchain w/ largefile, wchar" depends on BR2_B depends on !BR2_LARGEFILE || !BR2_WCHAR or if possible (typically when B is a package config option declared in that same Config.in file): if BR2_B comment "A needs a toolchain w/ largefile, wchar" depends on !BR2_LARGEFILE || !BR2_WCHAR [other config options depending on B] endif Otherwise, the comment would be visible even though the other dependencies are not met. This patch adds such missing dependencies, and changes existing such dependencies from depends on BR2_BASE_DEP && !BR2_TOOLCHAIN_USES_GLIBC to depends on BR2_BASE_DEP depends on !BR2_TOOLCHAIN_USES_GLIBC so that (positive) base dependencies are separate from the (negative) toolchain dependencies. This strategy makes it easier to write such comments (because one can simply copy the base dependency from the actual package config option), but also avoids complex and long boolean expressions. Signed-off-by: Thomas De Schampheleire Acked-by: Arnout Vandecappelle (Essensium/Mind) (untested) Signed-off-by: Peter Korsgaard

Config.in files: unify comments of toolchain option dependencies

2013-10-14T20:45:57+00:00

This patch lines up the comments in Config.in files that clarify which toolchain options the package depends on. Signed-off-by: Thomas De Schampheleire Signed-off-by: Peter Korsgaard