<html><head><style data-externalstyle="true">
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst, p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle, p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
line-height:115%;
}
</style></head><body><div data-externalstyle="false" style="font-family:Calibri,'Segoe UI',Meiryo,'Microsoft YaHei UI','Microsoft JhengHei UI','Malgun Gothic','Khmer UI','Nirmala UI',Tunga,'Lao UI',Ebrima,sans-serif;font-size:16px;"><div>Can you run ctest on your development machine, but have each test invoke the remote debugger separately? i.e. -- write a wrapper around add_test which invokes the command via the remote debugger on the VM instead of locally...</div><div> </div><div>That might be painful to do if you have lots of tests, and you don’t already have an add_test wrapper. But if you do have a wrapper, it should be easy enough in theory. (Assuming you can drive a remote debugger session via a command line of some sort. Or via a script.)</div><div> </div><div data-signatureblock="true"> </div>        <div style="border-top-color: rgb(225, 225, 225); border-top-width: 1px; border-top-style: solid;">                <strong>From:</strong> Robert Dailey<br>                <strong>Sent:</strong> March 19, 2013 3:33 PM<br>                <strong>To:</strong> Eric Noulard<br>                        <strong>CC:</strong> CMake<br>                <strong>Subject:</strong> Re: [CMake] Running tests on remote machine<br>        </div>        <div> </div>It simply uses TCP connection to the remote machine, using the Windows<br>Remote Debugger service. it handles the details of remote debugging,<br>all I do is point it to the correct executable to run from my project<br>settings on the host machine. No authe<br><br>The only thing that the program needs on the VM is the runtime<br>libraries, which are available as a separate installer<br>(redistributable package). Basically my VM simulates a production<br>environment for the most part, where if you had installed the program<br>via installer on that machine, it would run in a similar fashion.<br><br>Looks like I'm stuck making my VM into a dev machine so I can build<br>the code from scratch & run tests :( ... unless anyone has some ideas.<br><br>On Mon, Mar 18, 2013 at 1:39 PM, Eric Noulard <eric.noulard@gmail.com> wrote:<br>> 2013/3/18 Robert Dailey <rcdailey.lists@gmail.com>:<br>>> Hi,<br>>><br>>> I currently have a VM that I use to debug my executables. It has the<br>>> environment setup that is needed by the programs. Naturally, the tests<br>>> also depend on this environment (nothing was really mocked).<br>>><br>>> The machine hosting the VM is my dev machine, it only has CMake &<br>>> Visual Studio. I set it up to remote debug on the VM, which accesses<br>>> the compiled binaries via network shared folder.<br>><br>> Does remote debug with Visual enables the host to "run" something on the<br>> remote target without having some part of Visual installed on the<br>> remote target ?<br>><br>>> Is there a way I can just run the tests on the VM with CTest? I don't<br>>> want to have to install Perforce, Visual Studio, and CMake on my VM if<br>>> I can avoid it. Note both machines are running Windows.<br>><br>> AIFAIK CTest has no 'remote run' capability, so you'll need at least<br>> to have CTest<br>> installed on the VM.<br>><br>> That said I do have a not so different usage.<br>> I need to to distributed testing on a CMake enabled project.<br>> What I currently do is to write a (python)<br>> "test driver script" which does one (or several) remote connection to<br>> the target(s)<br>> and launch the CMake built binaries (and possibly tests inputs) which<br>> are available<br>> through network drive (host mounted on the target(s)).<br>><br>> That way CTest runs on my host and the executable runs on the remote targets.<br>> The drawback is that I need to have a relatively "intelligent" scripts<br>> which is able<br>> to remote login and monitor/connect to stderr, stdin, stdout on the<br>> remote execution.<br>><br>> My solution currently only works on Unixes or on a remote host which has<br>> an SSH server (ssh is my "generic" remote logion solution).<br>><br>> Thus my question, how does Visual do the remote login/connection for debugging?<br>><br>> --<br>> Erk<br>> Le gouvernement représentatif n'est pas la démocratie --<br>> http://www.le-message.org<br>--<br><br>Powered by www.kitware.com<br><br>Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html<br><br>Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ<br><br>Follow this link to subscribe/unsubscribe:<br>http://www.cmake.org/mailman/listinfo/cmake<br></div></body></html>