Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. A console window appears after deployment
QtWS25 Last Chance

A console window appears after deployment

Scheduled Pinned Locked Moved Installation and Deployment
console deploym
4 Posts 2 Posters 1.1k Views
  • 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.
  • S Offline
    S Offline
    StephanWoebbeking
    wrote on last edited by
    #1

    Hi,

    after I have successfully build an installer (WiX Toolset v3.8) for my Qt application (Qt Creator 3.1.1), there is a console window opening together with the MainWindow when I start my application. All the log messages from within the application (the ones that are usually caught by Qt Creator in the bottom window) are reported there. This window is not opening when I start the application from the IDE nor when I start it manually from the build directory (debug or release). Build and Deployment both happens on Windows 7 systems.

    Here is an extract from my project file:

    Project file

    QT += testlib widgets serialport webkitwidgets network
    
    CONFIG += c++11
    
    TARGET = ServiceApplication
    TEMPLATE = app
    
    SOURCES += \
        main.cpp \
    ...
        ../ServiceTools_Shared_QT/PF_Wennebostel/wbstlDevSRX2G4.cpp
    
    HEADERS += \
        mainwindow.h \
    ...
        ../ServiceTools_Shared_QT/PF_Wennebostel/wbstlDevPTX2G4.h
    
    FORMS += \
        mainwindow.ui \
        settingsdialog.ui
    
    RESOURCES += \
        ServiceApplication.qrc
    
    OTHER_FILES +=
    
    LIBS += -L$$PWD/../senn_msg_api/ -lsennheiser_msg_api
    LIBS += -LD:/DataVCS2/wennebostel_service/RtxEaiPortServer/ -lRtxProdTest
    LIBS += -LD:/DataVCS2/wennebostel_service/RtxEaiPortServer/ -lRepsClient
    
    INCLUDEPATH += $$PWD/../senn_msg_api/
    INCLUDEPATH += D:/DataVCS2/wennebostel_service/RtxEaiPortServer/
    DEPENDPATH += $$PWD/../senn_msg_api/
    DEPENDPATH += D:/DataVCS2/wennebostel_service/RtxEaiPortServer/
    

    Any idea what I am missing here?

    Thanks,
    Stephan

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #2

      Hi,

      I'd say the testlib is responsible. You should not use it in production code. It's only meant for testing

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      S 1 Reply Last reply
      0
      • SGaistS SGaist

        Hi,

        I'd say the testlib is responsible. You should not use it in production code. It's only meant for testing

        S Offline
        S Offline
        StephanWoebbeking
        wrote on last edited by
        #3

        @SGaist Does that mean that I have to exclude each and every qDebug call by preprocessor if's related to a DEBUG definition? Or would it be enough to install this specific detour function and send everything to NIL when it's not in debugging mode?

        Stephan

        1 Reply Last reply
        0
        • SGaistS Offline
          SGaistS Offline
          SGaist
          Lifetime Qt Champion
          wrote on last edited by
          #4

          No, it means that you should not use the QTest module in your application

          Interested in AI ? www.idiap.ch
          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

          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