Hi,
That sounds like a bug. If you don’t mind, create a ticket at
https://bugreports.qt.io/. That should be the fastest way to get it fixed.
Cheers,
Marcus
> On 15. May 2024, at 13:25, Toralf Lund <tor...@toralf.net> wrote:
>
> Hi
>
> I'm trying to set up Qt Creator for debugging on a "bare metal" device. (ARM
> system, using JTAG POD with built-in GDB server.)
>
> I think I can generally get this to work, but I'm experiencing an issue with
> the Run configuration: It seems like Qt Creator variables can't be used in
> "Executable" and "Working directory" settings. I mean, I get the normal
> "variables" icon and can select from a list etc., but it looks like nothing
> is ever expanded; if for instance I set Executable to
> "%{sourceDir}/executablename" and try to start debugging, I get
>
> Cannot debug: Could not find executable for "%{sourceDir}/exectablename".
>
> in the Application Output view.
>
> Note that I see this only for settings connected to the kit for my device.
> With the same configuration under Desktop, the debugger is started as
> expected, or if the file is actually missing, "%{sourceDir}" is replaced by
> the real source directory path in error messages.
>
> Has anyone else seen this? Is it a known error or limitation? Or am I missing
> something? Should I set up something else somewhere or use different
> variables or something?
>
> My goal is to avoid hard-coded full paths, for a shareable/version control
> system-friendly configuration...
>
> Some meta question (kind of) while I'm at it: I don't see a lot of traffic on
> this list. Does this mean there is a different (better) alternative way of
> asking questions? Or could it mean nobody is actually using Qt Creator. :-/ ?
>
> Thanks,
>
> - Toralf
>
> --
> 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
