Revert "Move context and coroutine"
This reverts commit 6be1787fdc13405fa9daa6755c28534bbcaa7458.
openbmc/openbmc#3720 tracks the issue we've been having with the latest
poky update. For now we're going to have to revert it which means we
need to go back to handling the older boost.
Lets revert this so we go back to not minimizing our boost library which
will cause a bit larger library in flash but allow us to support both
the old and new boost packaging.
(From meta-phosphor rev: 3ee1f9df23ab04871297676c265dfcf0a8db38f4)
Change-Id: Ib45de998931142ea74dffddafd960b7513717a18
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
diff --git a/meta-phosphor/recipes-support/boost/boost_%.bbappend b/meta-phosphor/recipes-support/boost/boost_%.bbappend
index fabb7f5..b614346 100644
--- a/meta-phosphor/recipes-support/boost/boost_%.bbappend
+++ b/meta-phosphor/recipes-support/boost/boost_%.bbappend
@@ -1,10 +1,12 @@
#This is largely to improve our build times by not building or installing
-#modules that OpenBMC does not use by our coding standard. Chrono and Thread
-#should not be relied directly, but are required dependencies of context and
-#coroutine at build time. See the relevant portion of the openbmc coding
-#standard with regards to boost libraries
+#modules that OpenBMC does not use by our coding standard. Another thing to
+#note is that for most targets, coroutine and context libraries are also added
+#with a BOOST_LIBS_append_<platform> for most targets. Chrono/Thread should not
+#be relied directly, but are required dependencies of context and coroutine.
+#See the relevant portion of the openbmc coding standard with regards to boost
+#libraries
#
#https://github.com/openbmc/docs/blob/master/cpp-style-and-conventions.md#boost
#
-BOOST_LIBS_openbmc-phosphor = "chrono context coroutine thread"
+#BOOST_LIBS_openbmc-phosphor = "chrono thread"