Changeset baac59c for x/lib/qtwebengine.xml
- Timestamp:
- 03/21/2020 11:42:20 AM (4 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 6d106671
- Parents:
- 71df408
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
x/lib/qtwebengine.xml
r71df408 rbaac59c 57 57 Please note that if you try to build webengine as part of 58 58 <application>Qt</application> and the static library is not available, 59 that build will either complete without installing webengine, or else fail60 during the install (both variants have been observed in 5.12.0).59 that build will either complete without installing webengine, or else 60 fail during the install (both variants have been observed in 5.12.0). 61 61 </para> 62 62 </note> … … 274 274 recognize the NINJAJOBS environment variable, this command will run system 275 275 ninja with the specified number of jobs (i.e. 4). 276 There are several reasons why you might want to do this:</para> 276 There are several reasons why you might want to do this: 277 </para> 277 278 278 279 <itemizedlist> 279 280 <listitem> 280 <para> Building on a subset of CPUs allows measuring the build time 281 for that number of processors or to run other CPU-intensive tasks on 282 other cores.</para> 283 </listitem> 284 <listitem> 285 <para>Improving the build speed on a less-well endowed 4-core 286 machine. On a machine with a powerful CPU and plenty of RAM, running 287 N+2 jobs (the ninja default for 4+ cores) for the large working sets 288 of the C++ compiles in this package is typically only marginally 289 faster than running N jobs at a time. But for a machine with less 290 memory it can be much slower.</para> 291 </listitem> 292 <listitem> 293 <para>Reducing the number of cores being used on long running, CPU 294 intensive packages may alleviate heat problems.</para> 281 <para> 282 Building on a subset of CPUs allows measuring the build time 283 for that number of processors or to run other CPU-intensive tasks on 284 other cores. 285 </para> 286 </listitem> 287 <listitem> 288 <para> 289 Improving the build speed on a less-well endowed 4-core machine. 290 On a machine with a powerful CPU and plenty of RAM, running N+2 291 jobs (the ninja default for 4+ cores) for the large working sets 292 of the C++ compiles in this package is typically only marginally 293 faster than running N jobs at a time. But for a machine with less 294 memory it can be much slower. 295 </para> 296 </listitem> 297 <listitem> 298 <para> 299 Reducing the number of cores being used on long running, CPU 300 intensive packages may alleviate heat problems. 301 </para> 295 302 </listitem> 296 303 </itemizedlist>
Note:
See TracChangeset
for help on using the changeset viewer.