“un-optimize” a VisualStudio-solution

Written by  on March 2, 2018 

By default after generating the solution from mpc-files for each vcxproj the optimization-level is set to maximum (O2), which can lead to trouble while debugging. Variables not “visible”, content of containers not readable, .. and then you can stop debugging, reset manually the optimization, restart and go to the breakpoint/crash. Which is a total waste of time.
I’ve also found no way to convince the mpc-buildsystem of building un-optimized.

Ok, then we build us a sed-oneliner which replaces in all project-files the line about optimization and run it under cygwin:

Category : C++cygwinVisualStudioWin

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.