[KDevelop feedback] About msvc support
kfunk at kde.org
Thu Jan 5 12:27:30 UTC 2017
On Thursday, 5 January 2017 09:59:55 CET KDevelop wrote:
> Luca Carella (not verified) (bkarelb at hotmail.it) sent a message using the
> contact form at https://www.kdevelop.org/contact/kdevelop_feedback.
> Don't know what are the plans for msvc support in KDevelop, but
> at the moment it's not really good: it's required to start KDevelop with a
> shell script(wich call vcvarsall.bat) in order to set up a proper
> environment for cmake. The script you ship along with KDevelop, by default
> set up the x86 compiler toolset..
> Doing this way, windows users can't set up multiple target, or the x64
> toolset without manually set up the environment for x64 toolset and start
> kdevelop from here.
Yes, we're aware that this is not a good solution. It's a hack to work around
the fact we're not having any config pages for setting up toolkits.
> I suggest to look on how QtCreator do this: basically they create a script
> that lunch vcvarsall, then call PATH to output the PATH,env variable. Then
> they read the output and use this to set-up the envirnoment at runtime(for
> example when changing target or toolkit).
For the meantime I could think of having a small popup dialog at start which
asks you which MSVC environment to load. I think that would solve most of the
issues, without a lot of work.
Switching the toolkits at *runtime* (something which QtCreator allows) is
something I (for instance) rarely do. Not saying we shouldn't support it
> Thanks, and hope to see lot of improvment, i would like to switch to
> KDevelop from QtCreator, but the moment for me it's not really user
If you want to help us out on Windows/MSVC support, please have a look at:
Kevin Funk | kfunk at kde.org | http://kfunk.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 163 bytes
Desc: This is a digitally signed message part.
More information about the KDevelop-devel