Re: gcc-5 transition of GDCM
> Fine! With your updated version of gccxml, I was able to fix several build
> errors in the gdcm package. I had to apply one patch [1].
>
> Unfortunately, there are still build errors related to mummy that read as
> follow: [...]
Pursuing my investigations, I have just noticed that the argument "--castxml-start=" seems to be non properly understood by castxml.
To spot this problem, I have included inside the "/usr/bin/gccxml" wrapper around castxml, a "print castxml_cmd" command to display the command that is invoked when running CMake. Here is the output:
=====
[ 0%] Generating xml/vtkGDCMImageReader.xml
cd /tmp/build-area/gdcm-2.4.4/obj-x86_64-linux-gnu/Utilities/VTK && /usr/bin/gccxml -fxml-start=_cable_ -I/usr/include/mummy-1.0.3 -I/usr/include/vtk-5.8 -DCABLE_CONFIGURATION /tmp/build-area/gdcm-2.4.4/obj-x86_64-linux-gnu/Utilities/VTK/xml/vtkGDCMImageReader_gccxml.cxx -Wno-deprecated -fxml=/tmp/build-area/gdcm-2.4.4/obj-x86_64-linux-gnu/Utilities/VTK/xml/vtkGDCMImageReader.xml
TRANSLATION from gccxml to castxml:
['/usr/bin/castxml', '--castxml-start', '_cable_', '-I/usr/include/mummy-1.0.3', '-I/usr/include/vtk-5.8', '-DCABLE_CONFIGURATION', '/tmp/build-area/gdcm-2.4.4/obj-x86_64-linux-gnu/Utilities/VTK/xml/vtkGDCMImageReader_gccxml.cxx', '-Wno-deprecated', '--castxml-gccxml', '-o', '/tmp/build-area/gdcm-2.4.4/obj-x86_64-linux-gnu/Utilities/VTK/xml/vtkGDCMImageReader.xml']
error: no such file or directory: '_cable_'
=====
As you notice, the "-fxml-start=_cable_" argument is replaced by two "--castxml-start _cable_" arguments, which is the proper behavior according to the manual of castxml:
=====
--castxml-start <name>[,<name>]...
Start AST traversal at declaration(s) with the given (qualified) name(s). Multiple names may be specified as a comma-separated list or by
repeating the option.
=====
The error "no such file or directory: '_cable_'" is however totally unexpected, as the expected argument to "--castxml-start" is a comma-separated list of qualified names, and not a file. This looks as a bug inside castxml. Steve, do you have any idea?
Sébastien-
Reply to: