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
{{ message }}
Repository navigation
Build node sources under visual studio 2013 #12070
Im trying to build the node sources just cloned on my local machine, then after runing the ./configure script , i open the visual project using visual studio 2013 then when i'm building i got some errors see the screenshot:
I'm using windows as a plateform and visual studio 2013 as an IDE.
@mscdex is there some code features in the node sources that prevent me to build on VS 2013, how about those people who used to work with 2013 version they cannot build node under windows so
@gibfahn i'm just used to work with VS2013 for a while, then i think i have to jump into the VS2015, so good to know about native addons still support by VS2013.
Can you tell me about problem with C++ 11 when using 2013 i cannot figure out whats going wrong if you use 2013, i just read on comment that there was some issues with c++11 but still not clair anyway.
@benmouh I don't know that much about this, but you can see #8067 for some of the workarounds we had in our codebase as a result of having to support VS2013. I think the problem was that the number of these workarounds in Node and deps were becoming increasingly unmanageable.
Activity
mscdex commentedon Mar 27, 2017
The build requirements indicate you need VS 2015 or VC++ Build Tools 2015 or newer to build node.
benmouh commentedon Mar 27, 2017
@mscdex is there some code features in the node sources that prevent me to build on VS 2013, how about those people who used to work with 2013 version they cannot build node under windows so
mscdex commentedon Mar 27, 2017
See the original issue about dropping VS2013 support for more information.
gibfahn commentedon Mar 27, 2017
@benmouh It was mostly C++11 issues that caused the update.
You should be able to just install the Visual C++ Build Tools 2015, which are much smaller than VS 2015. Is there a reason you need VS 2013?
Note that you can still build native addons with VS 2013.
benmouh commentedon Mar 27, 2017
@gibfahn i'm just used to work with VS2013 for a while, then i think i have to jump into the VS2015, so good to know about native addons still support by VS2013.
Can you tell me about problem with C++ 11 when using 2013 i cannot figure out whats going wrong if you use 2013, i just read on comment that there was some issues with c++11 but still not clair anyway.
gibfahn commentedon Mar 27, 2017
@benmouh I don't know that much about this, but you can see #8067 for some of the workarounds we had in our codebase as a result of having to support VS2013. I think the problem was that the number of these workarounds in Node and deps were becoming increasingly unmanageable.