2010/1/28 Michael Pyne <[email protected]>: > On Thursday 28 January 2010 09:51:45 John Tapsell wrote: >> Hey all, >> >> 3) It's just feels "transparent" and doesn't get in the way. It >> doesn't hide compiler messages or anything, and it becomes normal to >> just use jhbuild to build even normally. >> 5) Did I mention that it works transparently? It just doesn't get in the >> way. > > Given that you've mentioned it twice, I would like to know what is horribly > non-transparent about kdesvn-build. That way when the rest of the world > switches wholesale to jhbuild I'll still at least be able to fix that for > those still using kdesvn-build.
When compiling, the output from kdesvn-build is not the output from cmake. So it's "feels" like you are running an automated script to compile. Compile errors and compile warnings are hidden. If there's a compile failure, kdesvn does not tell you what that error is and continues onto the next module. John _______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
