Author Topic: MS Visual Studio 2017  (Read 534 times)

Offline WolfG

  • Multiple posting newcomer
  • *
  • Posts: 10
MS Visual Studio 2017
« on: February 19, 2019, 04:37:28 pm »
Greetings!

Can I use "MS Visual Studio Community 2017" for codeblocks at all?

First I tried to configure maually via toolchain but this does NOT allow a new compiler being added.
I've already replaced the default GNU by the 'TDM-GCC-64'compiler with success.

So I changed the default.conf and added
Code: [Select]
<msvs2017>
<NAME>
<str>
<![CDATA[Microsoft Visual Studio 2017]]>
</str>
</NAME>
<INCLUDE_DIRS>
<str>
<![CDATA[C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\include;]]>
</str>
</INCLUDE_DIRS>
<LIBRARY_DIRS>
<str>
<![CDATA[C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\lib\x64;]]>
</str>
</LIBRARY_DIRS>
<MASTER_PATH>
<str>
<![CDATA[C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023;]]>
</str>
</MASTER_PATH>
</msvs2017>
but this did not solve the issue.


I prefer CB over MSVS IDE, however if I cant use the MSVS compiler I'm having a problem.
Any hint will be very much appreciated.
Wolf

   

Offline New Pagodi

  • Multiple posting newcomer
  • *
  • Posts: 33
Re: MS Visual Studio 2017
« Reply #1 on: February 19, 2019, 04:53:48 pm »
I use visual studio 2017.  I made a copy of the "Microsoft Visual C++ 2010" compiler in codeblocks and then made the changes described here.  Other than the slightly annoying popup at startup mentioned in that thread, everything works OK.