Hi Knut, Can you explain why you need to patch the paths?
If you build remotely, I have a script that translates paths on stderr, which I can share if it helps you. - Orgad On Tue, Aug 22, 2023 at 6:14 PM Knut Petter Svendsen via Qt-creator < qt-creator@qt-project.org> wrote: > My build system utilizes the GccParser to identify compiler errors, and > that works fine. However, I'm currently exploring an approach to "patch" > the filepaths associated with the created tasks. I've been considering > subclassing the GccParser, but most of it is private. If only > createOrAmendTask() was protected it might have been possible. flush() is > virtual, but it can't access the private data. > > Are you aware of any elegant way to achieve this goal, or am I required to > duplicate the code? > > If I create my own parser which duplicates, I would have to ensure > GccParser is not active or else I would end up with duplicate issues in > the taskhub, right? > > Knut > > -- > 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
