From 9a00b8ccfef1d13088be2d76fefcb320c269732a Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Thu, 22 Jun 2017 13:24:59 +0200
Subject: Add extra support for symbol exporting in modularized projects

Since modules don't see each other's macros, we can use a single, keyword-
like macro for dll-exporting that is managed by the build system (so no
need for an "export" header). For example:

cxx.features.symexport = true

export __symexport void f ();
---
 build2/c/init.cxx | 1 +
 1 file changed, 1 insertion(+)

(limited to 'build2/c')

diff --git a/build2/c/init.cxx b/build2/c/init.cxx
index 3461086..159c0b8 100644
--- a/build2/c/init.cxx
+++ b/build2/c/init.cxx
@@ -264,6 +264,7 @@ namespace build2
         cm.tstd,
 
         false, // No C modules yet.
+        false, // No __symexport support since no modules.
 
         cast_null<process_path> (rs["pkgconfig.path"]),
         cast<dir_paths>         (rs[cm.x_sys_lib_dirs]),
-- 
cgit v1.1