<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=HU link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Someone managed to beat me to creating a CTest adapter for the Test Explorer UI extension to Visual Studio Code, so instead of writing on from scratch, I’ll start contributing to it. There is an „autorun test” property which can be triggered when the adapter sees fit. I wanted to create file watchers for the executable AND any files the test depends on, based on the REQUIRED_FILES property of the test. However, when the REQUIRED_FILES property is set on a test and I ask for –show-only=json-v1 ctest.exe fails with exit code -1073740791 and outputs nothing. Was this intended?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Cheers,</p><p class=MsoNormal>Máté</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>Feladó: </b><a href="mailto:csiga.biga@aol.com">Nagy-Egri Máté Ferenc</a><br><b>Elküldve: </b>2019. július 9., kedd 9:41<br><b>Címzett: </b><a href="mailto:kyle.edwards@kitware.com">Kyle Edwards</a>; <a href="mailto:cmake-developers@cmake.org">CMake fejlesztők</a><br><b>Tárgy: </b>RE: [cmake-developers] cmake-file-api and CTest</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi Kyle,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’ve never contributed to CMake before. I once wanted to enchance the makefile generators with batch-mode support and built CMake myself and walked through the code in debug mode to see what it does. I identified the entry point where I should’ve placed my code, but essential it would’ve require a major rewrite of the makefile generators to enable deferred makefile generation. Daunted by the amount of work, I figured it was not worth the effort. (It was primarily motivated by NMake.)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’ll try giving the file API a spin and see if I understand the code enough to be able to add new queries and extract tests from the internal representation. I was hoping to not have to touch CMake itself for this summer project, but it seems that’s the first step.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Cheers,<o:p></o:p></p><p class=MsoNormal>Máté<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b>Feladó: </b><a href="mailto:kyle.edwards@kitware.com">Kyle Edwards</a><br><b>Elküldve: </b>2019. július 8., hétfő 15:56<br><b>Címzett: </b><a href="mailto:csiga.biga@aol.com">Nagy-Egri Máté Ferenc</a>; <a href="mailto:cmake-developers@cmake.org">CMake fejlesztők</a><br><b>Tárgy: </b>Re: [cmake-developers] cmake-file-api and CTest<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On Sun, 2019-07-07 at 09:04 +0000, Nagy-Egri Máté Ferenc via cmake-<o:p></o:p></p><p class=MsoNormal>developers wrote:<o:p></o:p></p><p class=MsoNormal>> Hi!<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> I am trying to cook a CTest back-end to the Test Explorer UI<o:p></o:p></p><p class=MsoNormal>> extension for VS Code as a summer project and I thought of using the<o:p></o:p></p><p class=MsoNormal>> new cmake-file-api for it. The docs however are understandably scarce<o:p></o:p></p><p class=MsoNormal>> and I could not muster how to obtain tests and not targets. Is it<o:p></o:p></p><p class=MsoNormal>> possible with this initial API design? If not, is my best bet to<o:p></o:p></p><p class=MsoNormal>> invoke CTest and parse the console output?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>FileAPI does not currently list CTest tests, though I agree that this<o:p></o:p></p><p class=MsoNormal>would be a good thing to have, perhaps for 3.16. Is this something<o:p></o:p></p><p class=MsoNormal>you'd be willing to help with?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Kyle<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>