-
Notifications
You must be signed in to change notification settings - Fork 74
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
Visual Studio 2015 C++ compiler cannot compile certain constexpr constructions #60
Comments
I think this might be because VS2015 might not implement all the features of constexpr http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3652.html There are a few other declarations I had to make inline. |
Yes, your right. VS2015 is not 100% C++14 compatible, but it still supported by Microsoft until October 2025. I will have a look. |
If it helps, this is the patch i had to use: |
Visual Studio 2015 is mostly C++14 compatible, but some constexpr constructions are not supported. Add a helper macro to make it possible to use VS2015 to compile CharLS 2.1.0. See also #60
Hi Mark, |
Are you 100% sure that compiles? Without the We can patch things up with conda-forge, and I can try out your patchc in a bit. |
inline is used and needed for the free functions. In portable_anymap_file.h it is not needed as class member functions declared inside a class are auto inline. It compiles on my local VS 2015 setup. I was already thinking of adding an Azure CI pipeline to ensure older versions of VS are auto tested, will give that task some more prio. |
Hmm ok. Thanks for the detailed explanation. I didn't know about autoinline Yeah moving to Azure is OK, you just have to want to buy into yet an other platform. I'm trying to build with your patch now conda-forge/charls-feedstock#3 (comment) It seems to have worked. |
You can close if you want. |
charls/src/util.h
Line 121 in 20ed9e9
I'm getting an error on this line of code when trying to compile with VS 14.1
https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=106870&view=logs&j=2cc45e14-23e3-52d7-b33a-8c2744410b97&t=21c44aa7-1ae3-5312-cacc-7f19fefc82f4&l=688
This build will likely get destroyed, so I'm copying the error message
The text was updated successfully, but these errors were encountered: