[Cdash] Problem with cdash, subprojects and CTEST_USE_LAUNCHERS=TRUE?

David Cole david.cole at kitware.com
Mon Aug 20 21:06:35 UTC 2012


Well, I grepped like this (in the CMake source tree)... One leads to the
next till you finally find

git grep "\-\-launch"
git grep CTEST_LAUNCH_COMPILE
git grep RULE_LAUNCH_COMPILE
git grep RuleLauncher

Ah ha:
Source/cmLocalGenerator.cxx:void
cmLocalGenerator::InsertRuleLauncher(std::string& s, cmTarget* target,

If there is a rule launcher, it simply gets prepended to the "real rule" in
this method:
//----------------------------------------------------------------------------
void cmLocalGenerator::InsertRuleLauncher(std::string& s, cmTarget* target,
                                          const char* prop)
{
  if(const char* val = this->GetRuleLauncher(target, prop))
    {
    cmOStringStream wrapped;
    wrapped << val << " " << s;
    s = wrapped.str();
    }
}


--launch should appear in the generated makefiles after you include CTest,
and turn on CTEST_USE_LAUNCHERS.


HTH,
David


On Mon, Aug 20, 2012 at 4:08 PM, Alexander Neundorf <neundorf at kde.org>wrote:

> On Monday 20 August 2012, Alexander Neundorf wrote:
> ...
> > I'm looking at it right now...
> > I actually haven't figured out yet how that launchers feature works.
> > Should the string "launch" (or "--launch") appear somewhere in the
> > buildtree as soon as I include CTest ?
>
> Ah, wait, I got it: this happens in the testing build tree where cmake is
> executed from within ctest, right ?
>
> Alex
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cdash/attachments/20120820/3515dafe/attachment-0003.htm>


More information about the CDash mailing list