<![CDATA[qc20.0 cannot open the file in console output]]>here 5.15+qc8.0 and 6.8+qc8.0:
test code:
qDebug().nospace() << "\033[34m" << "my info, file://"<<FILE<<":"<<LINE<<" good\033[0m";
录制_2026_08_10_14_50_29_20.gif

but same code fail in qc20.0+5.15:
录制_2026_08_10_14_52_49_652.gif

]]>https://forum.qt.io/topic/164992/qc20.0-cannot-open-the-file-in-console-outputRSS for NodeSun, 30 Aug 2026 11:33:34 GMTMon, 10 Aug 2026 06:57:45 GMT60<![CDATA[Reply to qc20.0 cannot open the file in console output on Fri, 21 Aug 2026 06:39:00 GMT]]>@SimonSchroeder
The question is why the change in behaviour:

but qc18 is ok, qc20 cannot open the same FILE MACRO

Your statements are true, but why does behaviour apparently differ from Creator 18 to 20?

]]>https://forum.qt.io/post/839807https://forum.qt.io/post/839807Fri, 21 Aug 2026 06:39:00 GMT<![CDATA[Reply to qc20.0 cannot open the file in console output on Fri, 21 Aug 2026 06:27:18 GMT]]>I agree that ..\main.cpp looks a little suspicious. The question is, what is your directory structure? Where is your compiled executable located? And what is the working directory when executing the program? The two have to be the same for this to work.

]]>https://forum.qt.io/post/839805https://forum.qt.io/post/839805Fri, 21 Aug 2026 06:27:18 GMT<![CDATA[Reply to qc20.0 cannot open the file in console output on Thu, 20 Aug 2026 17:50:16 GMT]]>@QtTester
After you have tried @hskoglund's suggestions.

Forget for now about __FILE__, it's not relevant in itself. By the time you click on a string in the Output window the fact that it came from a macro in C++ has no effect. You say there is a change in behaviour. You say file://..\main.cpp used to work. For now just output a literal string for whatever the absolute path of a file is. See whether that works. If it does not the problem is in clicking any link. If that works, figure out what relative path (if any) works. If that has changed then maybe QtC 20 is sitting in a different directory from before. Whatever you will know where the difference comes from.

]]>https://forum.qt.io/post/839801https://forum.qt.io/post/839801Thu, 20 Aug 2026 17:50:16 GMT<![CDATA[Reply to qc20.0 cannot open the file in console output on Thu, 20 Aug 2026 15:31:46 GMT]]>I think Qt Creator 20 works just fine with VS2022, the behavior you're seeing with the FILE macro is a bit of lottery (50/50 chance of success). To even out the odds:
try open just 1 app in Qt Creator (not 2) and bulld in release mode (not a mix of debug and release).

]]>https://forum.qt.io/post/839800https://forum.qt.io/post/839800Thu, 20 Aug 2026 15:31:46 GMT<![CDATA[Reply to qc20.0 cannot open the file in console output on Thu, 20 Aug 2026 06:28:44 GMT]]>so it's definitely qtcreator20 does not support vs2022

]]>https://forum.qt.io/post/839796https://forum.qt.io/post/839796Thu, 20 Aug 2026 06:28:44 GMT<![CDATA[Reply to qc20.0 cannot open the file in console output on Thu, 20 Aug 2026 05:57:02 GMT]]>I don'y think so (Windows filenames are the same in lower and upper case).

]]>https://forum.qt.io/post/839795https://forum.qt.io/post/839795Thu, 20 Aug 2026 05:57:02 GMT<![CDATA[Reply to qc20.0 cannot open the file in console output on Thu, 20 Aug 2026 01:47:12 GMT]]>in https://learn.microsoft.com/en-us/cpp/build/reference/fc-full-path-of-source-code-file-in-diagnostics?view=msvc-170
it says:
In Visual Studio 2017 and earlier versions, /FC outputs full paths in lower case. Starting in Visual Studio 2019, /FC uses the same casing as the file system for full paths.

it's because the upper case?

]]>https://forum.qt.io/post/839794https://forum.qt.io/post/839794Thu, 20 Aug 2026 01:47:12 GMT<![CDATA[Reply to qc20.0 cannot open the file in console output on Thu, 20 Aug 2026 01:37:20 GMT]]>@hskoglund but qc18 is ok, qc20 cannot open the same FILE MACRO

]]>https://forum.qt.io/post/839793https://forum.qt.io/post/839793Thu, 20 Aug 2026 01:37:20 GMT<![CDATA[Reply to qc20.0 cannot open the file in console output on Tue, 11 Aug 2026 02:02:11 GMT]]>Hi, I think the FILE macro is not the best way to find your main.cpp file since it usually skips giving you the full path to the file. For the MSVC compiler you can try the /FC compile switch

]]>https://forum.qt.io/post/839647https://forum.qt.io/post/839647Tue, 11 Aug 2026 02:02:11 GMT<![CDATA[Reply to qc20.0 cannot open the file in console output on Tue, 11 Aug 2026 00:47:45 GMT]]>no one has this problem?

]]>https://forum.qt.io/post/839646https://forum.qt.io/post/839646Tue, 11 Aug 2026 00:47:45 GMT