[Qt-creator] Has anyone got the new custom parsers running?

[André Hartmann]

Hi Christian,

I'm feeling stupid now... I totally missed the fact that the parser 
needs to be enabled in the projects Run settings - which totally makes 
sense.

You already have a hint there where to configure the parsers, however 
having a hint in the reverse direction would have helped:

https://codereview.qt-project.org/c/qt-creator/qt-creator/+/309675

Thank you all for your help, it works nicely now.

Best regards,
André

Am 07.08.20 um 15:12 schrieb Christian Stenger:
> Hi Andre,
> 
> I had a similar issue...: you have custom output parsers on the build *and* on the run settings of a project.
> I had added them only to the build settings and wondered as well.. Enabling them on the run settings helped here..
> 
> BR,
> Christian
> 
> ________________________________________
> From: Qt-creator <qt-creator-bounces at qt-project.org> on behalf of Christian Kandeler <christian.kandeler at qt.io>
> Sent: Friday, August 7, 2020 2:56 PM
> To: qt-creator at qt-project.org
> Subject: Re: [Qt-creator] Has anyone got the new custom parsers running?
> 
> On Fri, 7 Aug 2020 14:02:06 +0200
> André Hartmann <andre.hartmann at iseg-hv.de> wrote:
> 
>> I've created a project with a main.cpp like that:
>>
>> #include <stdio.h>
>>
>> int main()
>> {
>>        printf("main.cpp:5: Hello World\n");
>>        return 0;
>> }
>>
>> Running that gives me the following Application Output:
>>
>> 13:49:52: Starting /home/user/build-Test/Test ...
>> main.cpp:5: Hello World
>> 13:49:52: /home/user/build-Test/Test exited with code 0
>>
>> I've then added a new Custom Output Parser in Tools > Options >
>> Build & Run > Custom Output Parsers with the following
>> pattern: "(.*):(\d+): (.*)" (without quotes, of course), which
>> passed the test text "main.cpp:5: Hello World" (without quotes) in
>> the  Custom Parser dialog. Capturing stdout and stderr was both enabled.
>>
>> After pressing Ok, I've run my program again, the output appeared in
>> Application Output, but nothing happened in the Issues pane.
>>
>> I've expected the message to appear in the Issues pane.
>>
>> Is there any obvious wrong in my test?
> 
> No, and your example works for me.
> Are you sure you're not filtering anything relevant? Note that custom parsers currently all have the type "compile output", even for run configurations.
> 
> 
> Christian
> _______________________________________________
> Qt-creator mailing list
> Qt-creator at qt-project.org
> https://lists.qt-project.org/listinfo/qt-creator
> _______________________________________________
> Qt-creator mailing list
> Qt-creator at qt-project.org
> https://lists.qt-project.org/listinfo/qt-creator
> 


-- 
André Hartmann, Dipl. Ing. (FH)
Softwareentwicklung / Software Development

E-Mail: andre.hartmann at iseg-hv.de
Tel: +49.351.26996-43 | Fax: +49.351.26996.21

iseg Spezialelektronik GmbH - HIGH VOLTAGE. EXACTLY.
iseg-hv.de | iseg-hv.com | download.iseg-hv.com

Bautzner Landstr. 23, 01454 Radeberg / Rossendorf, Germany
Geschäftsführer / Managing directors: Dr. Tanju Gleisberg, Tobias Pöthig
Amtsgericht / Lower district court: Dresden HRB 16250
Umsatzsteuer-Id: / VAT-ID: DE812508942

iseg on LINKEDIN | Let´s stay connected!
iseg on YOUTUBE | Tutorials and more ...
iseg on TWITTER | please follow!
iseg CATALOG | download iseg´s latest product catalog as PDF
iseg DOWNLOADS | manuals, software, firmware and more...
iseg high voltage power supply

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail. Das unerlaubte
Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht
gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail
in error) please notify the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.