Skip to content

Commit 355a69c

Browse files
MarcoFalkePastaPastaPasta
MarcoFalke
authored andcommitted
Merge bitcoin#24558: build: explicitly disable Boost multi_index serialization
0d01272 build: don't use Boost multi_index serialization (fanquake) Pull request description: We don't use the serialization or archiving facilities of multi_index. So globally disable support, which gives a minor improvement in build time, i.e less preprocessing work, given we don't link any Boost libs. See: https://www.boost.org/doc/libs/1_78_0/libs/multi_index/doc/tutorial/creation.html > Serialization capabilities are automatically provided by just linking with the appropriate Boost.Serialization library module: it is not necessary to explicitly include any header from Boost.Serialization, apart from those declaring the type of archive used in the process. If not used, however, serialization support can be disabled by globally defining the macro BOOST_MULTI_INDEX_DISABLE_SERIALIZATION. Disabling serialization for Boost.MultiIndex can yield a small improvement in build times, and may be necessary in those defective compilers that fail to correctly process Boost.Serialization headers. ACKs for top commit: MarcoFalke: cr ACK 0d01272 Tree-SHA512: 87c664a2f142dc6b8f8598341f9829be3fda8cf614d73cc9a894c8033ee40c6daa9b50f4049ecb1f1e3aaf342568d9a5f5c65af1e04c36ee3a9cb46eca95767b
1 parent 79bd3d9 commit 355a69c

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

configure.ac

+3
Original file line numberDiff line numberDiff line change
@@ -1466,6 +1466,9 @@ if test x$want_boost = xno; then
14661466
AC_MSG_ERROR([[only libdashconsensus can be built without boost]])
14671467
fi
14681468

1469+
dnl we don't use multi_index serialization
1470+
BOOST_CPPFLAGS="$BOOST_CPPFLAGS -DBOOST_MULTI_INDEX_DISABLE_SERIALIZATION"
1471+
14691472
dnl Prevent use of std::unary_function, which was removed in C++17,
14701473
dnl and will generate warnings with newer compilers for Boost
14711474
dnl older than 1.80.

0 commit comments

Comments
 (0)