Databases
StackOverflow2013
Postsdbo
POQt Moc'ing multiple files in parallel under msbuild
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POQt Moc'ing multiple files in parallel under msbuild
    primarykey
    data
    text
    <p>Using the Qt Visual studio plugin it seems to take care of most of almost everything in a seemless manner. Unfortunately it does the moc'ing using a CustomBuild step in msbuild. This results in a serial moc'ing, one after another. Is there a way to convince msbuild to do them in parallel - I'm tired of 7 cores sitting on their laurels like me.</p> <p>I've seen msbuild's BuildInParallel, but I'm not sure how to make that apply here.</p> <p>msbuild snippet: </p> <pre><code>&lt;Project&gt; ... &lt;ItemGroup&gt; &lt;CustomBuild Include="a_class4.h"&gt; &lt;AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"&gt;$(QTDIR)\bin\moc.exe;%(FullPath)&lt;/AdditionalInputs&gt; &lt;Message Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"&gt;Moc%27ing %(Identity)...&lt;/Message&gt; &lt;Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"&gt;.\GeneratedFiles\$(ConfigurationName)\moc_%(Filename).cpp&lt;/Outputs&gt; &lt;Command Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"&gt;"$(QTDIR)\bin\moc.exe" "%(FullPath)" -o ".\GeneratedFiles\$(ConfigurationName)\moc_%(Filename).cpp" -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_CORE_LIB -DQT_GUI_LIB "-I." "-I.\GeneratedFiles" "-I$(QTDIR)\include" "-I.\GeneratedFiles\$(ConfigurationName)\." "-I$(QTDIR)\include\qtmain" "-I$(QTDIR)\include\QtCore" "-I$(QTDIR)\include\QtGui" "-I." "-I." "-I." "-I."&lt;/Command&gt; &lt;/CustomBuild&gt; &lt;CustomBuild Include="a_class3.h"&gt; &lt;AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"&gt;$(QTDIR)\bin\moc.exe;%(FullPath)&lt;/AdditionalInputs&gt; &lt;Message Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"&gt;Moc%27ing %(Identity)...&lt;/Message&gt; &lt;Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"&gt;.\GeneratedFiles\$(ConfigurationName)\moc_%(Filename).cpp&lt;/Outputs&gt; &lt;Command Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"&gt;"$(QTDIR)\bin\moc.exe" "%(FullPath)" -o ".\GeneratedFiles\$(ConfigurationName)\moc_%(Filename).cpp" -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_CORE_LIB -DQT_GUI_LIB "-I." "-I.\GeneratedFiles" "-I$(QTDIR)\include" "-I.\GeneratedFiles\$(ConfigurationName)\." "-I$(QTDIR)\include\qtmain" "-I$(QTDIR)\include\QtCore" "-I$(QTDIR)\include\QtGui" "-I." "-I." "-I." "-I."&lt;/Command&gt; &lt;/CustomBuild&gt; &lt;/ItemGroup&gt; ... &lt;/Project&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USaldo
    1. USZac
    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. POQt Moc'ing multiple files in parallel under msbuild
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POQt Moc'ing multiple files in parallel under msbuild
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POQt Moc'ing multiple files in parallel under msbuild
      1. USaldo
      1. VTFavorite
    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