Issue metadata
Sign in to add a comment
|
fontconfig dependency not correctly picked up
Reported by
stefan.s...@gmail.com,
Jul 12 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0 Steps to reproduce the problem: 1. Compile Qt 5.9 (QtWebengine uses an bundled Chromium 56) 2. Fontconfig is not available in the standard folders (e.g., /usr/, /usr/local), but Chromium should use the bundled fontconfig anyways. What is the expected behavior? Compilation succeeds. What went wrong? Compilation fails, becauce fontconfig.h cannot be found. It can be fixed by manually adding "//third_party/fontconfig" to the deps list in content/browser/BUILD.gn and ui/gfx/BUILD.gn (see attached patch). There are also if-Blocks in both files which add fontconfig to deps, but their condition doesn't not evaluate to True when necessary, as it seems. Did this work before? Yes It worked in Qt 5.8 which bundled and older Chromium version Chrome version: 56, master Channel: n/a OS Version: Flash Version: I also opened an issue on the qt tracker: https://bugreports.qt.io/browse/QTBUG-61158
,
Nov 10 2017
,
Jan 8 2018
The issue still exists in Qt5 5.10. However, the patch (with some adjustments) that I provided no longer seems to help.
However, when I installed "fontconfig-devel" inside the container, the build succeeds. But(!), I explicitly do not want to link against the system fontconfig but against the fontconfig in my Conda environment. I configured Qt5 this way:
./configure -prefix $PREFIX \
-bindir $PREFIX/lib/qt5/bin \
-headerdir $PREFIX/include/qt5 \
-archdatadir $PREFIX/lib/qt5 \
-datadir $PREFIX/share/qt5 \
-opensource \
-confirm-license \
-release \
-shared \
-silent \
-I $PREFIX/include \
-I $PREFIX/include/mariadb \
-L $PREFIX/lib \
-nomake examples \
-nomake tests \
-qt-pcre \
-qt-xcb \
-qt-xkbcommon \
-qt-libjpeg \
-proprietary-codecs \
-dbus
But the bundled Chromium does not seem to look inside $PREFIX (and it actually should use the fontconfig bundle with itself).
,
Jan 9
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by jbanavatu@chromium.org
, Jul 13 2017