Note that there are some explanatory texts on larger screens.

plurals
  1. USJeff Trull
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. COI appreciate that the dependency scanner feature may only work for some languages... but it does work for C++, and it would be great to have this knowledge CMake already possesses available to users of Visual Studio. If not that, at least have some sort of hook so we can write it ourselves in CMake code (via source_group). An explicit list of dependencies will definitely go stale over time, as the compile will keep working even if it's wrong. Plus, it's redundant...
      singulars
    2. COIMO the thing all of these answers miss (with the exception of @Simeon) is that you don't want to explicitly list all of the header files, because: 1. The headers listed as explicit dependencies can easily drift out of sync with those you are actually using in the source, and 2. CMake knows already which headers you use, so it's redundant to input them manually as well. So we really need an answer that takes CMakes own knowledge of the header dependencies, and sticks them into a group for the solution.
      singulars
    3. COI came to this question because I had inadvertently created an empty local file called "new" in my include search path. This preempted the <new> system header which was used several #include levels away by a library I'm using. I spent hours figuring out why (message was **error: ‘nothrow’ is not a member of ‘std’** followed by a compiler crash). It seems like I can use the -iquote mechanism (is there a Visual Studio equivalent?) to ensure files included via angle brackets came only from system headers; it would be nice if that were supported via a CMake command.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload