-
Notifications
You must be signed in to change notification settings - Fork 20
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
Support for Windows 64-bit using Visual Studio 2013 Update 4 #77
Comments
Can you explain why As for the rest of it, it seems like their C++11 support is broken? It seems like its attempting to pick the wrong template instantiation multiple times. It seems it can't decide to pick the var-arg one, and instead grabs the non var-arg version (which is wrong). Do the notes for that VS release say anything about its support for Variable Argument templates? Maybe they aren't finished in that version? |
With respect to snprintf, Microsoft implemented _snprintf. See this post on Stackoverflow... http://stackoverflow.com/questions/2915672/snprintf-and-visual-studio-2010 According to the C++11 feature list, variadic templates are supported in VS 2013... https://msdn.microsoft.com/en-us/library/hh567368.aspx#featurelist I'm not surprised there are issues in this area. |
Ok, so ms still hasn't fixed the _ prepended posix api bugs yet, sigh. As for the template support, it used to work, so I'm not sure what is up with that. Is there a newer vs snapshot you can use? |
I'm actively debugging and testing with LuaGlue as it is currently blocking my development. I'll keep you posted as to what I find. I'm up to date with the latest supported Visual Studio 2013... Microsoft Visual Studio Professional 2013 Installed Version: Professional Team Explorer for Visual Studio 2013 06177-179-0133563-02988 Visual Basic 2013 06177-179-0133563-02988 Visual C# 2013 06177-179-0133563-02988 Visual C++ 2013 06177-179-0133563-02988 Visual F# 2013 06177-179-0133563-02988 Visual Studio 2013 Code Analysis Spell Checker 06177-179-0133563-02988 Portions of International CorrectSpell™ spelling correction system © 1993 by Lernout & Hauspie Speech Products N.V. All rights reserved. The American Heritage® Dictionary of the English Language, Third Edition Copyright © 1992 Houghton Mifflin Company. Electronic version licensed from Lernout & Hauspie Speech Products N.V. All rights reserved. Application Insights Tools for Visual Studio Package 1.0 Common Azure Tools 1.3 Microsoft Azure Mobile Services Tools 1.3 NuGet Package Manager 2.8.50926.663 PowerShell Tools 1.3 PreEmptive Analytics Visualizer 1.2 Windows Phone 8.1 SDK Integration 1.0 |
I've been following a blog post from MS's VS team, about snapshots, where they release work in progress versions of the compiler ahead of actual VS releases. If it's possible for you to try that, that could help figure out if its a VS C++11 support issue, or something LuaGlue is doing wrong. |
I just updated to the latest code on this repo. It doesn't come close to compiling with my tool chain... 1> MpLua.cpp |
Granted, it's not causing the internal compiler error. I'll work on getting this code to compile in VS 2013 and see how far I get. |
Oh god, its conflicting against my stack:: and std::stack, and I see a "in class initializer" error that should be easily fixable.. "should". but that might cause some duplicate symbol errors when linking if used in multiple files. so I'm wondering what to do there. These aren't problems in gcc, and I presume not with clang either. |
Rename to lg_stack? |
yeah, the stack problem isn't a real problem. rename, or namespace. but really, if gcc and clang can do it, so can msvc, but they choose not to? Really, they have REALLY incomplete support for C++11, and its frustrating. |
Multi-platform development is definitely challenging. Sometimes you need to work with lowest common denominator. I've worked through quite a few of the compiler issues by making a few small tweaks to the code and renaming stack to lg_stack. The next set of issues, I'm looking at now. They are a little more interesting. Maybe you have some insight... 1>------ Build started: Project: UPF, Configuration: Debug x64 ------ |
Multiplatform development can sure be challenging, but I haven't guaranteed support for MSVC due to its lack of support for full C++11. I'd like to support it if possible, but its looking like it isn't possible to support most versions of MSVC. The applyTuple problem seems to be MSVC not picking the correct template, or ignoring the var-arg template all-together. I have absolutely no idea how to work around that, if its even possible, without writing separate code just for MSVC that doesn't use vararg template magic, which completely defeats the purpose of LuaGlue. |
Hopefully, in the future VS will support C++11 better. I'll investigate some other libraries that might work with it today. Thanks for all of your help. |
Sorry I couldn't be more help. |
I'm attempting to use LuaGlue in a project that is being compiled on both OS X and Windows (64-bit support on both platforms). I'm using Visual Studio 2013 Update 4 (the latest update as of Jan 12, 2014).
I'm seeing various compiler errors with the code from LuaGlue master pulled today. From looking at the various open and closed issues, it looks like LuaGlue has worked on Windows at different points in time.
What is the current status of using LuaGlue on Windows?
See below for two examples of errors...
In LuaGLueLuaValue.h, snprintf(buff, sizeof(buff), "LUA_TNONE"); fails to compile. This behavior is expected based on the VS2013 notes.
I am also seeing an error about applyTuple...
The text was updated successfully, but these errors were encountered: