-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
msvc DLL workaround for templatized members #12
Comments
I think it might be possible to use clang-cl for Windows then.
…On Thu, Mar 7, 2019, 6:58 AM Nic30 ***@***.***> wrote:
The windows DLL build forbids the usage of the templates for members.
This is ridiculous as it says STL can not be used.
And there is probably no workaround.
http://www.unknownroad.com/rtfm/VisualStudio/warningC4251.html
The fact that everything have to be marked manually with dllimport/export
is smaller problem.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#12>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMZ_XIR7D0OaTPk2fbCa9mVTNlHMSoPks5vUEgQgaJpZM4bh_h7>
.
|
See https://clang.llvm.org/docs/MSVCCompatibility.html and http://blog.llvm.org/2018/11/30-faster-windows-builds-with-clang-cl_14.html The LLVM 8.0 release should happen quite soon, matter of days. In this case there are might be some problems with meson - mesonbuild/meson#4232 and mesonbuild/meson#4232 |
MSVC out of Visual Studio is complete disaster. |
And one funny thing, I was thinking that the current windows build does not work because there is some bug in impl. which appears only in windows. It turns out that mt19937 the random generator works differently under windows so the values in test does not match... |
The windows DLL build forbids the usage of the templates for members.
This is ridiculous as it says STL can not be used.
And there is probably no workaround.
http://www.unknownroad.com/rtfm/VisualStudio/warningC4251.html
The fact that everything have to be marked manually with dllimport/export is smaller problem.
The text was updated successfully, but these errors were encountered: