aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/flex/flex.inc
AgeCommit message (Collapse)Author
2014-05-01Add texinfo.bbclass; recipes that use texinfo utils at build-time inherit it.Max Eliaser
The class itself currently does nothing. The idea is to mark all recipes that make use of the texinfo utilities. In the future, this class could be used to suppress the generation/formatting of documentation for performance, explicitly track dependencies on these utilities, and eliminate Yocto's current dependency on the host system's texinfo utilities. Signed-off-by: Max Eliaser <max.eliaser@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-02-14flex: enable ptest supportChong Lu
Install flex test suite and run it as ptest. Signed-off-by: Chong Lu <Chong.Lu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-11-20flex: fix m4 issue on targetLaurentiu Palcu
Flex needs m4 to run (see below) and, since the create_wrapper introduces a bash dependency on target, give the path to m4 binary in the configure command line. Snippet from the flex documentation: "The macro processor m4 must be installed wherever flex is installed. <...> m4 is only required at the time you run flex." [YOCTO #5329] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-09-04flex: Only use create_wrapper for native and nativesdkOlof Johansson
The create_wrapper functions of utils.bbclass cause implicit dependencies on bash, which may not be suitable for deployment on target. Besides, the wrapper doesn't seem to be necessary on target. Signed-off-by: Olof Johansson <olofjn@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-02-01Flex: use proper m4 binary on targetMarcin Juszkiewicz
flex tries to execute: /data/oe/build/tmp-eglibc/sysroots/x86_64-linux/usr/bin/m4 As workaround you can: mkdir -p /data/oe/build/tmp-eglibc/sysroots/x86_64-linux/usr/bin/ ln -s /usr/bin/m4 /data/oe/build/tmp-eglibc/sysroots/x86_64-linux/usr/bin/ So this is a bug how OE builds flex. flex tries to execute: /data/oe/build/tmp-eglibc/sysroots/x86_64-linux/usr/bin/m4 As workaround you can: mkdir -p /data/oe/build/tmp-eglibc/sysroots/x86_64-linux/usr/bin/ ln -s /usr/bin/m4 /data/oe/build/tmp-eglibc/sysroots/x86_64-linux/usr/bin/ So this is a bug how OE builds flex. https://bugs.launchpad.net/linaro-aarch64/+bug/1106865 (From OE-Core rev: 215bcc780d9bc4a7d96d1c706db80abe4ef659dd) Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-02recipes-devtools: replace virtclass-native(sdk) with class-native(sdk)Robert Yang
The overrides virtclass-native and virtclass-nativesdk are deprecated, which should be replaced by class-native and class-nativesdk. [YOCTO #3297] Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-04-04flex.inc: inherit gettext class instead of adding gettext to DEPENDS directlyKhem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2011-01-07flex-native: create a wrapper script for sstate installationKevin Tian
flex-native encodes M4 staging path in its binary, which breaks sstate installation in a new build environment. Use create_wrapper to create a wrapper script which explicitly set M4 environmental variable to the new path Signed-off-by: Kevin Tian <kevin.tian@intel.com>
2010-12-16recipes-devtools: Add Summary informationMark Hatle
Add Summary information and update Descripts as necessary. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2010-08-27Major layout change to the packages directoryRichard Purdie
Having one monolithic packages directory makes it hard to find things and is generally overwhelming. This commit splits it into several logical sections roughly based on function, recipes.txt gives more information about the classifications used. The opportunity is also used to switch from "packages" to "recipes" as used in OpenEmbedded as the term "packages" can be confusing to people and has many different meanings. Not all recipes have been classified yet, this is just a first pass at separating things out. Some packages are moved to meta-extras as they're no longer actively used or maintained. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>