- Timestamp:
- 02/16/2018 06:13:40 AM (6 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, perl-modules, 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:
- ccc19e1b
- Parents:
- c8216c3d
- Location:
- x/lib
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
x/lib/qt5.xml
rc8216c3d r088e7e06 10 10 <!ENTITY qt5-download-http "&qt5-url;/qt-everywhere-src-&qt5-version;.tar.xz"> 11 11 <!ENTITY qt5-download-ftp " "> 12 <!ENTITY qt5-md5sum " c5e275ab0ed7ee61d0f4b82cd471770d">13 <!ENTITY qt5-size " 289MB">14 <!ENTITY qt5-buildsize " 9.6 GB (225MB installed)">15 <!ENTITY qt5-time " 29.8SBU (using parallelism=4)">12 <!ENTITY qt5-md5sum "7e167b9617e7bd64012daaacb85477af"> 13 <!ENTITY qt5-size "391 MB"> 14 <!ENTITY qt5-buildsize "10.1 GB (238 MB installed)"> 15 <!ENTITY qt5-time "30 SBU (using parallelism=4)"> 16 16 ]> 17 17 -
x/lib/qtwebengine.xml
rc8216c3d r088e7e06 8 8 <!ENTITY qtwebengine-download-http "https://download.qt.io/archive/qt/&qtwebengine-major;/&qtwebengine-version;/submodules/qtwebengine-everywhere-src-&qtwebengine-version;.tar.xz"> 9 9 <!ENTITY qtwebengine-download-ftp " "> 10 <!ENTITY qtwebengine-md5sum "0ea0b32e97911cf80d32b31cf10a6d8b"> 11 <!ENTITY qtwebengine-size "208 MB"> 12 <!ENTITY qtwebengine-buildsize "3.3 GB (144 MB installed)"> 13 <!ENTITY qtwebengine-time "95 SBU (using 4 cores)"> 14 15 <!-- Both qmake and ninja will use all available cores, in fact ninja runs n+2 16 jobs at a time. Most of our readers do not have more than 4 cores. 17 To reduce the number of available cores for measuring the build time: 18 # echo 0 > /sys/devices/system/cpu/cpu4/online 19 and repeat for each subsequent cpu. Never do this for cpu0. 20 You can cat /sys/devices/system/cpu/{online,offline} to check. 21 To reinstate the cores after measuring, echo 1 to the same files. --> 10 <!ENTITY qtwebengine-md5sum "77374c184f2ff5005d1c61a32ea38491"> 11 <!ENTITY qtwebengine-size "201 MB"> 12 <!ENTITY qtwebengine-buildsize "3.2 GB (137 MB installed)"> 13 <!ENTITY qtwebengine-time "43 SBU (using 4 cores)"> 22 14 ]> 23 15 … … 49 41 50 42 &lfs81_checked; 51 52 <note><para>Both qmake and ninja will use all available cores when 53 building. There is no conveninet way to control the number of cores 54 used during the build.</para></note> 43 44 <note><para>By default, ninja will use all online CPUs +2 (if at least 45 4 exist), even if they are not available to the current task because the 46 build terminal has been restricted with 'taskset'. To work around this, 47 see the Command Explanations below.</para></note> 55 48 56 49 <bridgehead renderas="sect3">Package Information</bridgehead> … … 178 171 <command>qmake</command>: This will build the included copy of 179 172 <application>ninja</application> if it is not already installed 180 and use it to configure the build. That and the subsequent 181 <command>make</command> command will use all available CPU cores. 173 and use it to configure the build. 174 </para> 175 176 <para> 177 <option>NINJAJOBS=4 make</option>: If you patched system ninja in LFS to 178 recognize the NINJAJOBS environment variable, this command will run system 179 ninja with the specified number of jobs (i.e. 4). Among the reasons why 180 you might want to do this are: building on a subset of CPUs, either to 181 measure the build time for that number of processors or to run other 182 CPU-intensive tasks on other cores, or to improve the build speed on a 183 less-well endowed 4-core machine. On a machine with a powerful CPU and 184 plenty of RAM, running N+2 jobs (the ninja default for 4+ cores) for the 185 large working sets of the C++ compiles in this package is typically only 186 marginally slower than running 4 jobs at a time. But for a machine with 187 less memory it might be much slower. 182 188 </para> 183 189
Note:
See TracChangeset
for help on using the changeset viewer.