diff options
Diffstat (limited to 'libodb-sqlite/odb/sqlite/details/export.hxx')
-rw-r--r-- | libodb-sqlite/odb/sqlite/details/export.hxx | 86 |
1 files changed, 86 insertions, 0 deletions
diff --git a/libodb-sqlite/odb/sqlite/details/export.hxx b/libodb-sqlite/odb/sqlite/details/export.hxx new file mode 100644 index 0000000..c0903ae --- /dev/null +++ b/libodb-sqlite/odb/sqlite/details/export.hxx @@ -0,0 +1,86 @@ +// file : odb/sqlite/details/export.hxx +// license : GNU GPL v2; see accompanying LICENSE file + +#ifndef ODB_SQLITE_DETAILS_EXPORT_HXX +#define ODB_SQLITE_DETAILS_EXPORT_HXX + +#include <odb/pre.hxx> + +#ifdef ODB_COMPILER +# error libodb-sqlite header included in odb-compiled header +#elif !defined(LIBODB_SQLITE_BUILD2) +# ifdef _MSC_VER +# include <odb/sqlite/details/config-vc.h> +# else +# include <odb/sqlite/details/config.h> +# endif +#endif + +// 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. + +#ifdef LIBODB_SQLITE_BUILD2 + +#if defined(LIBODB_SQLITE_STATIC) // Using static. +# define LIBODB_SQLITE_EXPORT +#elif defined(LIBODB_SQLITE_STATIC_BUILD) // Building static. +# define LIBODB_SQLITE_EXPORT +#elif defined(LIBODB_SQLITE_SHARED) // Using shared. +# ifdef _WIN32 +# define LIBODB_SQLITE_EXPORT __declspec(dllimport) +# else +# define LIBODB_SQLITE_EXPORT +# endif +#elif defined(LIBODB_SQLITE_SHARED_BUILD) // Building shared. +# ifdef _WIN32 +# define LIBODB_SQLITE_EXPORT __declspec(dllexport) +# else +# define LIBODB_SQLITE_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 LIBODB_SQLITE_EXPORT // Using static or shared. +#endif + +#else // LIBODB_SQLITE_BUILD2 + +#ifdef LIBODB_SQLITE_STATIC_LIB +# define LIBODB_SQLITE_EXPORT +#else +# ifdef _WIN32 +# ifdef _MSC_VER +# ifdef LIBODB_SQLITE_DYNAMIC_LIB +# define LIBODB_SQLITE_EXPORT __declspec(dllexport) +# else +# define LIBODB_SQLITE_EXPORT __declspec(dllimport) +# endif +# else +# ifdef LIBODB_SQLITE_DYNAMIC_LIB +# ifdef DLL_EXPORT +# define LIBODB_SQLITE_EXPORT __declspec(dllexport) +# else +# define LIBODB_SQLITE_EXPORT +# endif +# else +# define LIBODB_SQLITE_EXPORT __declspec(dllimport) +# endif +# endif +# else +# define LIBODB_SQLITE_EXPORT +# endif +#endif + +#endif // LIBODB_SQLITE_BUILD2 + +#include <odb/post.hxx> + +#endif // ODB_SQLITE_DETAILS_EXPORT_HXX |