Changes in x/lib/qtwebengine.xml [86e62cc:3f2db3a6]
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
x/lib/qtwebengine.xml
r86e62cc r3f2db3a6 11 11 <!ENTITY qtwebengine-download-http "&sources-anduin-http;/qtwebengine/qtwebengine-&qtwebengine-version;.tar.xz"> 12 12 <!ENTITY qtwebengine-download-ftp " "> 13 <!ENTITY qtwebengine-md5sum " af799617842cca0b765102c312fbdd46">13 <!ENTITY qtwebengine-md5sum "1302667c7e8a045fb0cc776f7e3627ad"> 14 14 <!ENTITY qtwebengine-size "306 MB"> 15 <!ENTITY qtwebengine-buildsize "5. 0 GB (154MB installed)">16 <!ENTITY qtwebengine-time "10 7SBU (typical, Using parallelism=4)">15 <!ENTITY qtwebengine-buildsize "5.1 GB (152 MB installed)"> 16 <!ENTITY qtwebengine-time "103 SBU (typical, Using parallelism=4)"> 17 17 ]> 18 18 … … 20 20 <?dbhtml filename="qtwebengine.html"?> 21 21 22 <sect1info>23 <date>$Date$</date>24 </sect1info>25 22 26 23 <title>QtWebEngine-&qtwebengine-version;</title> … … 78 75 79 76 <para> <!-- for git versions --> 80 The tarball linked to below was created from the 5.15 .6git branch77 The tarball linked to below was created from the 5.15 git branch 81 78 and the 87-branch of the chromium submodule (which is forked from 82 chromium). See the GIT-VERSIONS file in the tarball (after applying83 any patches) for details of thelatest commits.79 chromium). See the GIT-VERSIONS file in the tarball for details of the 80 latest commits. 84 81 </para> 85 82 </warning> … … 106 103 git checkout origin/87-branch (or whatever) 107 104 Use git log or git tk to look at its HEAD and check it seems appropriate. 105 If this doesn't work, use 'git submodule update' 108 106 109 107 To decide when it might be worth creating a new tarball, periodically keep … … 139 137 Decide on what to call the result and create a full xz tarball using tar -cJf. 140 138 139 NOTE: To use git archive, use something like this: 140 git archive - -format tar.gz - -output qtwebengine.tar.gz HEAD 141 git archive - -format tar.gz - -output chromium.tar.gz HEAD 142 141 143 UPDATE: Since we have to host the tarball, and it is over 300MB, it makes 142 144 sense to create a patch for subsequent fixes (for the first version, 314KB … … 151 153 end of note for editors --> 152 154 153 &lfs11 0a_checked;155 &lfs112_checked; 154 156 155 157 <warning> … … 170 172 171 173 <note> 174 <para> 175 If you are upgrading and have installed a newer version of <xref 176 linkend='icu'/> since you last installed <xref linkend='qt5'/>, you 177 will need to reinstall Qt5 before upgrading, otherwise the final link 178 of this package will fail with a warning that the version of icu 179 libraries needed by libQt5Core.so may conflict with the version 180 used for this package. 181 </para> 182 172 183 <para> 173 184 Unusually, the shipped GN build system (used to create the Ninja files) … … 218 229 <bridgehead renderas="sect3">Additional Downloads</bridgehead> 219 230 <itemizedlist spacing="compact"> 231 <!--<listitem> 232 <para> 233 Required patch: 234 <!\-\- keep links for releases and git versions as a reminder 235 that the tarball names names differ 236 <ulink url="&patch-root;/qtwebengine-everywhere-src-&qtwebengine-version;-ICU68-2.patch"/> \-\-> 237 238 <ulink url="&patch-root;/qtwebengine-&qtwebengine-version;-5.15.7-1.patch"/> 239 </para> 240 </listitem>--> 220 241 <listitem> 221 242 <para> 222 243 Required patch: 223 <!-- keep links for releases and git versions as a reminder 224 that the tarball names names differ 225 <ulink url="&patch-root;/qtwebengine-everywhere-src-&qtwebengine-version;-ICU68-2.patch"/> --> 226 227 <ulink url="&patch-root;/qtwebengine-&qtwebengine-version;-5.15.7-1.patch"/> 244 <ulink url="&patch-root;/qtwebengine-&qtwebengine-version;-build_fixes-1.patch"/> 228 245 </para> 229 246 </listitem> 230 247 <listitem> 231 248 <para> 232 Required patch:--> 233 <!-- <ulink url="&patch-root;/qtwebengine-&qtwebengine-version;-build_fixes-1.patch"/> --> 234 <ulink url="&patch-root;/qtwebengine-5.15.7-build_fixes-1.patch"/> 249 Required patch: 250 <ulink url="&patch-root;/qtwebengine-&qtwebengine-version;-ffmpeg5_fixes-1.patch"/> 235 251 </para> 236 252 </listitem> … … 244 260 <xref linkend="nodejs"/>, 245 261 <xref linkend="nss"/>, 246 <xref linkend="python2"/>, and 262 <xref linkend="pciutils"/>, and 263 <!-- <xref linkend="python2"/>, and --> 247 264 <xref linkend='qt5'/> 248 265 </para> … … 272 289 <para role="optional"> 273 290 <xref linkend="libevent"/>, 291 <xref linkend="mitkrb"/>, 274 292 <xref linkend="pipewire"/>, 275 293 <xref linkend="poppler"/>, 276 294 <ulink url="https://github.com/open-source-parsers/jsoncpp/releases">jsoncpp</ulink>, 277 295 <ulink url="https://github.com/cisco/libsrtp/releases">libsrtp</ulink>, 278 <ulink url="http ://google.github.io/snappy/">snappy</ulink>296 <ulink url="https://google.github.io/snappy/">snappy</ulink> 279 297 </para> 280 298 … … 287 305 <title>Installation of qtwebengine</title> 288 306 289 <note> 307 <!-- following merely commented instead of deleted, in case we need to 308 drop back when a future version of python3 is released --> 309 <!--<note> 290 310 <para> 291 311 Unlike version 5.15.2, the chromium-derived build system now needs … … 305 325 </para> 306 326 307 <screen role="root"><userinput>ln -svf /usr/bin/python{2,}</userinput></screen> 308 309 310 327 <screen role="root"><userinput>ln -svf /usr/bin/python{2,}</userinput></screen>--> 328 329 330 <!--<para> 311 331 Now apply a patch to update from 5.15.6 to the security and other fixes 312 332 contained in the 5.15.7 source: 313 333 </para> 314 334 315 <screen><userinput remap="pre">patch -Np1 -i ../qtwebengine-&qtwebengine-version;-5.15.7-1.patch</userinput></screen> 316 317 <para> 318 Apply apply a patch to fix several issues that can prevent the build working: 319 </para> 320 321 <screen><userinput remap="pre">patch -Np1 -i ../qtwebengine-5.15.7-build_fixes-1.patch</userinput></screen> 335 <screen><userinput remap="pre">patch -Np1 -i ../qtwebengine-&qtwebengine-version;-5.15.7-1.patch</userinput></screen>--> 336 337 <para> 338 Apply a patch to fix several issues that can prevent the build from completing, 339 and to force it to use python3: 340 </para> 341 342 <screen><userinput remap="pre">patch -Np1 -i ../qtwebengine-&qtwebengine-version;-build_fixes-1.patch</userinput></screen> 343 344 <para> 345 Apply a patch that resolves problems when building with ffmpeg-5: 346 </para> 347 348 <screen><userinput remap="pre">patch -Np1 -i ../qtwebengine-&qtwebengine-version;-ffmpeg5_fixes-1.patch</userinput></screen> 322 349 323 350 <!-- start of commands for git versions only --> … … 359 386 360 387 <para> 388 Next, fix the build tools so they can be run with Python-3.11+: 389 </para> 390 391 <screen><userinput>sed -e 's/\^(?i)/(?i)^/' \ 392 -i src/3rdparty/chromium/tools/metrics/ukm/ukm_model.py && 393 sed -e "s/'rU'/'r'/" \ 394 -i src/3rdparty/chromium/tools/grit/grit/util.py</userinput></screen> 395 396 <para> 361 397 Finally, fix a change in the build system which allows its developers to 362 398 pass e.g. -j20 to make (for quick tests of some areas) but breaks the … … 383 419 fi</userinput></screen>--> 384 420 421 <!--<para> 422 The last fix is needed to build with gcc-12: 423 </para> 424 425 <screen><userinput>sed -e '/#include/i#include <vector>' \ 426 -i src/3rdparty/chromium/third_party/skia/src/utils/SkParseColor.cpp</userinput></screen>--> 427 385 428 <para> 386 429 Install <application>qtwebengine</application> by running the following … … 428 471 -exec sed -i -e '/^QMAKE_PRL_BUILD_DIR/d' {} \;</userinput></screen> 429 472 430 473 <!--<para> 431 474 Finally, as the <systemitem class="username">root</systemitem> 432 475 user, remove the python symlink: 433 476 </para> 434 477 435 <screen role="root"><userinput>rm -v /usr/bin/python</userinput></screen> 478 <screen role="root"><userinput>rm -v /usr/bin/python</userinput></screen>--> 436 479 </sect2> 437 480 … … 464 507 </para> 465 508 509 <para> 510 <option>-webengine-kerberos</option>: Add this if you have installed <xref 511 linkend="mitkrb"/> and wish to connect from a browser using QtWebEngine 512 to a webserver which requires you to connect via kerberos. 513 </para> 514 466 515 <!-- 467 516 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" … … 484 533 with a lot of CPUs, trying to measure the build time for a 4-CPU 485 534 machine, <option>NINJAJOBS=4 make</option> will give a reasonable 486 approximation (there is a short period where N+2 python 2and node535 approximation (there is a short period where N+2 python and node 487 536 jobs run). 488 537 </para>
Note:
See TracChangeset
for help on using the changeset viewer.