User forums > Using Code::Blocks

VS2017 and Global Variables

(1/3) > >>

jamesson:
I was trying to follow the instructions at https://github.com/arnholm/cpde_utils/blob/master/doc/toolchain/CodeBlocks_MSVC_setup.pdf using VS2017. It gives instructions for VS/VS express 2013. However, after I got about halfway, I realized that there were 2 folder trees that satisfied (some of) the requirements, one at

C:\Program Files (x86)\Microsoft Visual Studio 14.0

and the other at


C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise

Should I use one of these consistently? If so, which?

cacb:
Hi jamesson,

That's my page at github. I don't have a ready reply for you regarding VS2017, since I still use VS2013 with Code::Blocks, but please post anything you conclude here, and I will update the document when you have a successful configuration. I might even upgrade then :-)

Traditionally, it has been a combination of Visual Studio folders and "Windows Kits" (these terms tend to vary) to get everuthing working, that's what that document reflects.

Please keep us posted.

sodev:
The first path could be a Visual Studio 2015 installation, the second path is a Visual Studio 2017 Enterprise installation. Choose the path of the compiler you want to use :).

Getting VS2017 to run requires a lot of changes to the pdf, the paths completely changed and some CodeBlocks requirements are not met anymore, someone else posted on this forum how to setup, im too lazy to dig up the thread ;D. To use VS2015 i think the pdf misses the paths to the CRT, otherwise it should still apply.

cacb:

--- Quote from: sodev on March 11, 2019, 10:32:57 am ---The first path could be a Visual Studio 2015 installation, the second path is a Visual Studio 2017 Enterprise installation. Choose the path of the compiler you want to use :).

Getting VS2017 to run requires a lot of changes to the pdf, the paths completely changed and some CodeBlocks requirements are not met anymore, someone else posted on this forum how to setup, im too lazy to dig up the thread ;D. To use VS2015 i think the pdf misses the paths to the CRT, otherwise it should still apply.

--- End quote ---

Agreed, I would be interested in the VS2015 configuration, as I have access to it. With CRT I presume you mean C Run-Time libraries.

sodev:
It's their universal crt that is new since that version, it's only a part of the runtime libraries.

My current VS2015 setup is described here http://forums.codeblocks.org/index.php/topic,22009.msg149847.html#msg149847, because i use the Windows XP toolkit im using another SDK and need some paths less.

Navigation

[0] Message Index

[#] Next page