It's not that the code would be trickier, it's that the CDash database schema only supports one view of a repository in terms of generating correct links on its update report pages. So even if ctest allowed you to do this, CDash would not produce correct output.<div>
<br></div><div>There's a lot *more* work to be done to get updates from multiple repositories or multiple paths within one repository working all the way through the ctest/cdash workflow.</div><div><br><br><div class="gmail_quote">
On Thu, Feb 18, 2010 at 11:04 AM, Tyler Roscoe <span dir="ltr"><<a href="mailto:tyler@cryptio.net">tyler@cryptio.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Thu, Feb 18, 2010 at 09:14:05AM -0500, David Cole wrote:<br>
> The APPEND option is probably a little more complicated than you think it<br>
> is... And it is not "secretly" (or otherwise) added to ctest_update...<br>
> CMake, being open source and all, has no secrets. :-)<br>
<br>
</div>I was just joking about it being secret. I was idly hoping that maybe<br>
when APPEND was added to _build and _configure, it was also added to<br>
_update but the docs were only updated for _build and _configure. Sounds<br>
like this is not the case; bummer.<br>
<div class="im"><br>
> We need to write some docs or an article that explains how to use "APPEND"<br>
> well.<br>
><br>
> Every call to ctest_build yields a completely new Build.xml file to send to<br>
> CDash. The APPEND option merely tells CDash to append the results to those<br>
> already in the database for a given build... it does not actually append<br>
> data to the same Build.xml file. Therefore, if you use it, you must also use<br>
> piecemeal ctest_submit calls to send each Build.xml file as it's produced<br>
> over to CDash before the next call overwrites the Build.xml file. (Things<br>
> are getting more complicated as CMake ages.)<br>
<br>
</div>FWIW this is how I assumed it would work.<br>
<br>
Is it the case that the underlying code that supports APPEND for _build<br>
and _configure would be a lot trickier for the case of _update? If so,<br>
why?<br>
<div><div></div><div class="h5"><br>
> On Wed, Feb 17, 2010 at 7:03 PM, Tyler Roscoe <<a href="mailto:tyler@cryptio.net">tyler@cryptio.net</a>> wrote:<br>
> > On Wed, Feb 17, 2010 at 04:16:15PM -0700, Clinton Stimpson wrote:<br>
> > > On 02/17/2010 03:49 PM, Tyler Roscoe wrote:<br>
> > > >On Wed, Feb 17, 2010 at 03:16:13PM -0700, Clinton Stimpson wrote:<br>
> > > ><br>
> > > >>Have you tried setting CTEST_UPDATE_OPTIONS to contain the extra<br>
> > > >>arguments for<br>
> > > >>updating the way you want?<br>
> > > >><br>
> > > >This affects the svn update command itself (which is working fine<br>
> > > >without further adjustment) but does not appear to affect the later svn<br>
> > > >log and svn status calls which (I assume) are what CTest parses to<br>
> > > >generate the Update log.<br>
> > > ><br>
> > > >Worse news for me: I don't think I can run "svn log projectA/ projectB/"<br>
> > > >to try to only get logs for those areas I care about because:<br>
> > > ><br>
> > > > svn: When specifying working copy paths, only one target may be<br>
> > given<br>
> > > ><br>
> > > >(I tried with URLs instead of working copy paths but that didn't work<br>
> > > >either.)<br>
> > > ><br>
> > ><br>
> > > What about multiple ctest_update() calls (one for each sub dir)?<br>
> > > I've put in a request for that to be handled too.<br>
> > > <a href="http://public.kitware.com/Bug/view.php?id=8263" target="_blank">http://public.kitware.com/Bug/view.php?id=8263</a><br>
> ><br>
> > It seems this would be a solution to my problem (maybe not as elegant as<br>
> > I'd<br>
> > like since I would have to include information about what a<br>
> > properly-configured working copy looks like in my build scripts (bad<br>
> > encapsulation / duplication) but I'll take what I can get :p).<br>
> ><br>
> > It looks like this feature has been implemented for ctest_configure()<br>
> > and ctest_build() via the APPEND option. Any chance it has been secretly<br>
> > added to ctest_update() but the documentation was forgotten (I'll check<br>
> > on this tomorrow unless someone happens to know)? If not, how hard would<br>
> > it be to add this functionality? Theoretically we could work from the<br>
> > examples in ctest_build() and ctest_update(), which would simplify the<br>
> > chore.<br>
</div></div></blockquote></div><br></div>