aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPekka Paalanen <pq@iki.fi>2025-12-28 10:36:16 +0200
committerPekka Paalanen <pq@iki.fi>2025-12-29 11:19:01 +0200
commitd1b8f352c3f68c8394f0a3f362d19ac18479d95f (patch)
tree2e233b4189cca6a9543d96826fbd93786646ce84
parentdoc: reinstate image maps (diff)
downloadwayland-d1b8f352c3f68c8394f0a3f362d19ac18479d95f.tar
wayland-d1b8f352c3f68c8394f0a3f362d19ac18479d95f.tar.gz
wayland-d1b8f352c3f68c8394f0a3f362d19ac18479d95f.tar.bz2
wayland-d1b8f352c3f68c8394f0a3f362d19ac18479d95f.tar.lz
wayland-d1b8f352c3f68c8394f0a3f362d19ac18479d95f.tar.xz
wayland-d1b8f352c3f68c8394f0a3f362d19ac18479d95f.tar.zst
wayland-d1b8f352c3f68c8394f0a3f362d19ac18479d95f.zip
server: fix wl_signal_add Doxygen warning
$ meson compile -C build -v xml-Server-doc INFO: autodetecting backend as ninja INFO: calculating backend command to run: /usr/bin/ninja -C /home/pq/git/wayland/build -v doc/doxygen/xml/Server/combine.xslt doc/doxygen/xml/Server/index.xml ninja: Entering directory `/home/pq/git/wayland/build' [1/1] /home/pq/git/wayland/doc/doxygen/gen-doxygen.py --builddir=doc/doxygen/xml/Server --section=Server --output-format=xml doc/doxygen/wayland.doxygen ../doc/doxygen/../../src/wayland-util.h ../doc/doxygen/../../src/event-loop.c ../doc/doxygen/../../src/wayland-server.c ../doc/doxygen/../../src/wayland-server.h ../doc/doxygen/../../src/wayland-server-core.h ../doc/doxygen/../../src/wayland-shm.c /home/pq/git/wayland/src/wayland-server-core.h:394: warning: explicit link request to 'wl_signal_add' could not be resolved I don't know why, but the "explicit link" mark-up fails, while the automatic link mark-up works. This warning disappears. Signed-off-by: Pekka Paalanen <pq@iki.fi>
-rw-r--r--src/wayland-server-core.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/wayland-server-core.h b/src/wayland-server-core.h
index c2dcc21..586ecfb 100644
--- a/src/wayland-server-core.h
+++ b/src/wayland-server-core.h
@@ -391,7 +391,7 @@ wl_client_set_max_buffer_size(struct wl_client *client, size_t max_buffer_size);
* object destruction.
*
* Clients should create wl_listener objects manually and can register them as
- * listeners to signals using #wl_signal_add, assuming the signal is
+ * listeners to signals using wl_signal_add(), assuming the signal is
* directly accessible. For opaque structs like wl_event_loop, adding a
* listener should be done through provided accessor methods. A listener can
* only listen to one signal at a time.