Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

[Solved] Creator: Strange compile output



  • My project compile, but lately, I get a lot of strange messages in the compile output that make it really hard to find the things I am interested in.

    Things like
    @# Not a target:
    .cc.o:

    Implicit rule search has not been done.

    Modification time never checked.

    File has not been updated.

    commands to execute (built-in):

    $(COMPILE.cc) $(OUTPUT_OPTION) $<

    Not a target:

    c:/Qt482_MinGW/mkspecs/features/include_source_dir.prf:

    Implicit rule search has been done.

    Last modified 2012-05-16 08:22:10

    File has been updated.

    Successfully updated.

    variable set hash-table stats:

    Load=0/32=0%, Rehash=0, Collisions=0/0=0%@

    (tons and tons of it).

    Can anyone enlighten me what this is supposed to mean, if there's something about my project I need to fix or how I can turn off these messages?
    I am using Qt Creator 2.8.1, Qt 4.8.2 and the MinGW version originally distributed with the old Qt SDK (3.8.1 + some patches, it seems)


  • Moderators

    Have you changed anything in your setup recently? Try doing a full rebuild (clean, run qmake, rebuild).



  • I don't remember doing any significant changes. Then again, I rarely look at the compile output, so the messages might have been there for a while.

    If I knew what they are trying to tell me, and whether they come from qmake, make, compiler or linker, I might get an idea what to do about them.


  • Moderators

    Looks like make output. See "this":http://www.gnu.org/software/make/manual/html_node/Implicit-Rule-Search.html, for example.



  • Thanks. Is there a kind of "output level", controlling the detail of make and compile output in gcc? I had hoped there would be options in Creator for that, but I haven't found anything.


  • Moderators

    You can pass -d to make to get more output.

    For g++: -v, -Wall, -Wextra, etc. Read the man page, in GCC you can really control almost anything.



  • Thanks again. Outputting less would be what I need, but I guess I'll have to search through the options.


  • Moderators

    Ah, I assumed you wanted more :P There are options for suppressing warnings, too.

    In G++, -w will inhibit all warning messages. Option -s for make will run it in silent mode.



  • I have no idea whether the messages shown above are considered warnings, or what they try to tell me. Because of them, the only way to find my actual compiler warnings is to jump to them directly from the "issues" output window. (Which isn't the worst way to do it, however)


Log in to reply