You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/* For Visual Studio 2012 global variable definitions */
#defineGLOBALVARDEF __declspec(dllexport)
#else
#defineGLOBALVARDEF
#endif
i think the canonical way to handle this is to use a define indicating a static build (and don't use the __declspec(dllexport) decorator if it is set), like so:
#ifdefFLITE_STATIC# defineGLOBALVARDEF#else# ifdefWIN32/* For Visual Studio 2012 global variable definitions */# defineGLOBALVARDEF __declspec(dllexport)
# else# defineGLOBALVARDEF# endif#endif
obviously, whoever wants to link flite statically, will then have to define FLITE_STATIC.
The text was updated successfully, but these errors were encountered:
umlaeute
added a commit
to umlaeute/flite
that referenced
this issue
Nov 8, 2022
it seems that it's impossible to create a
dll
that statically links against flite.the problem, is that for static builds you shouldn't export variables with
__declspec(dllexport)
, as found inflite/include/flite.h
Lines 68 to 73 in 6c9f20d
flite/src/synth/flite.c
Lines 47 to 52 in 6c9f20d
i think the canonical way to handle this is to use a define indicating a static build (and don't use the
__declspec(dllexport)
decorator if it is set), like so:obviously, whoever wants to link flite statically, will then have to define
FLITE_STATIC
.The text was updated successfully, but these errors were encountered: