On Wed, Jun 24, 2015 at 03:47:15PM +0100, Edmund Grimley Evans wrote: > > Of the others on your list: do they make much use of gccxml output? > > Are there tests for that? > > I don't know the answers. All I did was blindly run dpkg-buildpackage > on the packages I listed. However, a quick google/grep suggests that > python wrapping is only available for insighttoolkit4, which I haven't > built yet. The build logs at buildd.debian.org might give an idea of > what tests are run.
Correct: insighttoolkit doesn't provide any wrappings. It was too painful :-( ITK v4 provides python bindings; but as you no doubt know, it builds only for a very restricted set of architectures. > This article (http://www.kitware.com/blog/home/post/888) suggests that > upstream has already switched to CastXML, though Debian's current > insighttoolkit4 Build-Depends on gccxml. Right, because the blog is about the current development code. Hopefully castxml will be in the next release. Current ITK releases still use gccxml. > The ghastly arm64/ppc64el kludge has a reasonable chance of working, > perhaps, because those two architectures seem to have the same sizes > and alignments and signedness of basic types: > https://wiki.debian.org/ArchitectureSpecificsMemo If there is a > critical difference between the two architectures, it would be > interesting to know what it is. OK, given that -- and the fact that gccxml is end of life anyway -- I'm OK to include your patch. Thanks, -Steve
signature.asc
Description: Digital signature
