Repository navigation
Conversation
|
I asked a question about the validity of the reasoning here boostorg/assert#49 (comment) |
|
@cdglove I don't understand how this is a problem. Are you using Boost as a subdirectory? Try |
|
I'm using it like this: And consuming it like this: When one does this, it re-runs every GLOB in every file whether the library is being consumed or not. See my related post on the mailing list: |
Allows projects building boost via add_subdirectory to avoid the cost of GLOB on every build.
|
Updated as per discussion on the mailing list and integrated into the assert library. https://lists.boost.org/archives/list/boost@lists.boost.org/thread/LKPFNC3AMPIVWRAE75EFMYRMS6AL6MV4/ |
|
I just wanted to mention on the previous changes, before the recent update: There may be more IDEs than just Visual Studio that make use of source groups, such as Xcode. I wouldn't want to mandate Visual Studio to get this behaviour. |
When file(GLOB ... CONFIGURE_DEPENDS) or file(GLOB_RECURSE ... CONFIGURE_DEPENDS) is evaluated, CMake's make style generators create a verification script (VerifyGlobs.cmake) that gets run on every build, outputting "Re-checking globbed directories....". This can cause a a noticeable delay on incremental builds.
Since the headers are only needed for IDE project navigation, limiting this check to that use case is a good compromise.