Repository navigation
VS issues warning about wildcards in props file #158
Description
Activity
Are you aware of a better option? This is kind of necessary now since the files generated will depend on the namespaces included.
One option could be to generate a cpp file that
#includes all the other cpp files, however I have strong feelings that we'll get "compiler ran out of heap space" errors if enough stuff is getting projected (e.g. the sdk compilation tests).Another option might be to generate a targets file that has all the files listed, however I have strong doubts that msbuild will like that.
The link that the warning references mentions some alternatives that look maybe promising, but we'll need to test them out, in part because I'm unsure how they'll behave with sources getting generated after msbuild begins invocation.
C:\Users\asklar\source\repos\react-native-xaml\example\windows\WinRTTurboModule\WinRTTurboModule.vcxproj : warning : Wildcards in project items are not supported in VC projects or their imports. The 'ClInclude' wildcard project items added in 'C:\Users\asklar\source\repos\react-native-xaml\example\windows\packages\Microsoft.ReactNative.WinRT.0.67.20220127.3\build\native\WinRTTurboModule.props' will not be visible in the Solution Explorer. Please refer to the https://aka.ms/cpp/projectwildcards for supported options.