Buildd-setup faffing around with __FILE__ breaks my unit tests.

[Ximin Luo]

Sune Vuorela:
> [..]
> 
> What would you suggest changing the macro to ?  I can then try push it 
> upstream.
>  
>> Lots of other test runners do perfectly well without __FILE__, QT tests are
>> not special.
> 
> I haven't yet found a c++ test system that actually has this feature. The 
> internet suggests either rolling your own macro around __FILE__ or pass the 
> source dir in thru the build system somehow, or as command line arguments 
> Pointers are more than welcome.
> 

Yes, pass the source dir in through the build system "somehow", there are lots of possible ways you can do this, and this is what every other test runner does. A command-line argument or environment variable would be simplest.

Test runners all work in very similar ways and a large number of them have to be flexible enough to work on out-of-tree builds, the "C++" here should not be a barrier to anything I've suggested.

> If you have any good ideas, I'm all ears, but right now, I don't find your 
> style of communication in any way constructive.
> 

I don't find your style of communication constructive either. You dismissed my previous explanations and constructive suggestions, started quoting documentation like I didn't already previously read it, and are implying lots of other projects should do work but somehow QT should be exempt.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git