Visual Studio 2017 - Compiling C++ with older MSVC SDK -

-

with visual studio 2017, have several ways launch compilation within ide window. there's build menu, built-in command prompt, , cmake integration visual studio 2017 launches cmake.

the command prompt , cmake integration allow users launch compilation older versions of msvc. example, using cmakesettings.json, users can specify generator version 14 so:
"generator": "visual studio 14 2015"

unfortunately, there's fundamental problem in visual studio 2017 window , child processes automatically populated environment variables compiling version 15: equivalent of running vcvarsall.bat.

this problem because in microsoft document, recommendation not run vcvarsall.bat version once version of script has been run once in process. avoid conflicts between variables different versions.

if current version of visual c++ installed on computer has previous version of visual c++, should not run vcvars32.bat different versions in same command window.

https://msdn.microsoft.com/en-us/library/f2ccy3wt(v=vs.110).aspx
https://msdn.microsoft.com/en-us/library/f2ccy3wt(v=vs.140).aspx

this subtle problem, because passing generator option cmake takes care of things related msvc versioning. however, part of cmake script or child process launched cmake tries detect visual studio version see vs2017.

so, support generator option in cmakesettings.json, visual studio have provide mechanism cmake process obtain appropriate environment variables generator version specified. include nullifying or somehow removing 2017 specifics created upon opening visual studio 2017.

has else experienced problem , found way solve or workaround it?


Comments

Post a Comment

Popular posts from this blog

ios - MKAnnotationView layer is not of expected type: MKLayer -

-
Image
so code works fine logger riddled message. there way rid of or suppress it? postannotation.swift class postannotation: mkpointannotation { //mark: properties let post: post //mark: initialization init(post: post) { self.post = post super.init() self.coordinate = cllocationcoordinate2d(latitude: post.latitude, longitude: post.longitude) self.title = post.title self.subtitle = post.timestring() } } adding annotation let annotation = postannotation(post: post) self.map.addannotation(annotation) func mapview func mapview(_ mapview: mkmapview, viewfor annotation: mkannotation) -> mkannotationview? { if annotation mkuserlocation { return nil } var annotationview = mapview.dequeuereusableannotationview(withidentifier: "pin") as? mkpinannotationview if annotationview == nil { annotationview = mkpinannotationview(annotation: annotation, reuseidentifier: "pin")
Read more

ZeroMQ on Windows, with Qt Creator -

-
i have installed zmq link given below on windows 7. http://zeromq.org/distro:microsoft-windows 1) have c++ project in qt-creator , i'm using zmq c++ binding (zhelpers.hpp etc). 2) have added .lib installed zmq folder qtcreator 3) while compiling, compiler looks _imp__zmq_verion, in .dll files present in .lib have __imp_zmq_version. 4) causing undefined reference zmq_version. anyone else faced problem , has solution ?
Read more

unity3d - Unity SceneManager.LoadScene quits application -

-
i have 2 different scenes 1 named 'main' , other 'game' both added scenes in load. when use scenemanager.loadscene("game"); works no problem when tried return main scene code if (input.getkeydown (keycode.escape)) { scenemanager.loadscene("main"); } strangely game quits. thanks. sorry interruption. somewhere on other script found code. if (input.getkeydown (keycode.escape)) { application.quit (); } that's bad, know...
Read more