Fix unity builds after reintroduction of vfork

Boost.Process was being included before this flag was set. Seems safer
to set it in the build anyways.
This commit is contained in:
Robbert van der Helm
2021-06-22 19:00:21 +02:00
parent a3d34f8197
commit 15e271f70a
2 changed files with 2 additions and 3 deletions
+2
View File
@@ -42,6 +42,8 @@ compiler_options = [
# Disable the use of concepts in Boost.Asio until Boost 1.73 gets released
# https://github.com/boostorg/asio/issues/312
'-DBOOST_ASIO_DISABLE_CONCEPTS',
# Boost.Process's auto detection for vfork() support doesn't seem to work
'-DBOOST_POSIX_HAS_VFORK=1',
# We use an intrinsic to force flush-to-zero. SSE2 is always enabled in x86_64
# CPUs, but when we're compiling the 32-bit bitbridge we need to manually add
# this flag.
-3
View File
@@ -16,9 +16,6 @@
#include "utils.h"
// Boost.Process's auto detection for vfork() support doesn't seem to work
#define BOOST_POSIX_HAS_VFORK 1
#include <unistd.h>
#include <boost/dll/runtime_symbol_info.hpp>
#include <boost/process/io.hpp>