Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. warning or else ?
Forum Updated to NodeBB v4.3 + New Features

warning or else ?

Scheduled Pinned Locked Moved Unsolved General and Desktop
3 Posts 3 Posters 382 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.
  • A Offline
    A Offline
    Anonymous_Banned275
    wrote on last edited by
    #1

    I am getting this error (C++) so why is liker missing ?
    Of I remove the QMAKE_CXXFLAGS_WARN_OFF: I get perfect compile .

    Qt_5/5.12.2/gcc_64/mkspecs/features/data/dummy.cpp
    g++: warning: QMAKE_CXXFLAGS_WARN_OFF: linker input file unused because linking not done
    g++: error: QMAKE_CXXFLAGS_WARN_OFF: linker input file not found: No such file or directory
    make[1]: *** [Makefile:730: moc_predefs.h] Error 1
    make[1]: *** Waiting for unfinished jobs....
    make[1]: Leaving directory '/home/qy/Qt/Examples/Qt-5.12.12/widgets/mainwindows/mdi'
    make: *** [Makefile:52: sub----------home-qy-Qt-Examples-Qt-5-12-12-widgets-mainwindows-mdi-make_first] Error 2
    make: *** Waiting for unfinished jobs....
    make[1]: Entering directory '/mnt/sdd6/build-MDI_Bluetooth-Desktop_Qt_5_12_12_GCC_64bit-Debug/SYSTEM'
    make[1]: Nothing to be done for 'first'.

    1 Reply Last reply
    1
    • C Offline
      C Offline
      ChrisW67
      wrote on last edited by ChrisW67
      #2

      Since you fail to share what you are actually putting in your PRO file we are left to guess what you are trying to achieve, and how you have managed to break it.

      I guess that you are attempting to disable the normal state of affairs, where the compiler is directed to issue every possible warning.
      Observations:

      1. The correct way to disable (almost) all warnings is: CONFIG += warn_off (docs).
      2. You should not need to disable warnings. Read the warnings, understand why there is a warning, and address it in your code. The compiler writers are more aware of what is a risk to correct operation of your code than either you or I.
      3. The QMAKE_* variables are generally automatically managed and rarely need direct intervention.
      1 Reply Last reply
      3
      • EndrII 0E Offline
        EndrII 0E Offline
        EndrII 0
        wrote on last edited by
        #3
        This post is deleted!
        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