From 46c650900532fe4c80af66974c41c38d1acd0344 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Vladim=C3=ADr=20Vondru=C5=A1?= Date: Tue, 23 Nov 2021 21:27:29 +0100 Subject: [PATCH] doc: adapt to a rename of the Textured Triangle example. --- doc/platforms-html5.dox | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/platforms-html5.dox b/doc/platforms-html5.dox index 01c762695..814e5014e 100644 --- a/doc/platforms-html5.dox +++ b/doc/platforms-html5.dox @@ -434,12 +434,12 @@ you need more advanced styling, check out [m.css](https://mcss.mosra.cz). Emscripten applications don't have access to a filesystem, which means you need to bundle the files explicitly. One possibility is via @ref Corrade::Utility::Resource (basically the same way as you probably already -bundle shader code etc., as shown in the @ref examples-textured-triangle -example). In this case the file is compiled directly into the `*.wasm` binary, -which is the most optimal way, but it means you need to port your code away -from the usual filesystem APIs. Another possibility is via the -@cmake emscripten_embed_file() @ce CMake macro, which is available -when you build for Emscripten, coming from the [UseEmscripten.cmake](https://github.com/mosra/toolchains/blob/master/modules/UseEmscripten.cmake) +bundle shader code etc., as shown in the @ref examples-texturedquad example). +In this case the file is compiled directly into the `*.wasm` binary, which is +the most optimal way, but it means you need to port your code away from the +usual filesystem APIs. Another possibility is via the +@cmake emscripten_embed_file() @ce CMake macro, which is available when you +build for Emscripten, coming from the [UseEmscripten.cmake](https://github.com/mosra/toolchains/blob/master/modules/UseEmscripten.cmake) module: @code{.cmake}