Thanks Bill. With every update of Visual Studio 2017 (2017.3 is the latest as
of this moment), we're striving to improve the experience.
For a shorter summary of the advantages of using Visual Studio for CMake
projects, you can also check the deep-link
https://blogs.msdn.microsoft.com/visualst
On 8/18/2017 9:37 AM, Jean-Michaël Celerier wrote:
IMHO, Visual Studio's CMake integration is a joke in comparison to
QtCreator and CLion.
Microsoft has been working to fix that.
https://blogs.msdn.microsoft.com/vcblog/2016/10/05/cmake-support-in-visual-studio/
MS is shipping a version of CMa
> Visual Studio 2017 has the best C/C++ experience with CMake
IMHO, Visual Studio's CMake integration is a joke in comparison to
QtCreator and CLion.
---
Jean-Michaël Celerier
http://www.jcelerier.name
On Fri, Aug 18, 2017 at 12:04 PM, Nagy-Egri Máté Ferenc via
cmake-developers wrote:
>
CLion works well.
On Fri, Aug 18, 2017 at 6:04 AM, Nagy-Egri Máté Ferenc via cmake-developers
wrote:
> Impressed with VSCode?? If I saw this post anywhere else than the CMake
> mailing list, I’d understand, but VSCode with CMake is horrible. The fact
> that in 2017 I have to set include director
Impressed with VSCode?? If I saw this post anywhere else than the CMake mailing
list, I’d understand, but VSCode with CMake is horrible. The fact that in 2017
I have to set include directories, compiler definitions and target paths
manually to have proper IntelliSense (Code navigation and syntax
Le 16.08.17 à 16:27, Eric Wing a écrit :
I've been using a derivative of the iOS toolchain for many years that
you probably can find easily with a Google search. It has a lot of
shortcomings, but it generally works. And most of the shortcomings I
think are only solvable by properly fixing/modifyi
