![]() Build output parsing support so warning/error display is integrated with VSCode, listing them inside the IDE with usual interaction (e.g.If the directory doesnt already exist CMake will make it. ⢠Generation of include directories so VSCode has proper information to provide IDE support. B , Path to directory which CMake will use as the root of build directory.![]() targetincludedirectories(): To tell CMake that the project directory tree contains headers.In this way, we can have headers from different directories added to each other with a relative path to the project directory. targetsources(): to add the source in the currrent directory, app.cpp, to app target. With this minimal configuration, I would like this extension to provide me the following: addexecutable(): is to define app target. No need to complicate my life with kits and I don't need to relearn how to set some CMake variables. I already have a way to setup a build dir with various configuration parameters (simple shell scripts), and I prefer doing it like that for established projects as it's clear to me what's happening. ![]() It would be nice to have Visual Studio CodeCMake output integration without doing any additional configuration through the IDE outside of setting the build directory (for out of source builds). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |