cppclean | Finds problems in C++ source that slow development

You have to add the Python scripts path, e.g. C:\Users\USER\AppData\Local\Programs\Python\Python37-32\Scripts, to your system environment Path variable. (Replace USER with your actual user name and Python37-32 with your actual Python version). It's described here

So I can't take credit for this. I'm only posting answer so we can close this question. But the issue was with the portaudio library itself The portinfo.def file was not exporting the method that I was trying to call - the method referenced in the example file.

the fix was to add the following line to the portinfo.def file:

Pa_GetVersionInfo @ 69

Now my client / console app compiles. I will submit a patch later today to portaudio repo for the community to consider. But thanks to @HansPassant and πάντα ῥεῖ

You generally only need the .exe. Your app might depend on custom .dlls or the C++ run-time library in which case you would bundle the custom .dlls and/or the C++ redistributable.

Your screen shots are of a debug build and you normally want to distribute a release build instead because it is often smaller and contains more optimized code.

.obj files contain the machine code for each source file and is used by the linker when it merges all the required code into your .exe.

.pdb files contain debugging information. You should not distribute them but it is helpful to store them for yourself in case you need to debug a released version of your application.

The rest of the files in Debug and Release can also be ignored.

If your project is open source then you could include the c/c++ files and the Visual Studio project files. Or you could just upload them to Github.

In NSIS you could do something like this

From latest master branch find_warnings.py:

TODO(nnorwitz): provide a mechanism to configure which warnings should be generated and which should be suppressed. Currently, all possible warnings will always be displayed. There is no way to suppress any. There also needs to be a way to use annotations in the source code to suppress warnings.

So, it appears not at the moment.