-
Notifications
You must be signed in to change notification settings - Fork 1
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
.NET 4.0 client profile support #2
Comments
The namespace syntax xx:yy::zz is unique to C++ 17. The only Microsoft compilers that support it are Visual C++ 2015 and 2017. The alternative in C++ 2013 would be to create individual namespace scopes like this: namespace zuki { namespace io { namespace compression { Does this answer your question? If you search and replace "namespace zuki::io::compression" with "namespace zuki { namespace io { namespace compression {" and fix the single end brace in each file to be tripled, I think that should let most of it build under VC 2013. There are probably other VC 2015 unique features that I used, I wasn't considering backwards compatibility ... Let me know if I misunderstood! |
The question is about official support for .NET 4 Client profile. Its not a big deal to build it against VS2013 so why not... |
The library will not compile for .NET 4.0 as-is, it uses some .NET 4.5.x+ specific features. .NET 4.0 Client Profile is also not a "supported" target for C++/CLI, but you can hack the .vcxproj to use it if you're so inclined : https://stackoverflow.com/questions/8154000/how-to-target-the-net-4-client-profile-for-c-cli-under-visual-studio-2010 |
I'm not C++ expert but i made such build myself, there are nothing special in plain C code (original codecs) which requre .NET 4.5.2
Unfortunally in my build I replace "zuki::io::compression" with "zuki_io_compression" otherwise get huge errors from VS2013 compiler... Since I'n not C++ developer I can't adapt this code for VS2013 C++ compiler syntax except replace "zuki::io::compression" with "zuki_io_compression"...
The text was updated successfully, but these errors were encountered: