aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-support/boost/boost.inc
AgeCommit message (Collapse)Author
2016-01-11boost: update to 1.60.0Lukas Bulwahn
Due to the version update to 1.59.0, the two patches previously backported in this recipe are now dropped. The actual status of the arm-intrinsics.patch (reported with Upstream-Status: Backport) is unknown to the committer, and hence, that patch is kept in the recipe, even if it is possibly not required anymore. A deeper analysis is required to determine need and status of that patch. Second, boost 1.59.0 provides a new library, called timer, which is packaged as further library in the boost recipe. The update to boost 1.60.0 required no further changes beyond changing the checksum hashes. Third, on PPC architectures, qemuppc & mpc8315e-rdb [1] (tested by Ross Burton), the boost test library with the vanilla version 1.60.0 fails with: | gcc.compile.c++ bin.v2/libs/test/build/aca09349fdb84d131321425f6c3a38ed/execution_monitor.o | In file included from [...]/tmp/sysroots/mpc8315e-rdb/usr/include/fenv.h:114:0, | from [...]/tmp/sysroots/mpc8315e-rdb/usr/include/c++/5.3.0/fenv.h:36, | from ./boost/detail/fenv.hpp:97, | from ./boost/test/execution_monitor.hpp:64, | from ./boost/test/impl/execution_monitor.ipp:31, | from libs/test/src/execution_monitor.cpp:16: | ./boost/test/impl/execution_monitor.ipp: In function 'unsigned int boost::fpe::enable(unsigned int)': | ./boost/test/impl/execution_monitor.ipp:1383:7: error: expected id-expression before '(' token | ::feclearexcept(BOOST_FPE_ALL); | ^ | ./boost/test/impl/execution_monitor.ipp: In function 'unsigned int boost::fpe::disable(unsigned int)': | ./boost/test/impl/execution_monitor.ipp:1420:7: error: expected id-expression before '(' token | ::feclearexcept(BOOST_FPE_ALL); | ^ The commit f50e7bc9fed323c5705c0ed992c03e80eeec1dd6 from the boostorg/test github repository (branch: develop) [2] addresses that issue, but it was not merged in the 1.60.0 release. This commit adds this upstream-accepted patch, which was created by: `git checkout f50e7bc9fed323c5705c0ed992c03e80eeec1dd6 && git format-patch -1` [1] http://lists.openembedded.org/pipermail/openembedded-core/2016-January/114844.html [2] https://github.com/boostorg/test/commit/f50e7bc9fed323c5705c0ed992c03e80eeec1dd6 Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-01-07boost: ensure boost to remain an empty metapackageLukas Bulwahn
To ensure that boost remains an empty metapackage after version updates, we explicitly require boost files to be empty. If new libraries exist after a version update of the boost recipe, bitbake will emit a warning at the do_package task. For example, at the version update from 1.58.0 to 1.59.0, the new timer library is indicated with: WARNING: QA Issue: boost: Files/directories were installed but not shipped in any package: /usr/lib/libboost_timer.so.1.59.0 Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install. boost: 1 installed and not shipped files. [installed-vs-shipped] Ross Burton suggested this improvement on the openembedded-core mailing list during review of the boost recipe version update [1]. [1] http://lists.openembedded.org/pipermail/openembedded-core/2015-December/114314.html Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-12-09boost: adjust hard-coded path after python3 upgradeLukas Bulwahn
When using `PACKAGECONFIG = "python"` in the boost recipe, `bitbake boost` fails at do_compile with: ./boost/python/detail/wrap_python.hpp:50:23: fatal error: pyconfig.h: No such file or directory compilation terminated. This issue is due to the recent version upgrade from python 3.4 to 3.5: 701ec1977ced1bb08461e6de98b4f63d21cba8a6 python3: Upgrade from 3.4.3 to 3.5 The boost.inc file modifies the boost build configuration with a path containing the python3 major version, which is hard-coded in the boost.inc file. Hence after the python3 update, the path points to the outdated location and it needs to be updated to the new location. This issue was unrevealed by an internal continuous integration system for the meta-ros application layer. Further manual bisecting lead to the critical commit 701ec1977ced1bb08461e6de98b4f63d21cba8a6. Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-11-25boost.inc: remove unused parameter from get_boost_parallel_make()Andre McCurdy
The bb parameter seems to have been accidentally left behind after: http://git.openembedded.org/openembedded-core/commit/?id=1ff36aaec25a7ee89514366fe484345e8d1d7b64 Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-08-09boost: add python3 supportAndreas Müller
* Both - python/python3 - libs are build by adding 'python' to PACKAGECONFIG but are packed into separate packages * Indention was wrong in __anonymous() Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-07-16boost: add dirs flag to boostconfig taskRoss Burton
The boostconfig task expects to run in ${S} so make that explicit. Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-05-27boost: extend libraries with log and randomLukas Bulwahn
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-05-15boost: properly fix do_boostconfig re-executionMartin Jansa
* it was partially fixed in: commit 291e20a51544c640d07767d1dc32d762f4370f41 Author: Venkata ramana gollamudi <ramana.gollamudi@huawei.com> Date: Fri Apr 13 11:42:46 2012 +0000 Subject: boost: fix re-execution of task but with disadvantage that when CXX or *FLAGS variables were changed it was continuing to use old values * just remove the line before appending it with current values to fix that Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-05-03boost/libxslt: Enable nativesdk to unbreak <bitbake universe>Li Zhou
When run <make universe.fetchall>, the make will be broken because nativesdk-boost and nativesdk-libxslt don't exist. nativesdk-boost is depended by nativesdk-curlpp. nativesdk-libxslt is depended by nativesdk-python-lxml. In condition that meta-openembedded is compiled in. Add nativesdk building for boost and libxslt. Signed-off-by: Li Zhou <li.zhou@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-01-28boost: Avoid to use local host configurationFabien Proriol
Signed-off-by: Fabien Proriol <fabien.proriol@jdsu.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-12-25boost : Add the atomic and chrono libraries to the build.Philip Balister
Inspection of buildhistory shows no existing libraries changed and the atmoic and chrono libraries are packaged individually. Signed-off-by: Philip Balister <philip@balister.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-10boost: fix build when ${PARALLEL_MAKE} contains '-l'Enrico Scholz
The '-l' option which is valid for GNU make (--> limit by load) has a different meaning in bjam (--> limit maximum execution time) and will break very likely the build. Keep only the the '-l' option when passing PARALLEL_MAKE options to bjam. Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
2014-08-23boost: Upgrade to 1.56.0Saul Wold
Rebase boostconfig to handle moved user-config file Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-04-25Globally replace 'base_contains' calls with 'bb.utils.contains'Otavio Salvador
The base_contains is kept as a compatibility method and we ought to not use it in OE-Core so we can remove it from base metadata in future. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-03-17boost: Pass CFLAGS, CXXFLAGS and LDFLAGS correctly into boost.buildMike Crowe
The compileflags and linkflags do_boostconfig puts into user-config.jam are having no effect. According to http://www.boost.org/boost-build2/doc/html/bbv2/reference/tools.html the correct syntax would be <compileflags>"the flags" <linkflags>"the flags". Since the flags specified were having no effect they can't be necessary and can be safely removed. We should be passing ${CFLAGS}, ${CXXFLAGS} and ${LDFLAGS} instead so that users of the recipe can pass arbitrary flags as they choose. Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-02Replace one-line DESCRIPTION with SUMMARYPaul Eggleton
A lot of our recipes had short one-line DESCRIPTION values and no SUMMARY value set. In this case it's much better to just set SUMMARY since DESCRIPTION is defaulted from SUMMARY anyway and then the SUMMARY is at least useful. I also took the opportunity to fix up a lot of the new SUMMARY values, making them concisely explain the function of the recipe / package where possible. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2013-09-24boost: set up PACKAGECONFIG for boost-python libraryLukas Bulwahn
Until now, the comment in the boost.inc file suggested to enable the boost-python library by uncommenting some lines in that file. Using the new PACKAGECONFIG feature, boost-python can now be added optionally without need to modify the file or copying those lines into a bbappend file. Furthermore, we obtain the python version by inheriting python-dir instead of fixing the python version in this file. This commit is motivated by the need in the meta-ros layer, as discussed in the issue #145 of the meta-ros issue tracker [1]. [1] https://github.com/bmwcarit/meta-ros/pull/145 Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-06boost: adding serialization to BOOST_LIBSLukas Bulwahn
Since its initial commit from the classic OpenEmbedded repository in 43e94412c45b4b79485a64010c76d89b245bb235, serialization was commented out, reportedly due to some issue with powerpc in the boost version 1.36. In the classic OpenEmbedded repository, serialization has been added again since version 1.4x. The commit removes the outdated comment and adds serialization to the BOOST_LIBS after testing `bitbake boost` and bitbaking some applications using boost from the meta-ros layer for qemuppc. Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-22boost: fix build when PARALLEL_MAKE is not setMarko Lindqvist
It was passing "None" to bjam, which then parsed it as unknown build target. Signed-off-by: Marko Lindqvist <cazfi74@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-27boost: Limit PARALLEL_MAKE by -j 64Martin Jansa
* greater paralelism isn't supported by bjam and causes segfault or ignoring -j * PARALLEL_MAKE was enabled for boost in http://git.openembedded.org/openembedded-core/commit/?id=9b9cfc1dfe5e3b8f89b7a8508537166d0f23935e Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-03-29boost: Add real native supportStefan Herbrechtsmeier
The current boost recipe only creates the bjam build tool during a native run and thereby is not usable for other native recipes that depend on a boost library. Split out the build tool into its own bjam-native recipe and add real native support to the boost recipe. Additionally replace the boost-native with bjam-native in the DEPENDS. This allows recipes to depend on native boost librarties without increase of the build time for other use cases. Native compilation of bzip2 isn't working and therefore disabled. Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-21boost: Upgrade 1.51 -> 1.52Khem Raj
Drop hash_enums.patch which is already applied upstream Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-10boost: Use PARALLEL_MAKE for bjamSamuel Stirtzel
Like make, bjam accepts the parameter -jX for multithreaded execution do_install also profits from this setting Tested with a quad core 64bit intel cpu (with hyperthreading) PARALLEL_MAKE="j16" $ time bitbake boost before: real 14m37.433s user 7m40.785s sys 4m30.109s after: real 7m11.979s user 12m10.694s sys 2m47.078s Also fixes tab indention Signed-off-by: Samuel Stirtzel <s.stirtzel@googlemail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-13boost: Activate zlib and bzip2 because they now work.Denis 'GNUtoo' Carikli
This patch is needed for making wesnoth(will be sumbited in meta-games) work. [RP: Add missing bzip2 dependency] Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-02recipes-support: 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. NOTE: There were 2 errors in libcap.inc, the BUILD_LDFLAGS_virtclass_native should be BUILD_LDFLAGS_virtclass-native (the "_" should be "-"), otherwise it doesn't work, and the value was: "-Wl,rpath=...", this is incorrect, it shoudl be: "-Wl,-rpath=..." (lacked a - ), but we don't need this line, since it is already in the default BUILD_LDFLAGS. Remove it and we don't need to bump the PR since we just removed a unused line. [YOCTO #3297] Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-07-19Remove a number of unneeded import os/bb callsRichard Purdie
The bb and os modules are always imported so having these extra import calls are a waste of space/execution time. They also set a bad example for people copy and pasting code so clean them up. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-04-26boost: Ensure we use our user-config.jam fileSaul Wold
This change ensures we use the user-config.jam Configuration that we created and will not use anything from the user's home directory. [YOCTO #2302] Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-04-24boost: set python-root correctlyTasslehoff Kjappfot
[RP: Fix whitespace] Signed-off-by: Tasslehoff Kjappfot <tasskjapp@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-04-13boost: fix re-execution of taskVenkata ramana gollamudi
After building boost package, re-execution of boostconfig task followed by re-execution of compile task is giving following error "error: duplicate initialization of gcc with the following parameters" during compilation It is because multiple entries of gcc are being added during boostconfig re-execution there by failing the compilation. The patch fixes adding multiple "Using gcc" entries into /tools/build/v2/user-config.jam [Yocto #2194] Signed-off-by: Venkata Ramana Gollamudi <ramana.gollamudi@huawei.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-13boost: Correct license name BSL-1 -> BSL-1.0Richard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-05meta: Convert getVar/getVarFlag(xxx, 1) -> (xxx, True)Richard Purdie
Using "1" with getVar is bad coding style and "True" is preferred. This patch is a sed over the meta directory of the form: sed \ -e 's:\(\.getVar([^,()]*, \)1 *):\1True):g' \ -e 's:\(\.getVarFlag([^,()]*, [^,()]*, \)1 *):\1True):g' \ -i `grep -ril getVar *` Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-01-19boost: refactor packages for staticdevSaul Wold
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-01-05native.bbclass: Fix variable remapping coverageRichard Purdie
When looking for RDEPENDS to process, bitbake iterates through PACKAGES *and* PN. Since native.bbclass sets PACKAGES to be empty, its pointless remapping the list of PACKAGES since this does nothing. There is a problem since *_${PN} are used by bitbake but not remapped by the native.bbclass class extension code. This changes the code to remap _${PN} in both expanded and unexpanded forms. As a result of this, various surprising dependencies are uncovered and the patch rectifies those. These are real bugs since they're injecting unneeded (unremapped) dependencies into the dependency chain. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-01-03boost: Update to 1.48 and Clean upsSaul Wold
There were 2 "BJAM_OPTS =" in the .bb and .inc, the .inc was being overwritten and the ICU dependency was not removed correctly. Do some clean-up including moving install_append into do_install directly. Finally the BJAM_EXTRAS += "threading=multi" was not setting set correctly, set it on the BUILD spec line Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-12-13boost : Do not use icu when building boost.Philip Balister
Without this, boost needs to build icu to create images using boost regex. RP inidicated he would rather disable icu, than add an extra dependency to the recipe. Signed-off-by: Philip Balister <philip@balister.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-12-08OECore license fixes: meta/*Elizabeth Flanagan
This is a quick audit of only the most obviously wrong licenses found within OECore. These fixes fall into four areas: - LICENSE field had incorrect format so that the parser choked - LICENSE field has a license with no version - LICENSE field was actually incorrect - LICENSE field has an imaginary license that didn't exist This fixes most of the LICENSE warnings thrown, along with my prior commit adding additional licenses to common-licenses and additional SPDXLICENSEMAP entries. HOWEVER..... there is much to be done on the license front. For a list of recipes with licenses that need obvious fixing see: https://wiki.yoctoproject.org/wiki/License_Audit That said, I would suggest another license audit as I've found enough inconsistencies. A good suggestion is when in doubt, look at how openSuse or Gentoo or Debian license the package. Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
2011-11-26getVar/setVar cleanupsRichard Purdie
Complete the bb.data.getVar/setVar replacements with accesses directly to the data store object. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-11-16boost: Update to 1.47.0 & CleanupSaul Wold
Removed boost-jam-native since it was an older version no incompatible with boost 1.47. Modified boost to use BBCLASSEXTEND native for the bjam native binary. Removed older unused patches. Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>