On 2020-12-16 18:45 +0100, Stacho Mudrak wrote: > VTK9 should be OK, no need to use older versions.
Done. Therion is stuck waiting for current vtk package to transition to testing, and both are stuck because the mipsel buildds can't keep up but it should be OK in a week or so. > Exception catching has been removed from samples intentionally. We use > them as a series of tests when implementing a CMake build system. I did > not know, that samples are built on Debian. We've been doing that for many, many years as it provides some useful local documentation (although, checking, I see that the resolution of some of the images is too low to be useful). I chose not to use cavern so that the back-up calculation system in therion got tested. That seemed more appropriate for the therion build. It also simplified the build-dependency tree a little. > There is an option to have generated .3d files also present in the > samples. But adding cavern as a build-dependency seems to me as a better > idea in any case. And using it for the loop closure. OK. But then the therion back-up functionality may hardly ever get tested? Now that we have autopackage tests (tests run after the build on the installed packages), I guess we could run some tests both with and without cavern installed (maybe - not sure if we have that level of control). But we don't have the sample sources available to run a runtime, only at build-time. Using cavern is the 'normal' case so maybe it's better to do that at build-time too. I'll try it. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/
signature.asc
Description: PGP signature
_______________________________________________ Therion mailing list [email protected] https://mailman.speleo.sk/listinfo/therion
