From e6918187568dbd01842d8d1d2c808ce16a894239 Mon Sep 17 00:00:00 2001
From: Daniel Baumann <daniel.baumann@progress-linux.org>
Date: Sun, 21 Apr 2024 13:54:28 +0200
Subject: Adding upstream version 18.2.2.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
---
 .../tools/build/example/try_compile/Jamroot.jam    | 29 ++++++++++++++++++++++
 src/boost/tools/build/example/try_compile/foo.cpp  |  6 +++++
 src/boost/tools/build/example/try_compile/main.cpp |  8 ++++++
 3 files changed, 43 insertions(+)
 create mode 100644 src/boost/tools/build/example/try_compile/Jamroot.jam
 create mode 100644 src/boost/tools/build/example/try_compile/foo.cpp
 create mode 100644 src/boost/tools/build/example/try_compile/main.cpp

(limited to 'src/boost/tools/build/example/try_compile')

diff --git a/src/boost/tools/build/example/try_compile/Jamroot.jam b/src/boost/tools/build/example/try_compile/Jamroot.jam
new file mode 100644
index 000000000..3131e722e
--- /dev/null
+++ b/src/boost/tools/build/example/try_compile/Jamroot.jam
@@ -0,0 +1,29 @@
+
+# This example shows performing configure checks in B2,
+# e.g. to check for some system function or compiler quirk.
+
+# First, declare a metatarget that we'll try to build.
+obj foo : foo.cpp ;
+# Make it explicit so that it's only built if used by a configure check
+explicit foo ;
+
+# Declare a target that depends on configure check result.
+exe main
+    : main.cpp
+    # The check-target-builds invocation in requirements section will
+    # - build the specified metatarget
+    # - if it builds OK, add the properties in the second parameter
+    # - otherwise, add the properties in the third parameter
+    : [ check-target-builds foo : <define>FOO=1 : <define>FOO=0 ]
+    ;
+
+# To test this:
+#
+# 1. Build with "b2". You should see a "foo builds: yes" message, and running
+#    the produced executable will show that FOO is set to 1.
+# 2. Modify foo.cpp to contain a compile error, rebuild with
+#    "b2 -a --reconfigure". You should see a "foo builds: no" message, and running
+#    the produced executable should show that FOO is now set to 0.
+#
+# The output from the check is not shown on the console, instead it is
+# redirected to the bin/config.log file
diff --git a/src/boost/tools/build/example/try_compile/foo.cpp b/src/boost/tools/build/example/try_compile/foo.cpp
new file mode 100644
index 000000000..c9107f937
--- /dev/null
+++ b/src/boost/tools/build/example/try_compile/foo.cpp
@@ -0,0 +1,6 @@
+
+
+int foo()
+{
+   return 0;
+}
\ No newline at end of file
diff --git a/src/boost/tools/build/example/try_compile/main.cpp b/src/boost/tools/build/example/try_compile/main.cpp
new file mode 100644
index 000000000..12f64995b
--- /dev/null
+++ b/src/boost/tools/build/example/try_compile/main.cpp
@@ -0,0 +1,8 @@
+
+#include <iostream>
+using namespace std;
+
+int main()
+{
+    std::cout << "Foo: " << FOO << "\n";
+}
\ No newline at end of file
-- 
cgit v1.2.3