I hit the same issue as #133 The reason is that even if no cflags or cxxflags are specified in the Config, it will still forcibly set those in the cfg, even if no_default_flags is forced to true (in that case CMAKE_C(XX)_FLAGS is just set to empty). This causes some ...
写Makefile大概是每一个合格的C/C++程序员的基本功吧，几乎所有C语言写的开源项目都会用Makefile或者...
🐛 Bug Since I can't use conda gcc 7.3 (#29093), I tried to build master with system gcc 7.4 and met CMake Error at third_party/fbgemm/third_party/asmjit/CMakeLists.txt:100 (target_compile_features): target_compile_features no known featu...
I set -DCMAKE_C_FLAGS_RELEASE and -DCMAKE_CXX_FLAGS_RELEASE the build for 8.0.31 and 8.0.32 fails.How to repeat:This is on Ubuntu 22.04 that uses gcc 11.3.0 I start with this cmake command line based on the advice at:https://dev.mysql.com/doc/refman/8.0/en/source-configuration...
(issue corresponding to review suggestion here) CMAKE_CXX_FLAGS is used to configure compiler warnings in cmake as part of the testing procedure, (following the this advice). I am not aware of a warning API in cmake and I know of no opti...
In CMake/README.md, there is this line in the sample CMakeLists.txt file: set(CMAKE_CXX_FLAGS "-std=c++11 -stdlib=libc++ ${CMAKE_CXX_FLAGS}") The implication here is that if I want to compile with c++17, all I need to do is replace -std=...
Summary I am tempted to file this as a bug, but I suppose it is technically a feature request :) cxxflags and cflags as specified in package.yaml or even on the command line do not automatically get passed into CMake. (both ways just get...
^ make[2]: *** [openalpr/CMakeFiles/openalpr.dir/ocr/tesseract_ocr.cpp.o] Error 1 make[1]: *** [openalpr/CMakeFiles/openalpr.dir/all] Error 2 make: *** [all] Error 2 I solved it by following line into set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11") ...