Dear Goran, my guess is, that the line numbers in the format file(line) irritate the parser - you can see the filename has the additional (line) while the line column is empty. Afaik, Intel compilers are modeled after Microsoft ones which uses such format in contrast to gcc, which has file:line:column.
I'd suggest you to create a report at bugreports.qt.io, to include the screenshots from this mail and _important_ a plain text of the compile output. If possible, include a working (C++) compiler error and a non-working (fortran). Maybe that's enough to extend the parser unit tests and make your case work. Please add a link to the bugreport here as reply so others can follow. Thanks and best regards, Andre On 22.08.21 21:06, Goran Žauhar via Qt-creator wrote:
Hi there! I have application written in Fortran and C++. CMake and ninja are used for compiling. Fortran compiler is Intel Fortran (ifort). I use QtCreator for development and I am very happy with the setup but I have one annoying issue with QtCreator: ifort warnings/errors are present in Issues tab but clicking on them does not open the file in editor. C++ issues in Issues tab work as expected - clicking on them does indeed open the file in editor and the cursor is positioned in the line with the error/warning. I have experimented with Custom Output parsers but without any luck. I have attached the screenshot of the Issues tab, Compiler Output tab and Error dialog. Can I somehow configure QtCreator to overcome this or is it issue with how QtCreator parses compiler output? Thank you, /Goran _______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
_______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
