static/README.wasm.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 1565181908a06dcdb8d97d6be8ff773acd1d05cb
Author: Andrea Gelmini <andrea.gelm...@gelma.net>
AuthorDate: Mon Aug 19 07:53:53 2024 +0200
Commit: Julien Nabet <serval2...@yahoo.fr>
CommitDate: Mon Aug 19 08:55:14 2024 +0200
Fix typo
Change-Id: I3277386244f3a00c2756525829924870e3a3d2bb
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/172030
Tested-by: Julien Nabet <serval2...@yahoo.fr>
Reviewed-by: Julien Nabet <serval2...@yahoo.fr>
diff --git a/static/README.wasm.md b/static/README.wasm.md
index 69ca55a74322..64d5a361704f 100644
--- a/static/README.wasm.md
+++ b/static/README.wasm.md
@@ -109,7 +109,7 @@
workdir/UnpackedTarball/freetype/instdir/lib/libfreetype.a), not against the Qt
$QT5DIR/lib/libqtfreetype.a). This mismatch between the include files that Qt
is compiled against,
vs. the archive actually linked in, seems to not cause issues in practice.
(If it did, we could
either try to make both Qt and LO link against e.g. -sUSE_FREETYPE from
emscripten-ports, or we
-could move Qt from a prequisite to a proper external/qt5 LO module built
during the LO build, and
+could move Qt from a prerequisite to a proper external/qt5 LO module built
during the LO build, and
hack its configuration to build against LO's external/freetype etc. The
former approach, building Qt
with -sUSE_FREETYPE, is even tried in qtbase/src/gui/configure.json, but
apparently fails for
reasons not studied further yet, cf. Qt's config.log.)
