User forums > Using Code::Blocks

VS2017 and Global Variables

<< < (2/3) > >>

jamesson:

--- Quote from: cacb on March 11, 2019, 09:34:29 am ---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.

--- End quote ---


Cacb, would you be willing to help me update the PDF?

If so, please post as many as possible specific filenames you expect to find in all the variable directories

Thanks

Joe

New Pagodi:
Here are the directions I use for using Visual C++ 2017 with Code::Blocks.

jamesson:
New Pagodi:

Sorry, maybe I am not reading it correctly. Which directions are you referring to? The thread seems to terminate in a discussion of the bugs in your configuration.

New Pagodi:
Those directions work now.  Except for the popup when codeblocks starts which has to be ignored for now.

jamesson:
You mean, the bug involving spaces in directory names has been dealt with?

Thanks again

Joe

Navigation

[0] Message Index

[#] Next page

[*] Previous page