NEW231367
[WPE] Fails to build if not already installed 
https://bugs.webkit.org/show_bug.cgi?id=231367
Summary [WPE] Fails to build if not already installed
Michael Catanzaro
Reported 2021-10-07 09:41:37 PDT
If WPE WebKit is not already installed, it fails to build trying to configure cog during the build process. So WPE port currently depends on an existing WPE install to bootstrap itself. Oops? [1878/2019] Performing configure step for 'cog' FAILED: Tools/cog-prefix/src/cog-stamp/cog-configure /home/mcatanzaro/Projects/WebKit/WebKitBuild/WPE/Tools/cog-prefix/src/cog-stamp/cog-configure cd /home/mcatanzaro/Projects/WebKit/WebKitBuild/WPE/Tools/cog-prefix/src/cog-build && /usr/bin/cmake -DCOG_PLATFORM_GTK4=ON -DCOG_PLATFORM_HEADLESS=ON -DCOG_PLATFORM_X11=ON -DUSE_SOUP2=OFF -GNinja /home/mcatanzaro/Projects/WebKit/Tools/wpe/cog && /usr/bin/cmake -E touch /home/mcatanzaro/Projects/WebKit/WebKitBuild/WPE/Tools/cog-prefix/src/cog-stamp/cog-configure -- The C compiler identification is GNU 11.2.1 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Found Git: /usr/bin/git (found version "2.32.0") -- Source tree revision: 0.9.1+git-6dea32b -- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.0") -- Checking for module 'gio-2.0>=2.67.4' -- Found gio-2.0, version 2.70.0 -- Checking for module 'libsoup-3.0>=2.99.7' -- Found libsoup-3.0, version 3.0.1 -- Checking for module 'wpe-webkit-1.1>=2.33.1' -- Package 'wpe-webkit-1.1', required by 'virtual:world', not found CMake Error at /usr/share/cmake/Modules/FindPkgConfig.cmake:562 (message): A required package was not found Call Stack (most recent call first): /usr/share/cmake/Modules/FindPkgConfig.cmake:784 (_pkg_check_modules_internal) CMakeLists.txt:142 (pkg_check_modules) -- Configuring incomplete, errors occurred!
Attachments
Add attachment proposed patch, testcase, etc.
Michael Catanzaro
Comment 1 2021-10-07 09:48:15 PDT
Maybe it's OK because it depends on -DENABLE_DEVELOPER_MODE=ON and can be worked around pretty easily by building with -DENABLE_COG=OFF. So feel free to close this if this is intended. That said, I was surprised.
Note You need to log in before you can comment on or make changes to this bug.