CMAKE_CXX_FLAGS is used to add flags for all C++ targets. That’s handy to pass general arguments like warning levels or to selected required C++ standards. It has no effect on C or Fortran targets and the user might pass additional flags. add_compile_options adds the options to all targets within the directory and its sub-directories. This … Read more
I blogged this a long time ago, and I don’t know if it still valid or not, but the code is something like… private void testfile(string file) { if(isAssemblyDebugBuild(file)) { MessageBox.Show(String.Format(“{0} seems to be a debug build”,file)); } else { MessageBox.Show(String.Format(“{0} seems to be a release build”,file)); } } private bool isAssemblyDebugBuild(string filename) { return … Read more
Differences between various standard modes clang supports the -std option, which changes what language mode clang uses. The supported modes for C are c89, gnu89, c94, c99, gnu99 and various aliases for those modes. If no -std option is specified, clang defaults to gnu99 mode. Differences between all c* and gnu* modes: c* modes define … Read more
In our experience with a medium-sized project, adding -pipe made no discernible difference in build times. We ran into a couple of problems with it (sometimes failing to delete intermediate files if an error was encountered, IIRC), and so since it wasn’t gaining us anything, we quit using it rather than trying to troubleshoot those … Read more
“Make assembly COM visible” is a big hammer to make all public types in the assembly [ComVisible]. Rarely desirable, you will want to select the specific types that you want to be visible, like you did in your snippet. After the assembly is built, it needs to be registered so that a COM client can … Read more
I found it here: Ox and O2 are almost identical. They differ only in the fact that O2 also throws GF and Gy. There is almost no reason to avoid throwing these two switches.
Have you seen this? (most info is in the penultimate post) /p:DefineConstants=”MYSYMBOL1;MYSYMBOL2″
The gcc option -O enables different levels of optimization. Use -O0 to disable them and use -S to output assembly. -O3 is the highest level of optimization. Starting with gcc 4.8 the optimization level -Og is available. It enables optimizations that do not interfere with debugging and is the recommended default for the standard edit-compile-debug … Read more
Right from the docs: -fpermissive Downgrade some diagnostics about nonconformant code from errors to warnings. Thus, using -fpermissive will allow some nonconforming code to compile. Bottom line: don’t use it unless you know what you are doing!