mpyne at kde.org
Fri Jan 29 01:41:52 CET 2010
On Thursday 28 January 2010 19:29:15 John Tapsell wrote:
> 2010/1/28 Michael Pyne <mpyne at kde.org>:
> > 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.
Oh, I was afraid it was something like it's unclear how to build or update a
module or something.
I was long ago enlightened by unsermake (and probably more by Gentoo...) that
I usually have no need to watch output scroll by so that's why kdesvn-build
doesn't show it by default. (You can add the --debug option to see it but
you'll also get a ton more other useless noise in the process)
I did once have code (or maybe still do?) to try and intelligently grep the
error message for a failed build but could never get it accurate enough. Meh.
Sounds like it really annoys though, for which I'm sorry I guess, but I
definitely prefer it this way. Logged output (even if the output is also shown
on stdout) is far superior if only because you don't have to fix one error,
build and fail on a different module, rinse/repeat, but instead you can always
"scrollback" to where the error was unlike Linux TTYs or Konsole with a non-
infinite scrollback buffer. :)
As far as jhbuild goes then if it can be easily made to work I'm all for it
but I don't intend to work on it as I've got quite enough to do at this rate
already. Either way we don't even have an official build tool now (otherwise
you'd think kdesvn-build would be the TechBase "How to Build" article! ;) so I
see it as yet another useful alternative.
- Michael Pyne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20100128/7d24feb5/attachment.sig
More information about the Kde-scm-interest