buildroot/package/flex/Config.in, branch 2017.11

flex: rework patches to avoid host/target difference

2017-10-11T21:51:47+00:00

Currently, the target and host flex packages do not behave the same in terms of patching: the target variant has a patch hook that disables building the programs (because they are not needed, and do not build on no-MMU platforms). However, this hook is obviously not executed for host-flex, because we really want the host flex binary to be built. In preparation for the introduction of out-of-tree package build, it is important that we don't do different things in the patch hooks for the target and host variant of a given package, because the source tree will be shared between the target and host builds. To solve this, we introduce a --disable-program configure option, through a patch to the flex configure.ac and Makefile.am. This patch makes the current 0001-flex-disable-documentation.patch no longer needed. Furthermore, building the documentation is a PITA: flex.1 depends on configure.ac and a few other files generated during the build. Touching flex.1 does not work, because automake will forcibly remove the files when its prerequisites are too old, so pre-requisites of flex.1 will always be more recent than flex.1. So, we add a patch that adds a --disable-doc configure option. Fixes: http://autobuild.buildroot.org/results/f70/f70b39632535bb9692d0a032166b2f4104532967/ http://autobuild.buildroot.org/results/525/52567afdfe7992b3518de0e01227ba14aa300f21/ [...] Signed-off-by: Thomas Petazzoni [yann.morin.1998@free.fr: - rebase on-top of master, - add patch to not build the documentation, because simply touching flex.1 is no longer enough. - keep install in target/, for shared builds ] Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Cc: Adrian Perez de Castro Cc: Arnout Vandecappelle Signed-off-by: Thomas Petazzoni

flex: use the new gettext logic

2017-07-04T23:27:25+00:00

This commit switches to use the new gettext logic, which involves: - using TARGET_NLS_DEPENDENCIES instead of hand-encoded dependencies on gettext/host-gettext - dropping BR2_PACKAGE_GETTEXT selection Signed-off-by: Thomas Petazzoni

flex: bump version to 2.6.4

2017-05-11T19:43:53+00:00

- 0001 patch removed. It doesn't apply on this version and is also not necessary since the AR binary is now handled correctly with AR = @AR@. - 0002 patch removed. It's already included in this release: https://github.com/westes/flex/commit/a5cbe929ac3255d371e698f62dc256afe7006466 - The flex project has moved to GitHub, so modify the URLs in both flex.mk and Config.in files. - The sed command over Makefile.in to prevent the flex binary to be built fails, so remove it. That logic has been moved to src/Makefile.in, and whenever we disable the flex binary to be built then the compilation fails when building the documentation because some bits require "../src/flex", which is the flex binary. We prevent building the flex binary and the documentation using a new patch. Signed-off-by: Vicente Olivert Riera Signed-off-by: Thomas Petazzoni

package: kill pointless text justification

2015-04-23T07:47:08+00:00

Signed-off-by: Gustavo Zacarias Acked-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

flex: remove deprecated binary in target

2015-01-25T23:21:35+00:00

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

flex: change config text of 'target binary' option

2014-01-21T20:57:43+00:00

The buildroot manual contains a list of deprecated items, with their config title text, and the location in the config menu. If the config text does not mention a package name, this can be confusing. For example, the symbol BR2_PACKAGE_FLEX_BINARY has as text: 'Install tool in the target', which outside of the flex context makes no sense at all. To make sure the deprecated packages list in the manual is understandable, rename the (deprecated) flex 'target binary' config option. Signed-off-by: Thomas De Schampheleire 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"

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