Databases
StackOverflow2013
Postsdbo
POQt moc.exe not generating *.moc file
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POQt moc.exe not generating *.moc file
    primarykey
    data
    text
    <p>I'm trying to build the <em>qtestlib/tutorial1 example</em>, but the <em>testqstring.moc</em> file isn't being generated when I run <code>nmake</code> (I'm running Qt 4.5.2 on Windows XP SP3).<br> I copied <em>testqstring.cpp</em> from the tutorial directory to my build directory (<em>C:\sandboxes\testqstring</em>) and from the Qt command prompt ran vsvars32.bat file from my MS Visual Studio 8 installation to add the VS environment variables.</p> <p>According to the tutorial, I should run:</p> <pre><code>&gt; qmake -project "CONFIG += qtestlib" &gt; qmake &gt; nmake </code></pre> <p>When I do, the output from <code>nmake</code> is:</p> <blockquote> <p>C:/Apps/Qt/2009.03/qt/bin\moc.exe -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_TESTLIB_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I"....\Apps\Qt\2009.03\qt\include\QtCore" -I"....\Apps\Qt\2009.03\qt\include\QtGui" -I"....\Apps\Qt\2009.03\qt\include\QtTest" -I"....\Apps\Qt\2009.03\qt\include" -I"." -I"....\Apps\Qt\2009.03\qt\include\ActiveQt" -I"debug" -I"....\Apps\Qt\2009.03\qt\mkspecs\win32-g++" -D__GNUC__ -DWIN32 testqstring.cpp -o debug\testqstring.moc</p> <p>g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_TESTLIB_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I"....\Apps\Qt\2009.03\qt\include\QtCore" -I"....\Apps\Qt\2009.03\qt\include\QtGui" -I"....\Apps\Qt\2009.03\qt\include\QtTest" -I"....\Apps\Qt\2009.03\qt\include" -I"." -I"....\Apps\Qt\2009.03\qt\include\ActiveQt" -I"debug" -I"....\Apps\Qt\2009.03\qt\mkspecs\win32-g++" -o debug\testqstring.o testqstring.cpp</p> <p>testqstring.cpp:63:27: testqstring.moc: No such file or directory<br> NMAKE : fatal error U1077: 'C:\Apps\Qt\2009.03\mingw\bin\g++.EXE' : return code '0x1' Stop.<br> NMAKE : fatal error U1077: 'C:\PROGRA~1\MICROS~3\VC\BIN\nmake.exe' : return code '0x2' Stop.</p> </blockquote> <p>So, I can see that moc.exe is being called to generate debug/testqstring.moc, but that file is never generated.</p> <p>Thank you for any and all guidance you can provide.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USDoug Cuthbertson
    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
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POQt moc.exe not generating *.moc file
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POQt moc.exe not generating *.moc file
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POQt moc.exe not generating *.moc file
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan you include the .pro file generated when running the first command?
      singulars
      1. POQt moc.exe not generating *.moc file
      1. USRopez
    2. COI had the same problem. But I solved it by removing file qt.conf from <qtpath>/bin directory.
      singulars
      1. POQt moc.exe not generating *.moc file
      1. This table or related slice is empty.
 

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