docs: Fix references to pkg-config files

The pkg-config files for GDK were dropped in 4.0, and now the GTK
pkg-config files have been renamed.
This commit is contained in:
Emmanuele Bassi 2019-02-06 10:40:51 +01:00
parent 1668496359
commit 22f073b57b
2 changed files with 2 additions and 4 deletions

View File

@ -64,8 +64,7 @@
* *
* The functions in this section are specific to the GDK Wayland backend. * The functions in this section are specific to the GDK Wayland backend.
* To use them, you need to include the `<gdk/gdkwayland.h>` header and use * To use them, you need to include the `<gdk/gdkwayland.h>` header and use
* the Wayland-specific pkg-config files to build your application (either * the Wayland-specific pkg-config `gtk4-wayland` file to build your application.
* `gdk-wayland-3.0` or `gtk+-wayland-3.0`).
* *
* To make your code compile with other GDK backends, guard backend-specific * To make your code compile with other GDK backends, guard backend-specific
* calls by an ifdef as follows. Since GDK may be built with multiple * calls by an ifdef as follows. Since GDK may be built with multiple

View File

@ -53,8 +53,7 @@
* *
* The functions in this section are specific to the GDK X11 backend. * The functions in this section are specific to the GDK X11 backend.
* To use them, you need to include the `<gdk/gdkx.h>` header and use * To use them, you need to include the `<gdk/gdkx.h>` header and use
* the X11-specific pkg-config files to build your application (either * the X11-specific pkg-config file `gtk4-x11` to build your application.
* `gdk-x11-3.0` or `gtk+-x11-3.0`).
* *
* To make your code compile with other GDK backends, guard backend-specific * To make your code compile with other GDK backends, guard backend-specific
* calls by an ifdef as follows. Since GDK may be built with multiple * calls by an ifdef as follows. Since GDK may be built with multiple