Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. Prevent generation of qt.conf
Forum Updated to NodeBB v4.3 + New Features

Prevent generation of qt.conf

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
2 Posts 2 Posters 244 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    purplehorace
    wrote on last edited by purplehorace
    #1

    Hello All
    I have searched a lot and cannot find an answer to my problem

    I have an embedded platform that I am successfully cross compiling Qt6.8.x applications/demos for and deploying them for remote debug.

    When launching the application I noticed that it would fail:

    Remote debugging from host 10.0.0.152, port 47390
    Process /home/purplehorace/bin/particles3d created; pid = 8529
    QML debugging is enabled. Only use this in a safe environment.
    Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
    Qt depends on a UTF-8 locale, but has failed to switch to one.
    If this causes problems, reconfigure your locale. See the locale(1) manual
    for more information.
    qt.qpa.wayland: No shell integration named "xdg-shell" found
    qt.qpa.wayland: No shell integration named "wl-shell" found
    qt.qpa.wayland: No shell integration named "ivi-shell" found
    qt.qpa.wayland: No shell integration named "qt-shell" found
    qt.qpa.wayland: Loading shell integration failed.
    qt.qpa.wayland: Attempted to load the following shells QList("xdg-shell", "wl-shell", "ivi-shell", "qt-shell")
    qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
    This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
    
    Available platform plugins are: wayland.
    
    Process exited with code: 0.
    

    If I delete the qt.conf file, which just has the contents of:

    [Paths]
    Prefix = ..
    

    The application will start and run without issue.

    Is there any way to disable the generation and deployment of the qt.conf file ?

    Thanks for your help.

    1 Reply Last reply
    0
    • hskoglundH Offline
      hskoglundH Offline
      hskoglund
      wrote on last edited by
      #2

      Maybe you can get around this problem by creating an empty qt,conf file at a place with higher priority than the current directory, I'm thinking of storing it in your executable as a resource ( i.e. :/qt/etc/qt.conf) more here: https://doc.qt.io/qt-6/qt-conf.html

      P.S. If Qt does not like an empty qt.conf, try (almost) the same as above:
      [Paths]
      Prefix = .

      1 Reply Last reply
      0

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved