dmaax/ladybird
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ladybird/vcpkg.json

341 lines
5.6 KiB
JSON
Raw Normal View History

Meta+LibWebView: Install and link sqlite3 with vcpkg We will use sqlite3 as a replacement for LibSQL. Using a tried-and-true database will allow us to avoid maintaining our an incomplete, non-ACID, and less performant implementation. It also means we do not have to launch and manage the singleton SQLServer process.
2024-06-04 17:28:35 -03:00
{
Meta+LibJS: Upgrade simdjson to the latest version 5e0ee26e8bef854553dfe3a6cdf3ce508a926acd pulls in an old version of simdjson, this commit upgrades to the latest release. This commit also pins `dav1d` to the version it was before this change.
2026-01-15 21:48:48 -03:00
"builtin-baseline": "2fa7118fb2ce0c27ab73e08ab1991f4cb67af880",
Meta+LibWebView: Install and link sqlite3 with vcpkg We will use sqlite3 as a replacement for LibSQL. Using a tried-and-true database will allow us to avoid maintaining our an incomplete, non-ACID, and less performant implementation. It also means we do not have to launch and manage the singleton SQLServer process.
2024-06-04 17:28:35 -03:00
"dependencies": [
LibWeb: Add ANGLE ANGLE is going to be used for WebGL implementation in upcoming changes.
2024-11-29 15:26:57 -03:00
{
"name": "angle",
Meta: Enable metal feature for angle
2024-12-20 21:47:26 -03:00
"platform": "osx",
"features": [
Meta: Update vcpkg baseline
2025-06-29 18:44:17 -03:00
"metal"
Meta: Enable metal feature for angle
2024-12-20 21:47:26 -03:00
]
LibWeb: Add ANGLE ANGLE is going to be used for WebGL implementation in upcoming changes.
2024-11-29 15:26:57 -03:00
},
Meta: Patch angle vcpkg to build on Linux This involves removing x11 dependencies, and not setting angle_use_x11.
2025-06-24 20:18:25 -03:00
{
"name": "angle",
Meta: Build angle on all BSD systems
2026-01-15 14:11:56 -03:00
"platform": "linux | windows | android | bsd"
Meta: Patch angle vcpkg to build on Linux This involves removing x11 dependencies, and not setting angle_use_x11.
2025-06-24 20:18:25 -03:00
},
AK: Clean up backtraces This commit replaces the default backtrace logic with cpptrace, for nicer, colored backtraces. Cpptrace runs on all of our supported platforms excpet android. As such backtrace.h is left in place. All the backtrace functions are made noinline to have a consistent number of frames. A maximum depth parameter is added to dump_backtrace with a default of 100. This should be enough, and can be easily changed, and allows for limiting the maximum depth. Setting the LADYBIRD_BACKTRACE_SNIPPETS environment variable enables surrouding code snippets in the backtrace. Specifically 2 lines above and below. This number can be changed by calling snippet_context on the formatter. For the whole list of options of what can be done with formatting see the cpptrace repository. On Windows we skipped frames when verification fails and when dump_backtrace was added the logic was wrong and would have skipped frames we care about. This commit also implements skipping frames on Linux. The only time where this does not skip all frames is when the call to backtrace gets intercepted. Then we will end up skipping one frame less than needed. To keep delayload on Windows a patch and overlay port is used. When upstream accepts these changes and vcpkg bumps the version the patch could be removed to have just the cmake define.
2025-06-26 13:29:30 -03:00
{
"name": "cpptrace",
Vcpkg: Disable cpptrace for freeBSD Cpptrace is not supported on freeBSD, so until that changes it will not be built from vcpkg.
2025-10-09 13:38:14 -03:00
"platform": "linux | windows | osx"
AK: Clean up backtraces This commit replaces the default backtrace logic with cpptrace, for nicer, colored backtraces. Cpptrace runs on all of our supported platforms excpet android. As such backtrace.h is left in place. All the backtrace functions are made noinline to have a consistent number of frames. A maximum depth parameter is added to dump_backtrace with a default of 100. This should be enough, and can be easily changed, and allows for limiting the maximum depth. Setting the LADYBIRD_BACKTRACE_SNIPPETS environment variable enables surrouding code snippets in the backtrace. Specifically 2 lines above and below. This number can be changed by calling snippet_context on the formatter. For the whole list of options of what can be done with formatting see the cpptrace repository. On Windows we skipped frames when verification fails and when dump_backtrace was added the logic was wrong and would have skipped frames we care about. This commit also implements skipping frames on Linux. The only time where this does not skip all frames is when the call to backtrace gets intercepted. Then we will end up skipping one frame less than needed. To keep delayload on Windows a patch and overlay port is used. When upstream accepts these changes and vcpkg bumps the version the patch could be removed to have just the cmake define.
2025-06-26 13:29:30 -03:00
},
RequestServer: Use libcurl for HTTP and HTTPS downloads This replaces the use of our home-grown implementations inherited from SerenityOS.
2024-09-05 08:20:09 -03:00
{
"name": "curl",
Meta+RequestServer: Enable HTTP/3 for curl This adds an overlay port for curl that adds the features required for HTTP/3. This is not quite compatible with the upstream vcpkg.json, because enabling HTTP/2 makes it use the default SSL backend, which is sectransp for macOS and schannel on Windows. These backends are not compatible with ngtcp2. Additionally, we can not build curl with multiple SSL backends when using ngtcp2. I couldn't find a way to selectively disable/enable dependencies based on what features are enabled, so I made HTTP/2 pick OpenSSL in our overlay port. Upstream vcpkg will likely want to support wolfSSL and GnuTLS backends for ngtcp2, so they'll be additional work to get this into upstream.
2025-07-07 12:03:37 -03:00
"default-features": false,
RequestServer: Use libcurl for HTTP and HTTPS downloads This replaces the use of our home-grown implementations inherited from SerenityOS.
2024-09-05 08:20:09 -03:00
"features": [
Meta: Update curl to version 8.10.1 Contains a fix for CVE-2024-8096.
2024-09-19 15:21:49 -03:00
"brotli",
Meta+RequestServer: Enable HTTP/3 for curl This adds an overlay port for curl that adds the features required for HTTP/3. This is not quite compatible with the upstream vcpkg.json, because enabling HTTP/2 makes it use the default SSL backend, which is sectransp for macOS and schannel on Windows. These backends are not compatible with ngtcp2. Additionally, we can not build curl with multiple SSL backends when using ngtcp2. I couldn't find a way to selectively disable/enable dependencies based on what features are enabled, so I made HTTP/2 pick OpenSSL in our overlay port. Upstream vcpkg will likely want to support wolfSSL and GnuTLS backends for ngtcp2, so they'll be additional work to get this into upstream.
2025-07-07 12:03:37 -03:00
"non-http",
LibWebSocket+RequestServer: Add a WebSocketImpl using libcurl This implementation can be better improved in the future by ripping out a lot of the manual logic in LibWebSocket and rely on libcurl to parse our message payloads. But for now, this uses the 'raw mode' of curl websockets in connect-only mode to allow for somewhat seamless integration into our event loop.
2025-02-20 08:18:37 -03:00
"http2",
Meta+RequestServer: Enable HTTP/3 for curl This adds an overlay port for curl that adds the features required for HTTP/3. This is not quite compatible with the upstream vcpkg.json, because enabling HTTP/2 makes it use the default SSL backend, which is sectransp for macOS and schannel on Windows. These backends are not compatible with ngtcp2. Additionally, we can not build curl with multiple SSL backends when using ngtcp2. I couldn't find a way to selectively disable/enable dependencies based on what features are enabled, so I made HTTP/2 pick OpenSSL in our overlay port. Upstream vcpkg will likely want to support wolfSSL and GnuTLS backends for ngtcp2, so they'll be additional work to get this into upstream.
2025-07-07 12:03:37 -03:00
"http3",
vcpkg: Explicitly use OpenSSL backend with curl The generic `ssl` feature selects Secure Transport on macOS, which is a deprecated library and support for it in curl is also deprecated and scheduled for removal after May 2025: https://daniel.haxx.se/blog/tag/securetransport/ Secure Transport is replaced by Network Framework, but as per the blog post above, there's no foreseeable future of curl supporting it. With this information, we now explicitly use OpenSSL as the backend for curl, inline with the default choice for Linux. This gives us some key benefits: - A maintained and current TLS library - TLS 1.0 and 1.1 is disabled by default - TLS 1.3 is now available - Modern cipher suites - Removal of TLS_EMPTY_RENEGOTIATION_INFO_SCSV extension - Opportunity to support HTTP/3 with nghttp3 and OpenSSL's QUIC support - More extensions, key exchanges, EC point formats, etc.
2025-02-28 13:22:57 -03:00
"openssl",
Meta: Enable the zstd feature for curl This content encoding is used by Facebook. For example: ``` > GET /rsrc.php/v5/yj/l/0,cross/VNfVTw9fSM1.css HTTP/3 Host: static.xx.fbcdn.net Accept-Encoding: deflate, gzip, br, zstd Alt-Used: (nil):0 User-Agent: Mozilla/5.0 (macOS; AArch64) Ladybird/1.0 Accept: text/css,*/*;q=0.1 Accept-Language: en Sec-Fetch-Dest: style Sec-Fetch-Mode: cors Origin: https://www.facebook.com Sec-Fetch-Site: cross-site Referer: https://www.facebook.com/ ``` The response (with some headers removed for brevity): ``` < HTTP/3 200 < content-encoding: zstd < content-type: text/css; charset=utf-8 < last-modified: Mon, 01 Jan 2001 08:00:00 GMT < expires: Fri, 10 Jul 2026 07:47:17 GMT < cache-control: public,max-age=31536000,immutable < content-length: 7448 < date: Fri, 11 Jul 2025 11:52:03 GMT < access-control-allow-origin: https://www.facebook.com * Added alt-svc: static.xx.fbcdn.net:443 over h3 < alt-svc: h3=":443"; ma=86400 < priority: u=3,i < ```
2025-07-11 08:54:04 -03:00
"websockets",
"zstd"
RequestServer: Use libcurl for HTTP and HTTPS downloads This replaces the use of our home-grown implementations inherited from SerenityOS.
2024-09-05 08:20:09 -03:00
]
},
Meta+WebContent+LibWeb: Add, link and initialize SDL3
2025-08-15 10:55:09 -03:00
{
"name": "dbus",
"default-features": false,
Meta: Build dbus on FreeBSD
2025-09-12 10:03:45 -03:00
"platform": "linux | freebsd"
Meta+WebContent+LibWeb: Add, link and initialize SDL3
2025-08-15 10:55:09 -03:00
},
LibCore: Port DirIterator to Windows using vcpkg dirent.h
2024-10-24 14:56:43 -03:00
{
"name": "dirent",
"platform": "windows"
},
AK+Everywhere: Replace custom number parsers with fast_float Our floating point number parser was based on the fast_float library: https://github.com/fastfloat/fast_float However, our implementation only supports 8-bit characters. To support UTF-16, we will need to be able to convert char16_t-based strings to numbers as well. This works out-of-the-box with fast_float. We can also use fast_float for integer parsing.
2025-06-26 20:06:46 -03:00
"fast-float",
Meta: Add ffmpeg to vcpkg dependencies Now that we are using shared libraries, it is possible to add into our vcpkg dependencies without worrying about LGPL
2024-11-07 16:47:48 -03:00
{
"name": "ffmpeg",
"features": [
"avcodec",
"avformat",
LibMedia: Implement audio conversion in AudioDataProvider
2025-12-10 22:22:05 -03:00
"swresample",
Meta: Add ffmpeg to vcpkg dependencies Now that we are using shared libraries, it is possible to add into our vcpkg dependencies without worrying about LGPL
2024-11-07 16:47:48 -03:00
"dav1d",
"openh264",
"opus",
"webp",
"theora",
"vorbis",
"vpx",
"zlib"
]
},
Ladybird: Use fontconfig to choose generic fonts on non-Apple systems If we get a suggestion from fontconfig, we try those fonts first, before falling back on the hard coded list of known suitable fonts for each generic family.
2024-06-07 14:50:00 -03:00
{
"name": "fontconfig",
Meta: Replace `freebsd | openbsd` in vcpkg.json with `bsd` This makes the file just a little bit cleaner and makes the work for supporting future BSD systems simpler.
2026-01-15 13:06:04 -03:00
"platform": "linux | bsd | osx"
LibLocale: Install ICU package and link into LibLocale Rather than removing LibLocale entirely, we will use it as a wrapper around ICU (which has some C-like interfaces, and uses UTF-16 for its string types). Using ICU will provide better web compatibility overall, and will let us implement features we were previously unable to (e.g. Intl.Collator requires data that is not in the JSON export of the CLDR).
2024-06-08 12:10:10 -03:00
},
Meta: Explicitly list required features for harfbuzz and skia
2024-11-07 16:46:15 -03:00
{
"name": "harfbuzz",
Meta: Replace `freebsd | openbsd` in vcpkg.json with `bsd` This makes the file just a little bit cleaner and makes the work for supporting future BSD systems simpler.
2026-01-15 13:06:04 -03:00
"platform": "linux | bsd | windows",
Meta: Explicitly list required features for harfbuzz and skia
2024-11-07 16:46:15 -03:00
"features": [
"freetype",
"icu"
]
},
{
"name": "harfbuzz",
"platform": "osx",
"features": [
"coretext",
"icu"
]
},
LibLocale: Install ICU package and link into LibLocale Rather than removing LibLocale entirely, we will use it as a wrapper around ICU (which has some C-like interfaces, and uses UTF-16 for its string types). Using ICU will provide better web compatibility overall, and will let us implement features we were previously unable to (e.g. Intl.Collator requires data that is not in the JSON export of the CLDR).
2024-06-08 12:10:10 -03:00
"icu",
LibGfx: Remove home-grown JPEG codec in favor of libjpeg-turbo
2024-06-16 11:08:31 -03:00
"libjpeg-turbo",
LibGfx: Use libjxl to decode JPEG XL images It currently doesn't support animated image. Note that Gfx::Bitmap has no support for get_pixel when the format is RGBA8888. This is why it has been removed from the tests.
2024-07-21 18:23:28 -03:00
"libjxl",
LibGfx: Remove home-grown PNG codec in favor of libpng+apng
2024-06-18 16:06:15 -03:00
{
"name": "libpng",
LibCore+LibWeb: Use Metal backend for Skia painter on macOS If Metal context and IOSurface are available, Skia painter will use Ganesh GPU backend on macOS, which is noticeably faster than the default CPU backend. Painting pipeline: 1. (WebContent) Allocate IOSurface for backing store 2. (WebContent) Allocate MTLTexture that wraps IOSurface 3. (WebContent) Paint into MTLTexture using Skia 4. (Browser) Wrap IOSurface into Gfx::Painter and use QPainter/CoreGraphics to blit backing store into viewport. Things we should improve in the future: 1. Upload textures for images in advance instead of doing that before every repaint. 2. Teach AppKit client to read directly from IOSurface instead of copying.
2024-06-26 12:56:55 -03:00
"features": [
"apng"
]
},
Meta: Don't compile libproxy for Android libproxy isn't availiable for Android.
2025-06-10 14:16:14 -03:00
{
"name": "libproxy",
Meta: Don't build libproxy on all BSD systems
2026-01-15 13:06:25 -03:00
"platform": "!(android | bsd)"
Meta: Don't compile libproxy for Android libproxy isn't availiable for Android.
2025-06-10 14:16:14 -03:00
},
LibGfx: Decode AVIF images Use libavif to decode AVIF images in LibGfx.
2024-07-06 04:33:38 -03:00
{
"name": "libavif",
"features": [
"dav1d"
]
},
LibCrypto: Add `libtommath` vcpkg dependency and link it An overlay port is required to add the `stdc-iec-559` and `install-pc` patches. The `stdc-iec-559` patch is required because Clang doesn't define `__STDC_IEC_559__`. However, glibc and musl define it if `__GCC_IEC_559` is not defined. The macro is taken from glibc source code. The `install-pc` patch is required because libtommath doesn't install the pkg-config files when building statically compromising our ability to find it during build. Clang: https://clang.llvm.org/c_status.html#:~:text=Yes-, IEC%2060559%20support,-Unknown glibc: https://sourceware.org/git/?p=glibc.git;a=blob; f=include/stdc-predef.h
2025-04-26 06:53:09 -03:00
"libtommath",
LibGfx: Decode WebP images with libwebp
2024-07-12 05:08:39 -03:00
{
"name": "libwebp",
"features": [
"anim",
"libwebpmux",
"simd"
]
},
LibCore/System: Add mmap, munmap for Windows
2024-11-20 10:39:13 -03:00
{
"name": "mman",
"platform": "windows"
},
LibWeb: Implement XPath functionality using libxml2
2025-09-29 17:09:51 -03:00
"libxml2",
LibCrypto: Link with OpenSSL Add OpenSSL with vcpkg and link with LibCrypto using CMake. Also added a placeholder GN setup.
2024-12-20 05:06:14 -03:00
"openssl",
Meta: Build QT with vcpkg on FreeBSD This is a workaround for the fact that on FreeBSD the system icu has symbol renaming disabled which causes our build to clash with the expectations of the system QT.
2025-06-29 18:46:51 -03:00
{
"name": "qtbase",
"platform": "freebsd",
"default-features": false,
"features": [
Meta: Add the dbus feature to qtbase D-Bus is needed for Qt to build its accessibility support and since we build D-Bus regardless it doesn't add any overhead.
2025-09-12 10:04:21 -03:00
"dbus",
Meta: Build QT with vcpkg on FreeBSD This is a workaround for the fact that on FreeBSD the system icu has symbol renaming disabled which causes our build to clash with the expectations of the system QT.
2025-06-29 18:46:51 -03:00
"doubleconversion",
"fontconfig",
"freetype",
"gui",
"icu",
"jpeg",
"network",
"opengl",
"pcre2",
"png",
"thread",
"vulkan",
"widgets",
"xcb",
"xcb-xlib",
"xlib",
"xrender",
"zstd"
]
},
Meta: Install qtbase and qtmultimedia vcpkg ports on Windows
2025-08-10 15:19:29 -03:00
{
"name": "qtbase",
"platform": "windows",
"default-features": false,
"features": [
"doubleconversion",
"freetype",
"gui",
"icu",
"jpeg",
"network",
"opengl",
"pcre2",
"png",
"thread",
"vulkan",
"widgets",
"zstd"
]
},
LibCore: Fix pthread-related errors on Windows Fixes compilation error in Notifier.h and link errors in ThreadEventQueue.cpp
2024-11-16 04:44:30 -03:00
{
"name": "pthread",
"platform": "windows"
},
Meta+WebContent+LibWeb: Add, link and initialize SDL3
2025-08-15 10:55:09 -03:00
{
"name": "sdl3",
"default-features": false
},
LibJS: Use simdjson for JSON.parse Replace the custom AK JSON parser with simdjson for parsing JSON in LibJS. This eliminates the intermediate AK::JsonValue object graph, going directly from JSON text to JS::Value. simdjson's on-demand API parses at ~4GB/s and only materializes values as they are accessed, making this both faster and more memory efficient than the previous approach. The AK JSON parser is still used elsewhere (WebDriver protocol, config files, etc.) but LibJS now uses simdjson exclusively for JSON.parse() and JSON.rawJSON().
2026-01-11 17:09:41 -03:00
"simdjson",
AK+LibWeb: Replace our home-grown base64 encoder/decoders with simdutf We currently have 2 base64 coders: one in AK, another in LibWeb for a "forgiving" implementation. ECMA-262 has an upcoming proposal which will require a third implementation. Instead, let's use the base64 implementation that is used by Node.js and recommended by the upcoming proposal. It handles forgiving decoding as well. Our users of AK's implementation should be fine with the forgiving implementation. The AK impl originally had naive forgiving behavior, but that was removed solely for performance reasons. Using http://mattmahoney.net/dc/enwik8.zip (100MB unzipped) as a test, performance of our old home-grown implementations vs. the simdutf implementation (on Linux x64): Encode Decode AK base64 0.226s 0.169s LibWeb base64 N/A 1.244s simdutf 0.161s 0.047s
2024-07-15 16:25:08 -03:00
"simdutf",
LibCore+LibWeb: Use Metal backend for Skia painter on macOS If Metal context and IOSurface are available, Skia painter will use Ganesh GPU backend on macOS, which is noticeably faster than the default CPU backend. Painting pipeline: 1. (WebContent) Allocate IOSurface for backing store 2. (WebContent) Allocate MTLTexture that wraps IOSurface 3. (WebContent) Paint into MTLTexture using Skia 4. (Browser) Wrap IOSurface into Gfx::Painter and use QPainter/CoreGraphics to blit backing store into viewport. Things we should improve in the future: 1. Upload textures for images in advance instead of doing that before every repaint. 2. Teach AppKit client to read directly from IOSurface instead of copying.
2024-06-26 12:56:55 -03:00
{
"name": "skia",
"platform": "osx",
Meta+LibGfx+LibWeb: Update skia to 144 and remove overlay port Skia deprecated some non-span versions of their API, but they provided SK_SUPPORT_UNSPANNED_APIS to expose the legacy versions. SkFontMgr_New_FontConfig now requires a font scanner to be passed in. There were a few screenshot tests that visibily looked the same but skia must've changed some rendering infrastructure as the PNGs were not matching anymore so I rebaselined those and adjusted the fuzzy matching config to allow them to pass on both macOS and Linux. The empty-radial-gradient-crash Ref test started to fail as we were setting the horizontal scale factor to inf in when the height = 0. It looks like something changed to make doing that not valid anymore. The overlay port is removed as the issues, mainly skcms symbol import and export were resolved upstream in skia and utilized in the new port version.
2025-09-02 06:27:04 -03:00
"default-features": false,
LibCore+LibWeb: Use Metal backend for Skia painter on macOS If Metal context and IOSurface are available, Skia painter will use Ganesh GPU backend on macOS, which is noticeably faster than the default CPU backend. Painting pipeline: 1. (WebContent) Allocate IOSurface for backing store 2. (WebContent) Allocate MTLTexture that wraps IOSurface 3. (WebContent) Paint into MTLTexture using Skia 4. (Browser) Wrap IOSurface into Gfx::Painter and use QPainter/CoreGraphics to blit backing store into viewport. Things we should improve in the future: 1. Upload textures for images in advance instead of doing that before every repaint. 2. Teach AppKit client to read directly from IOSurface instead of copying.
2024-06-26 12:56:55 -03:00
"features": [
Ladybird+LibWeb+LibGfx: Add option to force use of fontconfig This allows us to get identical metrics on macOS and Linux. Without this, Skia will use CoreText on macOS and give us slightly different text metrics. That causes layout tests to be slightly different on different platforms, which is a huge headache. So let's not do that. You can now launch Ladybird and headless-browser with --force-fontconfig to load fonts through fontconfig. Tests run in this mode by default.
2024-08-19 15:35:49 -03:00
"metal",
Meta: Explicitly list required features for harfbuzz and skia
2024-11-07 16:46:15 -03:00
"fontconfig",
"harfbuzz",
"icu"
LibCore+LibWeb: Use Metal backend for Skia painter on macOS If Metal context and IOSurface are available, Skia painter will use Ganesh GPU backend on macOS, which is noticeably faster than the default CPU backend. Painting pipeline: 1. (WebContent) Allocate IOSurface for backing store 2. (WebContent) Allocate MTLTexture that wraps IOSurface 3. (WebContent) Paint into MTLTexture using Skia 4. (Browser) Wrap IOSurface into Gfx::Painter and use QPainter/CoreGraphics to blit backing store into viewport. Things we should improve in the future: 1. Upload textures for images in advance instead of doing that before every repaint. 2. Teach AppKit client to read directly from IOSurface instead of copying.
2024-06-26 12:56:55 -03:00
]
},
{
"name": "skia",
Meta+LibGfx: Remove fontconfig dependency on Windows Previously when launching a UI process and/or a WebContent process on Windows, the following message would be output to the console: Fontconfig error: Cannot load default config file: No such file: (null) Apparently on Windows, you have to provide a font .conf file to fontconfig explicitly. Since we are not doing that, the default fonts that are backed off to are not ideal. Similar to how we aren't using fontconfig on Android, Windows also has native font infrastructure in terms of both a collection of System installed fonts as well as skia support for font managers that use native Windows APIs. With that, we can remove the usage of fontconfig entirely and improve the fonts used on websites like ladybird.org or google.com.
2025-11-18 21:34:00 -03:00
"platform": "windows",
Meta+LibGfx+LibWeb: Update skia to 144 and remove overlay port Skia deprecated some non-span versions of their API, but they provided SK_SUPPORT_UNSPANNED_APIS to expose the legacy versions. SkFontMgr_New_FontConfig now requires a font scanner to be passed in. There were a few screenshot tests that visibily looked the same but skia must've changed some rendering infrastructure as the PNGs were not matching anymore so I rebaselined those and adjusted the fuzzy matching config to allow them to pass on both macOS and Linux. The empty-radial-gradient-crash Ref test started to fail as we were setting the horizontal scale factor to inf in when the height = 0. It looks like something changed to make doing that not valid anymore. The overlay port is removed as the issues, mainly skcms symbol import and export were resolved upstream in skia and utilized in the new port version.
2025-09-02 06:27:04 -03:00
"default-features": false,
Meta+LibGfx: Remove fontconfig dependency on Windows Previously when launching a UI process and/or a WebContent process on Windows, the following message would be output to the console: Fontconfig error: Cannot load default config file: No such file: (null) Apparently on Windows, you have to provide a font .conf file to fontconfig explicitly. Since we are not doing that, the default fonts that are backed off to are not ideal. Similar to how we aren't using fontconfig on Android, Windows also has native font infrastructure in terms of both a collection of System installed fonts as well as skia support for font managers that use native Windows APIs. With that, we can remove the usage of fontconfig entirely and improve the fonts used on websites like ladybird.org or google.com.
2025-11-18 21:34:00 -03:00
"features": [
"freetype",
"harfbuzz",
"icu",
"vulkan"
]
},
{
"name": "skia",
Meta: Replace `freebsd | openbsd` in vcpkg.json with `bsd` This makes the file just a little bit cleaner and makes the work for supporting future BSD systems simpler.
2026-01-15 13:06:04 -03:00
"platform": "linux | bsd",
Meta+LibGfx+LibWeb: Update skia to 144 and remove overlay port Skia deprecated some non-span versions of their API, but they provided SK_SUPPORT_UNSPANNED_APIS to expose the legacy versions. SkFontMgr_New_FontConfig now requires a font scanner to be passed in. There were a few screenshot tests that visibily looked the same but skia must've changed some rendering infrastructure as the PNGs were not matching anymore so I rebaselined those and adjusted the fuzzy matching config to allow them to pass on both macOS and Linux. The empty-radial-gradient-crash Ref test started to fail as we were setting the horizontal scale factor to inf in when the height = 0. It looks like something changed to make doing that not valid anymore. The overlay port is removed as the issues, mainly skcms symbol import and export were resolved upstream in skia and utilized in the new port version.
2025-09-02 06:27:04 -03:00
"default-features": false,
LibWeb+LibCore: Use Vulkan backend for Skia on Linux Skia now uses GPU-accelerated painting on Linux if Vulkan is available. Most of the performance gain is currently negated by reading the GPU backend back into RAM to pass it to the Browser process. In the future, this could be improved by sharing GPU-allocated memory across the Browser and WebContent processes.
2024-07-03 14:23:27 -03:00
"features": [
Meta: Explicitly list required features for harfbuzz and skia
2024-11-07 16:46:15 -03:00
"freetype",
"fontconfig",
"harfbuzz",
"icu",
LibWeb+LibCore: Use Vulkan backend for Skia on Linux Skia now uses GPU-accelerated painting on Linux if Vulkan is available. Most of the performance gain is currently negated by reading the GPU backend back into RAM to pass it to the Browser process. In the future, this could be improved by sharing GPU-allocated memory across the Browser and WebContent processes.
2024-07-03 14:23:27 -03:00
"vulkan"
]
LibGfx: Remove home-grown PNG codec in favor of libpng+apng
2024-06-18 16:06:15 -03:00
},
Android: Integrate vcpkg with Gradle build This ensures that vcpkg downloads and builds all dependencies for Android. We add it as a CMAKE_TOOLCHAIN_FILE that then chainloads the Android NDK's toolchain file, as per the vcpkg documentation.
2024-07-03 16:17:16 -03:00
{
"name": "skia",
Meta: Enable Vulkan and ANGLE when compiling for Android Vulkan seems to have been disabled due to not being able to compile. However, it compiles on my machine and it works on my phone. As for ANGLE, someone just forgot about Android.
2025-07-03 14:28:28 -03:00
"platform": "android",
Meta+LibGfx+LibWeb: Update skia to 144 and remove overlay port Skia deprecated some non-span versions of their API, but they provided SK_SUPPORT_UNSPANNED_APIS to expose the legacy versions. SkFontMgr_New_FontConfig now requires a font scanner to be passed in. There were a few screenshot tests that visibily looked the same but skia must've changed some rendering infrastructure as the PNGs were not matching anymore so I rebaselined those and adjusted the fuzzy matching config to allow them to pass on both macOS and Linux. The empty-radial-gradient-crash Ref test started to fail as we were setting the horizontal scale factor to inf in when the height = 0. It looks like something changed to make doing that not valid anymore. The overlay port is removed as the issues, mainly skcms symbol import and export were resolved upstream in skia and utilized in the new port version.
2025-09-02 06:27:04 -03:00
"default-features": false,
Meta: Enable Vulkan and ANGLE when compiling for Android Vulkan seems to have been disabled due to not being able to compile. However, it compiles on my machine and it works on my phone. As for ANGLE, someone just forgot about Android.
2025-07-03 14:28:28 -03:00
"features": [
"vulkan"
]
Android: Integrate vcpkg with Gradle build This ensures that vcpkg downloads and builds all dependencies for Android. We add it as a CMAKE_TOOLCHAIN_FILE that then chainloads the Android NDK's toolchain file, as per the vcpkg documentation.
2024-07-03 16:17:16 -03:00
},
LibLocale: Install ICU package and link into LibLocale Rather than removing LibLocale entirely, we will use it as a wrapper around ICU (which has some C-like interfaces, and uses UTF-16 for its string types). Using ICU will provide better web compatibility overall, and will let us implement features we were previously unable to (e.g. Intl.Collator requires data that is not in the JSON export of the CLDR).
2024-06-08 12:10:10 -03:00
"sqlite3",
Meta: Enable Vulkan and ANGLE when compiling for Android Vulkan seems to have been disabled due to not being able to compile. However, it compiles on my machine and it works on my phone. As for ANGLE, someone just forgot about Android.
2025-07-03 14:28:28 -03:00
"vulkan",
Meta: Explicitly enable zstd feature for tiff in vcpkg Without this, the library was pulling system libzstd implicitly.
2025-04-01 13:04:51 -03:00
{
"name": "tiff",
"features": [
"zstd"
]
Meta: Update vcpkg to latest master
2025-04-22 11:42:14 -03:00
},
Meta: Enable Vulkan and ANGLE when compiling for Android Vulkan seems to have been disabled due to not being able to compile. However, it compiles on my machine and it works on my phone. As for ANGLE, someone just forgot about Android.
2025-07-03 14:28:28 -03:00
"vulkan-headers",
Meta: Add explicit vcpkg dependency for zlib zlib is already included transitively for other dependencies, include it explicitly and link it with `LibCompress`.
2025-03-01 13:32:14 -03:00
"woff2",
"zlib"
Meta+LibWebView: Install and link sqlite3 with vcpkg We will use sqlite3 as a replacement for LibSQL. Using a tried-and-true database will allow us to avoid maintaining our an incomplete, non-ACID, and less performant implementation. It also means we do not have to launch and manage the singleton SQLServer process.
2024-06-04 17:28:35 -03:00
],
"overrides": [
LibWeb: Add ANGLE ANGLE is going to be used for WebGL implementation in upcoming changes.
2024-11-29 15:26:57 -03:00
{
"name": "angle",
Meta: Update ANGLE to chromium/7258
2025-06-24 10:02:25 -03:00
"version": "chromium_7258#0"
LibWeb: Add ANGLE ANGLE is going to be used for WebGL implementation in upcoming changes.
2024-11-29 15:26:57 -03:00
},
Meta: Bring Flatpak dependency versions in line with vcpkg versions
2025-12-15 19:08:04 -03:00
{
"name": "cpptrace",
"version": "1.0.2"
},
Meta: Update curl to version 8.10.1 Contains a fix for CVE-2024-8096.
2024-09-19 15:21:49 -03:00
{
"name": "curl",
Meta: Update curl to version 8.16.0
2025-09-23 17:48:19 -03:00
"version": "8.16.0#0"
Meta: Update curl to version 8.10.1 Contains a fix for CVE-2024-8096.
2024-09-19 15:21:49 -03:00
},
Meta+LibJS: Upgrade simdjson to the latest version 5e0ee26e8bef854553dfe3a6cdf3ce508a926acd pulls in an old version of simdjson, this commit upgrades to the latest release. This commit also pins `dav1d` to the version it was before this change.
2026-01-15 21:48:48 -03:00
{
"name": "dav1d",
"version": "1.5.1#0"
},
Meta+WebContent+LibWeb: Add, link and initialize SDL3
2025-08-15 10:55:09 -03:00
{
"name": "dbus",
Meta: Update dbus to version 1.16.2#2
2025-09-23 17:48:20 -03:00
"version": "1.16.2#2"
Meta+WebContent+LibWeb: Add, link and initialize SDL3
2025-08-15 10:55:09 -03:00
},
Meta: Pin recently added vcpkg dependencies
2024-12-23 14:51:16 -03:00
{
"name": "dirent",
Meta: Update dirent to version 1.26.0
2025-09-23 17:48:21 -03:00
"version": "1.26#0"
Meta: Pin recently added vcpkg dependencies
2024-12-23 14:51:16 -03:00
},
AK+Everywhere: Replace custom number parsers with fast_float Our floating point number parser was based on the fast_float library: https://github.com/fastfloat/fast_float However, our implementation only supports 8-bit characters. To support UTF-16, we will need to be able to convert char16_t-based strings to numbers as well. This works out-of-the-box with fast_float. We can also use fast_float for integer parsing.
2025-06-26 20:06:46 -03:00
{
"name": "fast-float",
Meta+Tests: Update fast-float to version 8.1.0 This release comes with a fix for a bug where certain unicode emoji characters encoded in UTF-16 were mistakenly parsed as integers. This manifested in keys of an JS object being coerced into integers, i.e. `{ "⤵️": 42 }` would become `{ "5": 42 }`. Relevant upstream PR: https://github.com/fastfloat/fast_float/pull/325
2025-09-23 17:48:22 -03:00
"version": "8.1.0#0"
AK+Everywhere: Replace custom number parsers with fast_float Our floating point number parser was based on the fast_float library: https://github.com/fastfloat/fast_float However, our implementation only supports 8-bit characters. To support UTF-16, we will need to be able to convert char16_t-based strings to numbers as well. This works out-of-the-box with fast_float. We can also use fast_float for integer parsing.
2025-06-26 20:06:46 -03:00
},
Meta: Add ffmpeg to vcpkg dependencies Now that we are using shared libraries, it is possible to add into our vcpkg dependencies without worrying about LGPL
2024-11-07 16:47:48 -03:00
{
"name": "ffmpeg",
Meta: Update ffmpeg to version 7.1.1#5
2025-09-23 17:48:22 -03:00
"version": "7.1.1#5"
Meta: Add ffmpeg to vcpkg dependencies Now that we are using shared libraries, it is possible to add into our vcpkg dependencies without worrying about LGPL
2024-11-07 16:47:48 -03:00
},
LibLocale: Install ICU package and link into LibLocale Rather than removing LibLocale entirely, we will use it as a wrapper around ICU (which has some C-like interfaces, and uses UTF-16 for its string types). Using ICU will provide better web compatibility overall, and will let us implement features we were previously unable to (e.g. Intl.Collator requires data that is not in the JSON export of the CLDR).
2024-06-08 12:10:10 -03:00
{
"name": "fontconfig",
Meta: Update fontconfig to version 2.15.0
2025-05-23 09:05:38 -03:00
"version": "2.15.0#4"
LibLocale: Install ICU package and link into LibLocale Rather than removing LibLocale entirely, we will use it as a wrapper around ICU (which has some C-like interfaces, and uses UTF-16 for its string types). Using ICU will provide better web compatibility overall, and will let us implement features we were previously unable to (e.g. Intl.Collator requires data that is not in the JSON export of the CLDR).
2024-06-08 12:10:10 -03:00
},
Meta: Pin harfbuzz to 10.2.0 for now Several of us (including our WPT runner) are getting linker errors with 11.2.0, as Qt is pulling in the system harfbuzz.
2025-07-02 11:22:25 -03:00
{
"name": "harfbuzz",
"version": "10.2.0#0"
},
LibLocale: Install ICU package and link into LibLocale Rather than removing LibLocale entirely, we will use it as a wrapper around ICU (which has some C-like interfaces, and uses UTF-16 for its string types). Using ICU will provide better web compatibility overall, and will let us implement features we were previously unable to (e.g. Intl.Collator requires data that is not in the JSON export of the CLDR).
2024-06-08 12:10:10 -03:00
{
"name": "icu",
Meta: Update icu to 78.1#1
2026-01-09 12:45:43 -03:00
"version": "78.1#1"
LibLocale: Install ICU package and link into LibLocale Rather than removing LibLocale entirely, we will use it as a wrapper around ICU (which has some C-like interfaces, and uses UTF-16 for its string types). Using ICU will provide better web compatibility overall, and will let us implement features we were previously unable to (e.g. Intl.Collator requires data that is not in the JSON export of the CLDR).
2024-06-08 12:10:10 -03:00
},
LibGfx: Remove home-grown JPEG codec in favor of libjpeg-turbo
2024-06-16 11:08:31 -03:00
{
"name": "libjpeg-turbo",
Meta: Update libjpeg-turbo to version 3.1.1
2025-08-27 07:33:46 -03:00
"version": "3.1.1#0"
LibGfx: Remove home-grown JPEG codec in favor of libjpeg-turbo
2024-06-16 11:08:31 -03:00
},
LibGfx: Use libjxl to decode JPEG XL images It currently doesn't support animated image. Note that Gfx::Bitmap has no support for get_pixel when the format is RGBA8888. This is why it has been removed from the tests.
2024-07-21 18:23:28 -03:00
{
"name": "libjxl",
Meta: Update vcpkg for patched libjxl port and remove our overlay port
2025-06-27 20:31:10 -03:00
"version": "0.11.1#3"
LibGfx: Use libjxl to decode JPEG XL images It currently doesn't support animated image. Note that Gfx::Bitmap has no support for get_pixel when the format is RGBA8888. This is why it has been removed from the tests.
2024-07-21 18:23:28 -03:00
},
LibGfx: Remove home-grown PNG codec in favor of libpng+apng
2024-06-18 16:06:15 -03:00
{
"name": "libpng",
Meta: Update libpng to version 1.6.50
2025-08-27 07:34:26 -03:00
"version": "1.6.50#0"
LibGfx: Remove home-grown PNG codec in favor of libpng+apng
2024-06-18 16:06:15 -03:00
},
Build: Fix libpxbackend dependency mismatch libpxbackend was not being installed from vcpkg which lead to use of libpxbackend on the system causing library mismatch in rolling distros(ie arch linux) a
2024-11-28 00:29:14 -03:00
{
"name": "libproxy",
"version": "0.4.18#3"
},
LibCrypto: Add `libtommath` vcpkg dependency and link it An overlay port is required to add the `stdc-iec-559` and `install-pc` patches. The `stdc-iec-559` patch is required because Clang doesn't define `__STDC_IEC_559__`. However, glibc and musl define it if `__GCC_IEC_559` is not defined. The macro is taken from glibc source code. The `install-pc` patch is required because libtommath doesn't install the pkg-config files when building statically compromising our ability to find it during build. Clang: https://clang.llvm.org/c_status.html#:~:text=Yes-, IEC%2060559%20support,-Unknown glibc: https://sourceware.org/git/?p=glibc.git;a=blob; f=include/stdc-predef.h
2025-04-26 06:53:09 -03:00
{
"name": "libtommath",
"version": "1.3.0#2"
},
LibGfx: Decode AVIF images Use libavif to decode AVIF images in LibGfx.
2024-07-06 04:33:38 -03:00
{
"name": "libavif",
Meta: Update libavif to version 1.3.0#1 To update to ICU 78.1, a bump to the Vcpkg baseline is required. However, for some reason 1.3.0#0 fails to compile on the newer baseline. Updating to 1.3.0#1 fixes the issue.
2025-12-03 18:58:23 -03:00
"version": "1.3.0#1"
LibGfx: Decode AVIF images Use libavif to decode AVIF images in LibGfx.
2024-07-06 04:33:38 -03:00
},
LibGfx: Decode WebP images with libwebp
2024-07-12 05:08:39 -03:00
{
"name": "libwebp",
Meta: Update libwebp to version 1.6.0#1
2025-09-23 17:48:24 -03:00
"version": "1.6.0#1"
LibGfx: Decode WebP images with libwebp
2024-07-12 05:08:39 -03:00
},
Meta: Lock libxml2 version in vcpkg.json
2025-12-04 09:15:36 -03:00
{
"name": "libxml2",
"version": "2.13.8#1"
},
Meta: Pin recently added vcpkg dependencies
2024-12-23 14:51:16 -03:00
{
"name": "mman",
"version": "git-f5ff813#5"
},
{
"name": "openssl",
Meta: Update openssl to version 3.5.3
2025-09-23 17:48:25 -03:00
"version": "3.5.3#0"
Meta: Pin recently added vcpkg dependencies
2024-12-23 14:51:16 -03:00
},
Meta: Build QT with vcpkg on FreeBSD This is a workaround for the fact that on FreeBSD the system icu has symbol renaming disabled which causes our build to clash with the expectations of the system QT.
2025-06-29 18:46:51 -03:00
{
"name": "qtbase",
Meta: Update qtbase to 6.10.0#1
2026-01-09 12:43:01 -03:00
"version": "6.10.0#1"
Meta: Build QT with vcpkg on FreeBSD This is a workaround for the fact that on FreeBSD the system icu has symbol renaming disabled which causes our build to clash with the expectations of the system QT.
2025-06-29 18:46:51 -03:00
},
Meta+WebContent+LibWeb: Add, link and initialize SDL3
2025-08-15 10:55:09 -03:00
{
"name": "sdl3",
Meta: Update SDL3 to 3.2.28
2025-12-30 12:11:38 -03:00
"version": "3.2.28#0"
Meta+WebContent+LibWeb: Add, link and initialize SDL3
2025-08-15 10:55:09 -03:00
},
LibJS: Use simdjson for JSON.parse Replace the custom AK JSON parser with simdjson for parsing JSON in LibJS. This eliminates the intermediate AK::JsonValue object graph, going directly from JSON text to JS::Value. simdjson's on-demand API parses at ~4GB/s and only materializes values as they are accessed, making this both faster and more memory efficient than the previous approach. The AK JSON parser is still used elsewhere (WebDriver protocol, config files, etc.) but LibJS now uses simdjson exclusively for JSON.parse() and JSON.rawJSON().
2026-01-11 17:09:41 -03:00
{
"name": "simdjson",
Meta+LibJS: Upgrade simdjson to the latest version 5e0ee26e8bef854553dfe3a6cdf3ce508a926acd pulls in an old version of simdjson, this commit upgrades to the latest release. This commit also pins `dav1d` to the version it was before this change.
2026-01-15 21:48:48 -03:00
"version": "4.2.4#0"
LibJS: Use simdjson for JSON.parse Replace the custom AK JSON parser with simdjson for parsing JSON in LibJS. This eliminates the intermediate AK::JsonValue object graph, going directly from JSON text to JS::Value. simdjson's on-demand API parses at ~4GB/s and only materializes values as they are accessed, making this both faster and more memory efficient than the previous approach. The AK JSON parser is still used elsewhere (WebDriver protocol, config files, etc.) but LibJS now uses simdjson exclusively for JSON.parse() and JSON.rawJSON().
2026-01-11 17:09:41 -03:00
},
AK+LibWeb: Replace our home-grown base64 encoder/decoders with simdutf We currently have 2 base64 coders: one in AK, another in LibWeb for a "forgiving" implementation. ECMA-262 has an upcoming proposal which will require a third implementation. Instead, let's use the base64 implementation that is used by Node.js and recommended by the upcoming proposal. It handles forgiving decoding as well. Our users of AK's implementation should be fine with the forgiving implementation. The AK impl originally had naive forgiving behavior, but that was removed solely for performance reasons. Using http://mattmahoney.net/dc/enwik8.zip (100MB unzipped) as a test, performance of our old home-grown implementations vs. the simdutf implementation (on Linux x64): Encode Decode AK base64 0.226s 0.169s LibWeb base64 N/A 1.244s simdutf 0.161s 0.047s
2024-07-15 16:25:08 -03:00
{
"name": "simdutf",
Meta: Update simdutf to version 7.4.0
2025-08-27 07:36:52 -03:00
"version": "7.4.0#0"
AK+LibWeb: Replace our home-grown base64 encoder/decoders with simdutf We currently have 2 base64 coders: one in AK, another in LibWeb for a "forgiving" implementation. ECMA-262 has an upcoming proposal which will require a third implementation. Instead, let's use the base64 implementation that is used by Node.js and recommended by the upcoming proposal. It handles forgiving decoding as well. Our users of AK's implementation should be fine with the forgiving implementation. The AK impl originally had naive forgiving behavior, but that was removed solely for performance reasons. Using http://mattmahoney.net/dc/enwik8.zip (100MB unzipped) as a test, performance of our old home-grown implementations vs. the simdutf implementation (on Linux x64): Encode Decode AK base64 0.226s 0.169s LibWeb base64 N/A 1.244s simdutf 0.161s 0.047s
2024-07-15 16:25:08 -03:00
},
LibWeb: Add Skia painting command executor This change introduces Skia painter available under a flag. It's not yet match capabilities of Gfx::Painter and is not ready to replace it. Motivation: - The current CPU painter is a performance bottleneck on most websites. Our own GPU painter implementation is very immature and has received relatively little attention. - There is ongoing effort on building painter that supports affine transforms (AffineCommandExecutorCPU) but it is far from being on par with the default CPU painter. Skia will allow us to immediately get full transformation support for all painting commands. GPU painting: I experimented with Ganesh GPU-backend, however profiling revealed that without sharing viewport texture between WebContent and Browser processes, it won't bring much performance improvement compared to CPU-backend. Therefore, I decided to keep this PR focused on implementing most of painting commands and switch to GPU-backend in future changes. Text rendring: Skia painter uses glyph bitmaps produced by LibGfx. Using Skia for text rendering will require large refactoring of the font rendering subsystem. Currently, it's impossible to construct SkFont right before rendering because Gfx::VectorFont can't be serialized back into sequence of bytes. There is a problem with ugly include paths like: `#include <core/SkBitmap.h>`. I would prefer to have skia prefix in the path. There was an attempt to fix that but PR was rejected https://github.com/microsoft/vcpkg/pull/32660 Regressions compared to Gfx::Painter: - DrawText is not implemented - PaintTextShadow is not implemented - PaintRadialGradient and PaintLinearGradient do not support "transition hints" and repeat length - PaintConicGradient is not implemented - DrawTriangleWave is not implemented - DrawLine does not account for line style property - DrawScaledBitmap and DrawScaledImmutableBitmap do not account for scaling mode property
2024-06-10 08:22:04 -03:00
{
"name": "skia",
Meta+LibGfx+LibWeb: Update skia to 144 and remove overlay port Skia deprecated some non-span versions of their API, but they provided SK_SUPPORT_UNSPANNED_APIS to expose the legacy versions. SkFontMgr_New_FontConfig now requires a font scanner to be passed in. There were a few screenshot tests that visibily looked the same but skia must've changed some rendering infrastructure as the PNGs were not matching anymore so I rebaselined those and adjusted the fuzzy matching config to allow them to pass on both macOS and Linux. The empty-radial-gradient-crash Ref test started to fail as we were setting the horizontal scale factor to inf in when the height = 0. It looks like something changed to make doing that not valid anymore. The overlay port is removed as the issues, mainly skcms symbol import and export were resolved upstream in skia and utilized in the new port version.
2025-09-02 06:27:04 -03:00
"version": "144#0"
LibWeb: Add Skia painting command executor This change introduces Skia painter available under a flag. It's not yet match capabilities of Gfx::Painter and is not ready to replace it. Motivation: - The current CPU painter is a performance bottleneck on most websites. Our own GPU painter implementation is very immature and has received relatively little attention. - There is ongoing effort on building painter that supports affine transforms (AffineCommandExecutorCPU) but it is far from being on par with the default CPU painter. Skia will allow us to immediately get full transformation support for all painting commands. GPU painting: I experimented with Ganesh GPU-backend, however profiling revealed that without sharing viewport texture between WebContent and Browser processes, it won't bring much performance improvement compared to CPU-backend. Therefore, I decided to keep this PR focused on implementing most of painting commands and switch to GPU-backend in future changes. Text rendring: Skia painter uses glyph bitmaps produced by LibGfx. Using Skia for text rendering will require large refactoring of the font rendering subsystem. Currently, it's impossible to construct SkFont right before rendering because Gfx::VectorFont can't be serialized back into sequence of bytes. There is a problem with ugly include paths like: `#include <core/SkBitmap.h>`. I would prefer to have skia prefix in the path. There was an attempt to fix that but PR was rejected https://github.com/microsoft/vcpkg/pull/32660 Regressions compared to Gfx::Painter: - DrawText is not implemented - PaintTextShadow is not implemented - PaintRadialGradient and PaintLinearGradient do not support "transition hints" and repeat length - PaintConicGradient is not implemented - DrawTriangleWave is not implemented - DrawLine does not account for line style property - DrawScaledBitmap and DrawScaledImmutableBitmap do not account for scaling mode property
2024-06-10 08:22:04 -03:00
},
Meta+LibWebView: Install and link sqlite3 with vcpkg We will use sqlite3 as a replacement for LibSQL. Using a tried-and-true database will allow us to avoid maintaining our an incomplete, non-ACID, and less performant implementation. It also means we do not have to launch and manage the singleton SQLServer process.
2024-06-04 17:28:35 -03:00
{
"name": "sqlite3",
Meta: Update sqlite3 to version 3.50.4
2025-08-27 07:37:20 -03:00
"version": "3.50.4#0"
LibGfx: Use the woff2 library to decode WOFF2 font files This saves us the trouble of maintaining our own implementation, and instantly brings us to full WOFF2 feature parity with others. Co-Authored-By: Andrew Kaster <akaster@serenityos.org>
2024-06-06 06:10:01 -03:00
},
{
"name": "woff2",
Meta: Update woff2 to version 1.0.2#5 This includes a patch which lets it build on GCC 15. See https://github.com/microsoft/vcpkg/pull/45132
2025-04-22 11:43:01 -03:00
"version": "1.0.2#5"
Meta: Add explicit vcpkg dependency for zlib zlib is already included transitively for other dependencies, include it explicitly and link it with `LibCompress`.
2025-03-01 13:32:14 -03:00
},
{
"name": "zlib",
"version": "1.3.1"
Meta+LibWebView: Install and link sqlite3 with vcpkg We will use sqlite3 as a replacement for LibSQL. Using a tried-and-true database will allow us to avoid maintaining our an incomplete, non-ACID, and less performant implementation. It also means we do not have to launch and manage the singleton SQLServer process.
2024-06-04 17:28:35 -03:00
}
]
}
Reference in a new issue Copy permalink