Databases
StackOverflow2013
Postsdbo
POErrors in QT headers using clang
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POErrors in QT headers using clang
    primarykey
    data
    text
    <h1>Questions:</h1> <hr> <p>My question is thus: How do I build my QT project without turning off warnings altogether (or having to sort through a million purposeless ones to find my own)? Can I suppress warnings for just the QT headers?</p> <h1>Details:</h1> <hr> <h3>Issue</h3> <hr> <p>A number of months ago, I started a QT project in QT-Creator. At the time I was using gcc 4.6. After a bit other priorities asserted themselves and I found myself without time to work on the project until now. In the interim I switched to using clang. When I configured my QT project to use clang -- which project compiled without warnings in g++ -- it generated some 263 warnings all within the QT headers themselves. Mostly sign-conversion and unreachable-code.</p> <hr> <h3>Attempts</h3> <hr> <p>To try and get around this I added -isystem /path/to/QT/include/dir based on <a href="http://clang.llvm.org/docs/UsersManual.html#controlling-diagnostics-in-system-headers">this entry in the Clang User Manual</a>, but it did not seem to affect anything. Though I am not certain, I think it is because my code <code>#include</code>'s the QT headers by name, not by directory. While the solution to that might be to manually list every single QT header used (have not tried), it would mean I would have to update it every time I upgraded QT or used a new header. Surely there is a better solution.</p> <p>As requested here is the actual compile command being executed:</p> <pre><code>clang++ -c -pipe -Qunused-arguments -Weverything -cxx-isystem /path/to/qt/4.8.3/include/ -g -D_REENTRANT -DQT_NO_KEYWORDS -DQT_SHARED -I/path/to/qt/x86_64/4.8.3/mkspecs/unsupported/linux-clang -I. -I.moc -I.ui -I/path/to/qt/4.8.3/include/ -o .obj/main.o main.cpp </code></pre> <hr> <h3>Specs</h3> <hr> <p>I am using:</p> <ul> <li>Linux 3.2.0-40-generic #64-Ubuntu SMP x86_64 GNU/Linux <ul> <li>Though others on my team use Windows</li> </ul></li> <li>QT creator 2.6.2 </li> <li>QT 4.8.3</li> <li>clang version 3.2 (trunk 165250) (llvm/trunk 165249) <ul> <li>Target: x86_64-unknown-linux-gnu</li> </ul></li> </ul>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USTsubashi
    1. USTsubashi
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POErrors in QT headers using clang
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POErrors in QT headers using clang
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POErrors in QT headers using clang
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 for format :)
      singulars
      1. POErrors in QT headers using clang
      1. USstardust
    2. COWhere is the actual command line used to compile the code? Do not describe in elaborate prose what you can copy and paste.
      singulars
      1. POErrors in QT headers using clang
      1. USn.m.
    3. COUpdated to include the compile command
      singulars
      1. POErrors in QT headers using clang
      1. USTsubashi
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload