I just tried to verify my statements and they have to be corrected slightly. I see some size differences between plain release and release with debug for the *.exe and *.dll files. I always had the opinion(!) that there is no difference to the release build. I have to find out now what the differenc...

Thanks for trying.
I have to conclude that I have a home made problem.

Hartmuth

Yes it should, and I am talking only about the third party libraries not FreeCAD itself. If anybody wants to build FreeCAD with debug info that is up to the them. I do it. The problem one encounters in plain debug mode is that the setup is in such a way that all kinds of libraries are slightly renam...

Debug builds would be nice but you could cheat a little bit and make it easier to debug by building "Release with debug info". It should build the same way as a release build but it would also create the *.pdb files. Something that is not ideal but would already help a lot

Hello folks, I use a VS2017 compiled version of FreeCAD, with Qt5 and Python3 support (FEM etc. turned off) and the latest conda libraries. I don't show the FreeCAD version info here, because the version.h file is hand generated and doesn't agree with the real status (See conda.) When I try to creat...

I completely understand. I had enough problems with the "default" and the #pragma. It's O.K. for small projects but if one starts to deal with projects that use many libraries it just becomes painful. It is considerably less painful to write a few more lines for the linker and actually hav...

The missing library is called "concrt.lib"

Removing the /NODEFAULTLIB from the linker options in the project file for Points makes it work. The typical warning about inconsistent libraries (static/dll) doesn't show up when it is removed. The question now is what one has to add to make it work with /NODEFAULTLIB added. I haven't found a hint ...

I'll do I found this on https://docs.microsoft.com/en-us/cpp/parallel/concrt/overview-of-the-concurrency-runtime ... Concurrency Runtime implementation history In Visual Studio 2010 through 2013, the Concurrency Runtime was incorporated within msvcr100.dll through msvcr120.dll. When the UCRT refacto...

Not impossible :-(. And the MS documentation was changed again for VS2017 and the API references are really "easy" to find. I'll have a look at the release notes if I can find something. This should be marked as a breaking change. I take it from your link that it works for you in an older ...