Skip to content

Clean up project solution structure#1538

Open
SaschaWillems wants to merge 1 commit intoKhronosGroup:mainfrom
SaschaWillems:vs_solution_cleanup
Open

Clean up project solution structure#1538
SaschaWillems wants to merge 1 commit intoKhronosGroup:mainfrom
SaschaWillems:vs_solution_cleanup

Conversation

@SaschaWillems
Copy link
Copy Markdown
Collaborator

Description

With some recent additions, the Visual Studio solution generated via CMake became cluttered, confusing people as to what's the right project to actually launch:

image

This PR cleans up that project structure by moving the recently added vgf components to the ThirdParty folder and framework related projects to the framework folder. That only leaves the samples project at the top level, making it clear that this is the project people are supposed to start from the IDE:

image

Note that this is a pure visual change and doesn't change anything about the source code structure itself and does not affect the build in any way. It simple tells CMake that, if the IDE supports it, those projects should be displayed in their respective sub folders.

General Checklist:

Please ensure the following points are checked:

  • My code follows the coding style
  • I have reviewed file licenses
  • I have commented any added functions (in line with Doxygen)
  • I have commented any code that could be hard to understand
  • My changes do not add any new compiler warnings
  • My changes do not add any new validation layer errors or warnings
  • I have used existing framework/helper functions where possible
  • My changes do not add any regressions
  • I have tested every sample to ensure everything runs correctly
  • This PR describes the scope and expected impact of the changes I am making

Note: The Samples CI runs a number of checks including:

  • I have updated the header Copyright to reflect the current year (CI build will fail if Copyright is out of date)
  • My changes build on Windows, Linux, macOS and Android. Otherwise I have documented any exceptions

If this PR contains framework changes:

  • I did a full batch run using the batch command line argument to make sure all samples still work properly

@SaschaWillems SaschaWillems added the build This is relevant to the build system label May 2, 2026
@asuessenbach
Copy link
Copy Markdown
Contributor

Looks much better!

But I would not expect the framework in a components folder.

And while you're at it: maybe you could move all those Shaders-<Language> folders into some Shaders folder?
Like

Shaders
|--- GLSL
|--- HLSL
|--- SLANG
|--- SPVASM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build This is relevant to the build system

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants