Skip to content

Conversation

@bk138
Copy link

@bk138 bk138 commented Oct 28, 2021

The parsing of entries like <Image Include="image.bmp" /> is more of
a UX thing as developers will expect image groups they have in their
original Visual Studio project to appear in whatever IDE they're
using with their converted-to-CMake-project. At least so I think.

The parsing of entries like <ResourceCompile Include="resource.rc" />
however makes resource file entries appear in the resulting
CMakeLists.txt which is a real functionality fix. Without the resource
files listed, converting projects using resource files would result in
broken converted projects.

The parsing of entries like `<Image Include="image.bmp" />` is more of
a UX thing as developers will expect image groups they have in their
original Visual Studio project to appear in whatever IDE they're
using with their converted-to-CMake-project. At least so I think.

The parsing of entries like `<ResourceCompile Include="resource.rc" />`
however makes resource file entries appear in the resulting
CMakeLists.txt which is a real functionality fix. Without the resource
files listed, converting projects using resource files would result in
broken converted projects.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant