Come up with an universal approach for copying bin tools to tools/ folder
Closed, InvalidPublic

Description

vcpkg currently has a very fuzzy documentation on what is allowed to be in bin/ folder (e.g. build tools) and what needs to go to tools/ folder (e.g. runtime tools).

Our current approach is very quirky and explicit: we copy some particular exes that we think or need to get the framework or their dependencies build. This is mostly because Windows builds save their .dlls in bin/ as well, making it impossible to just move all the binaries to tools/ folder.

However, some additional build or runtime tools may be required by the actual software consuming these frameworks, and we should be really explicitly deciding about which are to be copied or not, so we should instead come up with an universal code that we will be able to copy/paste into kf5's portfile.cmake and that will handle the build and runtime tools for all platforms.

This will likely require opening an issue with vcpkg asking for more explicit documentation/guidelines/requirements on that subject.

wrobelda created this task.Sep 17 2020, 6:00 PM
wrobelda triaged this task as High priority.
wrobelda renamed this task from Come up with an universal template for copying bin tools to tools/ folder, according to vcpkg guidelines to Come up with an universal approach for copying bin tools to tools/ folder, according to vcpkg guidelines.
wrobelda renamed this task from Come up with an universal approach for copying bin tools to tools/ folder, according to vcpkg guidelines to Come up with an universal approach for copying bin tools to tools/ folder.
wrobelda updated the task description. (Show Details)