Resources in Tree (Feature)

[aronrubin]

This is a feature request for CMake projects. Please consider adding the files listed in the RESOURCE property of each target within the solution explorer tree. This now works with install(TARGET) on all platforms.

https://cmake.org/cmake/help/latest/prop_tgt/RESOURCE.html

Thank you,
Aron

[support]

Hi,

Thanks for the suggestion. Based on a quick research, it looks like a iOS/MacOS-specific feature. As this is a relatively rare use case for VisualGDB, we will not be able to add it as a regular VisualGDB feature. However, if you could confirm that CMake reports the resources via the JSON code model interface (or could prepare a patch to our open-source CMake fork that will export this information via the JSON model), we should be able to modify VisualGDB to display the resources in Solution Explorer.

[aronrubin]

set_property(TARGET ${TGT_NAME} APPEND PROPERTY RESOURCE ${TGT_LIST_OF_FILES})

Together with

install(TARGETS ${TGT_NAME}
  RUNTIME DESTINATION bin
  RESOURCE DESTINATION "share/${PROJECT_NAME}"
)

Will install resources as needed on every platform, not just Apple anymore. More importantly for my purposes, CPack will put the files in an installer/deb/pkg/rpm/zip on a component basis. Note BundleUtilities is not only for Apple anymore and can be used to package non-project DLLs in a Windows installer.

Aron

 

• This reply was modified 5 years, 11 months ago by support. Reason: formatting

[support]

Hi,

Sorry, this still looks like a relatively rarely used feature, so we will only be able to support it if CMake itself reports the resources via the JSON code model interface.

[aronrubin]

I see now; properties are not reported in the code model. I did not realize that before. This explains much. Do you happen to have insight into why there is no property query facility?

[support]

Hi,

The CMake code model reporting logic is generally relatively simple and only covers a few most common parameters. We extended it a lot in our CMake fork (including the ability to step through CMake files) and we may eventually add support for reporting generic properties (or specifically resources), however currently we cannot promise any timeframe for this. Please consider creating a patch for our CMake fork that will report the necessary information (alternatively we could give you a quote for developing this as a custom feature).

[Author]

Posts