#14729: qtwebengine after 5.15.2
-------------------------+-----------------------
 Reporter:  ken@…        |       Owner:  ken@…
     Type:  enhancement  |      Status:  assigned
 Priority:  high         |   Milestone:  10.2
Component:  BOOK         |     Version:  SVN
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+-----------------------

Comment (by ken@…):

 I've got a bit further (managed to build it and do an INSTALL_ROOT install
 on BLFS-10.0, which highlighted a few things and worked around possible
 remaining glibc-2.33 issues.

 Although the qtwebengine 5.15.3 branch is visible online, using that gave
 me many differences from what gentoo were using. Twice very near the end
 of the build I had failures. For the first one I found that gentoo had
 reverted a patch from chromium. For the second I looked at git blame and
 found that the FTBFS was related to a merge of 5.15.3 into -dev (which is
 the ongoing development). There is also a 5.15 branch, using that changed
 the module version from 6.0+ to 5.15.3. Of course, in the absence of
 Qt-5.15.3 we need to build for 5.15.2.

 This does not need the revert from chromium.

 I'm currently calling this qtwebengine-5.15branch_20210303 to indicate
 where this came from.

 From an existing qtwebengine git pull I've done:
 {{{
 git submodule update --init
 git pull --recurse-submodules
 git fetch origin
 git branch -r # to show remote branches
 git checkout -b 5.15 origin/5.15

 git-archive ignores submodules, so tarring this up is
 a multi-stage process:

 git archive --prefix qtwebengine-5.15branch_20210303/ \
  -o /path/to/qtwebengine-only.tar

 then go down to src/thirdparty. There are three modules:
 chromium, gn, ninja. Go into each in turn and create an
 archive (prefix chromium/ etc).

 In somewhere with plenty of space (the chromium submodule
 is somewhat large, it is also different from upstream chromium,
 with backports and a qtwebengine directory in it) untar the
 qtwebengine tarball, then cd into that and go down to
 src/submodules. Untar each submodule.

 The completed source can now be tarred up with tar -cJf, it
 takes some time and includes files such as .gitignore but not
 any git history.
 }}}

--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/14729#comment:5>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to