![]() ![]() Expected:Ĭorrect flags passed to GCC CMake Tools Log In that case too, nuking the build directory and manually running cmake from the terminal made things run as they should. When manually starting the build via make VERBOSE=1 I noted the -g option was not being passed to GCC in spite of having the Debug variant selected. She was trying to debug a program and kept getting an error along the lines of symbols not found. use -isystem instead of -I via target_include_directories), however I observed similar behavior with a co-worker yesterday. ![]() In my case I was trying to declare some directories as SYSTEM (i.e. Repeating the above steps, but selecting Release instead of Debug works as expected. This only appears to happen when selecting the DEBUG build variant. If I nuke the build directory and manually configure (i.e. Once the build fails, in the terminal I manually start the build via make VERBOSE=1 and looking at the GCC command, sure enough the flags are not being passed to GCC. Building commences but it becomes apparent that not all the flags given in CMakeLists.txt were passed to the compiler.I push the build button at the bottom (kit had been previously selected.).I configure the project via clicking the "Click to select build variant" button on the status ribbon at the bottom of the screen and then select Debug in the pop up that appears.Makefile build generatorįrom a completely fresh build (i.e. Ubuntu 16.04, cmake 3.14.6, vscode 1.41.1, c/c++ extension 0.26.3, cmake tools 1.2.3īuilding within docker remote dev container. Debug build variant doesn't pass correct flags to GCC. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |