microsoft/GSL

Make files visible in generated Visual Studio solution

Open

#1,216 创建于 2025年9月26日

在 GitHub 查看
 (4 评论) (0 反应) (0 负责人)C++ (5,695 star) (721 fork)batch import
Help WantedPriority: LowStatus: Open

描述

If you generate a Visual studio solution from the current CMake the GSL headers like algorithm and assert don't appear. The only way you seem to be able to see them is to open a test like algorithm_tests.cpp and then do a "Go to document" on a line like #include <gsl/algorithm>. In my local copy I added the following

add_custom_target(include SOURCES
    gsl/algorithm
    gsl/assert
    gsl/byte
    gsl/gsl
    gsl/narrow
    gsl/pointers	
    gsl/span
    gsl/span_ext
    gsl/util	
    gsl/zstring		
)

But I am sure that is the wrong way to do it.

I also added

set(SolutionItems
    .clang-format
    .gitattributes
    .gitignore
    CMakeSettings.json
    CONTRIBUTING.md
    LICENSE
    README.md
    SECURITY.md
    ThirdPartyNotices.txt)
set_property(DIRECTORY APPEND PROPERTY VS_SOLUTION_ITEMS ${SolutionItems})

This makes all these files appears in the "Solution Items" folder in the IDE which is super useful.

贡献者指南

技术栈
cpp
领域
build systemdeveloper experience
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
2
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
under 1 hour
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Basic CMakeFamiliarity with Visual Studio
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
85
研究方向
Review the repository's CMakeLists.txt to understand current header organization. The issue suggests adding headers to a custom target and also adding project files to VS SOLUTION ITEMS. Check maintainer feedback in the comments (4 comments) for preferred implementation. Ensure the solution is compatible with non Visual Studio generators by using cmake generator expressions if needed. Implement the changes in a PR and verify that headers appear in the Visual Studio solution without affecting build functionality.