Expose qtests through buildsystem
apaku at gmx.de
Sun Jun 22 10:29:19 UTC 2008
On 21.06.08 22:56:22, Manuel Breugelmans wrote:
> On Saturday 21 June 2008 12:06:31 Andreas Pakulat wrote:
> > On 21.06.08 10:41:13, Manuel Breugelmans wrote:
> > > Right, thats exactly why that .shell should be called from xtest. No need
> > > for messing with library paths nor unix signals. Anyway forget about it,
> > > I'll just do + ".shell".
> > The problem is that only CMake supports that (and IIRC libtool too). But
> > for custom makefiles, custom buildsystems and even qmake you'll have to
> > fiddle around with at least the libraries.
> > I'm not sure I understand why you need to know wether a test aborts or
> > segfaults. Is that really needed for the results? Its failing in any
> > case and whoever looks at the results needs to look at the test too -
> > possibly running it manually to double-check why it fails. Did I miss
> > something?
> > Andreas
> Idea is to provide the same level of information as the cli version, not less.
> Not being able to tell a user the difference between a segfault, c-assert()
> or something else is a pretty big drawback in my book.
Ok, I personally don't see the need in practice, but this is your
project and I don't have real objections against it :)
Don't look now, but there is a multi-legged creature on your shoulder.
More information about the KDevelop-devel