Build infrastructure update

1 files changed, 36 insertions, 0 deletions

diff --git a/print/export b/print/export
new file mode 100644
index 0000000..c96ae14
--- /dev/null
+++ b/print/export
@@ -0,0 +1,36 @@
+// file: print/export -*- C++ -*-
+
+#pragma once
+
+// Normally we don't export class templates (but do complete specializations),
+// inline functions, and classes with only inline member functions. Exporting
+// classes that inherit from non-exported/imported bases (e.g., std::string)
+// will end up badly. The only known workarounds are to not inherit or to not
+// export. Also, MinGW GCC doesn't like seeing non-exported function being
+// used before their inline definition. The workaround is to reorder code. In
+// the end it's all trial and error.
+
+#if defined(LIBPRINT_STATIC)         // Using static.
+#  define LIBPRINT_EXPORT
+#elif defined(LIBPRINT_STATIC_BUILD) // Building static.
+#  define LIBPRINT_EXPORT
+#elif defined(LIBPRINT_SHARED)       // Using shared.
+#  ifdef _WIN32
+#    define LIBPRINT_EXPORT __declspec(dllimport)
+#  else
+#    define LIBPRINT_EXPORT
+#  endif
+#elif defined(LIBPRINT_SHARED_BUILD) // Building shared.
+#  ifdef _WIN32
+#    define LIBPRINT_EXPORT __declspec(dllexport)
+#  else
+#    define LIBPRINT_EXPORT
+#  endif
+#else
+// If none of the above macros are defined, then we assume we are being used
+// by some third-party build system that cannot/doesn't signal the library
+// type. Note that this fallback works for both static and shared but in case
+// of shared will be sub-optimal compared to having dllimport.
+//
+#  define LIBPRINT_EXPORT            // Using static or shared.
+#endif