]> code.ossystems Code Review - openembedded-core.git/commit
bjam-native: don't do debug builds
authorRoss Burton <ross@burtonini.com>
Tue, 29 Sep 2020 22:16:37 +0000 (23:16 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Tue, 6 Oct 2020 22:11:47 +0000 (23:11 +0100)
commit66d583d1b2bc54cac278c30b5dbc9fde016eb6ee
tree6e88150416bf01b788608a5cd6d52033876c95ba
parent8dfaf5cd4eb5c8e352e7833ec47db1a14ea58b47
bjam-native: don't do debug builds

Previously this recipe was changed to do debug builds because otherwise insane
warns that the binary is already stripped.

However, debug builds for boost.build also pass -O0.  It turns out that given
how large Boost is (or, how bad boost.build is) doing a release build with -O3
knocks a third off the walltime for a Boost package in my test, mainly by reducing
how long it spends deciding that nothing needs to be rebuilt in do_install:

  PKG      TASK        ABSDIFF  RELDIFF  WALLTIME1 -> WALLTIME2
  boost    do_install  -330.7s   -69.2%     477.6s -> 146.9s
  boost    do_compile    -7.1s    -2.7%     269.3s -> 262.2s

Replace debug mode with INSANE_SKIP=already-stripped.

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-support/boost/bjam-native_1.74.0.bb
meta/recipes-support/boost/files/0001-Build-debug-version-of-bjam.patch [deleted file]
meta/recipes-support/boost/files/0001-build.sh-use-DNDEBUG-also-in-debug-builds.patch [deleted file]