On Tue, 5 May 2020 19:56:02 +1000 Marc Reilly <marc.rei...@gmail.com> wrote:
> The "Add build library search path" option was already checked, but I also > noticed the "Run in terminal" option was also checked ... unchecking this > allowed the program to run. > So, I'm guessing that its something to do with launching the console (in > this case 'konsole') and the mix of the Qt libs from the system and from > QtC install. Yes, if your terminal also uses Qt, then you're out of luck -- either the terminal or your application will fail. You need to use a non-Qt-based terminal then, or build your app with rpath. > If I create a new 'Run configuration', the "Run in terminal" option is > checked by default, but I'm ok with working around this for now ... This happens if Creator considers this a console application. However, it seems no one wants this behavior, so I think we'll change the default in the next version. > I'm not sure if this is really a QtC bug It is not. > or some other system issue more > specific to me, so I haven't lodged a bug report as yet. Any other tips > welcome. (Is there a way to change which console QtC uses by default?) The respective setting is in Tools -> Options -> Environment -> System. As for the default value, there is a hardcoded list of which the first one that is found is used. konsole comes pretty late in that list, so it seems you don't have any of the others installed. Christian _______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
