ladybird/Documentation/Troubleshooting.md
Timothy Flynn 5681dbee64 Meta: Move the vcpkg installation/cache directories under Build
In addition to changing the build-type dependent build directories, we
can take this opportunity to move the vcpkg cache directory to the Build
folder itself. This probably isn't 100% needed, but it ensures that no
leftover artifacts are used from non-dynamic vcpkg builds, and it's also
generally nice to have all build artifacts under Build.
2024-11-06 10:38:57 -07:00

1.8 KiB
Raw Blame History

Troubleshooting

In case of an error, you might find an answer of how to deal it here.

Building Ladybird

CMake fails to configure the build because it's outdated

Ensure your CMake version is >= 3.25 with cmake --version. If your system doesn't provide a suitable version of CMake, you can download a binary release from the CMake website.

GCC is missing or is outdated

Ensure your gcc version is >= 13 with gcc --version. Otherwise, install it. If your gcc binary is not called gcc you have to specify the names of your C and C++ compiler when you run cmake, e.g. cmake ../.. -GNinja -DCMAKE_C_COMPILER=gcc-13 -DCMAKE_CXX_COMPILER=g++-13.

Legacy renegotiation is disabled

Ensure your /etc/ssl/openssl.cnf file has the following options:

[openssl_init]
ssl_conf = ssl_sect

[ssl_sect]
system_default = system_default_sect

[system_default_sect]
MinProtocol = TLSv1.2
CipherString = DEFAULT@SECLEVEL=1
Options = UnsafeLegacyRenegotiation

When building with the Qt chrome on macOS, you may encounter the following message:

CMake Warning at /opt/homebrew/Cellar/qt/6.7.0_1/lib/cmake/Qt6/FindWrapOpenGL.cmake:48 (target_link_libraries): Target "ladybird" requests linking to directory "/usr/X11R6/lib". Targets may link only to libraries. CMake is dropping the item.

…followed by 14-line stack trace, the top of which is this:

Build/vcpkg/scripts/buildsystems/vcpkg.cmake:859 (_find_package)

…and all of it shown in bright yellow, making you think it must be important and something must need to be fixed. But thats not the case. Instead, despite that, youll be able to build successfully with the Qt chrome.