Luca

@kracejic any input on this PR?

@LucaFuma74 the task was never tested on an on-premise Azure DevOps Server (or TFS server). It requires changes to the manifest, and potentially changes in the APIs it is currently...

Same here, for one repository is not working and coverage is 0%. Running tests locally it reports around 70%. https://github.com/lukka/run-vcpkg/issues/109

@davidebeatrici This could be helpful: https://stackoverflow.com/questions/43981966/cmake-how-to-specify-directory-where-ctest-should-look-for-executables

@davidebeatrici i'd be glad if you could explain the feature request more in detail. Note that the action does not invoke `ctest` and all the action can do is to...

@illia-bilinskyi my guess is that depends on the `generator` that CMake is going to pick up at run time in the configure phase. Since you did not specify it, if...

@Sapd this is mostly uncharted territory for me. I put that input in order to potentially let the user drive the [`Options.shell` value](https://nodejs.org/api/child_process.html#child_processexeccommand-options-callback) passed to `child_process.exec()` in this [section of...

@Sapd you may try the modification you suggest by directly modifying the [dist/index.js](https://github.com/lukka/run-cmake/blob/main/dist/index.js) content in your own fork. That file is the "executable" which is run the the action runs....

@Sapd as an additional note, the path you see (without the backslashes, ` /usr/bin/bash: line 1: C:Program FilesCMakebincmake.exe: command not found`) would indicate that the filesystem paths must all manipulated/joined...

@SamuelMarks if i get this right, this is the question: "how can I implement a pure workflow without using `run-vcpkg` (with or without `run-cmake`) and without having `vcpkg` as a...