openFrameworks | openFrameworks is a community-developed cross platform toolkit for creative coding in C++ | Video Utils library

The http://winlibs.com/ build of GCC/MinGW-w64 has a very recent version of MinGW-w64 which contains devpropdef.h.

Solved installing g++-10 and gcc-10 using:

Best method to do this is to use something called the factory pattern.

Basically, define a function that takes an argument of some defined type that can be used to figure out what kind of simulation you want, and then create that simulation and return a pointer to it.

A simple version of it might look like this:

It's this loop

Taken from the comments to the question. Although this is unusual it could be that a header in one of the dependencies of your project has the same name as a header in the filesystem library. And since you put boost first in the Additional Include Directories the boost header was included instead of a header from a different library. By default with Visual Studio boost automatically inserts link commands using a #pragma comment(lib, libname) so including this header will cause a link dependency.

A solution to try in this case is to move boost to the end of the Additional Include Directories so when the compiler searches for the header it will find the one from the previous dependency first.

It's a typo. : should be ::. You can see it being correct in the fourth code block of the linked examples, while the previous two were, presumably, copy-pasted with the same error.

It may, however, be confused as a label, but a label cannot be placed in such contexts.

I tried running the same code in Visual Studio Code and it debugged like normal but I need the 2017 version for a class.

First, please check whether you have opened a solution or a project rather than a cpp file. In general, all the debug configuration info are stored in the xxxx.vcxproj file and .vs hidden folder which belog to the whole project.

Solution

First, try to click File-->Open-->Porject/Solution to open .sln or xxx.vcxproj file. Besides, right-click on the project which you want to debug to click Set as StartUp Project.

Note: each project can only has one main cpp file. Or you can just add these codes into the main cpp file directly.

If the steps above did not work, please try these:

1) exclude this project from your solution(remove it) and then build your solution without it.

2) you should again add your project into the current solution and then build your solution and set it as Start Up Application.

In addition, if you cretae the OpenFrameworks project with other third party tool to generate it and then open the project in VS2017, I think you cannot do this. Incompatibilities and other issues can arise because the project itself generated by other tools is not the same as the project structure created by VS2017.

So try these steps to create OpenFrameworks projects with VS2017:

1) install openFrameworks extension on Tools-->Extension and Updates.

2) After that, when you create the openFrameworks project in VS2017, do not forget to add the folder path of of_v0.11.0_vs2017_release which is downloaded from this link.

You can follow this guidance to get more detailed steps.

3) After that, you can try to add these codes in main.cpp file.