mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-07-31 06:13:29 +02:00
.gitlab-ci
.reuse
LICENSES
docs
reference
gio
dbus-error.md
dbus-introspection.md
dbus-name-owning.md
dbus-name-watching.md
dbus-utils.md
error.md
file-attributes.md
gapplication.rst
gdbus-codegen.rst
gdbus.rst
gio-querymodules.rst
gio.rst
gio.toml.in
glib-compile-resources.rst
glib-compile-schemas.rst
gresource.rst
gsettings.rst
gvfs-overview.odg
gvfs-overview.png
io-scheduler.md
menu-example.png
menu-exporter.md
menu-model.png
meson.build
migrating-gconf.md
migrating-gdbus.md
migrating-gnome-vfs.md
migrating-posix.md
networking.md
overview.md
pollable-utils.md
tls-overview.md
unix-mounts.md
urlmap.js
girepository
glib
gmodule
gobject
AUTHORS
COPYING
NEWS
meson.build
CODEOWNERS
backports.md
issue-and-merge-request-management.md
macros.md
meson-version.md
rationales.md
releasing.md
roadmap.md
supported-platforms.md
testing.md
toolchain-requirements.md
win32-build.md
fuzzing
gio
girepository
glib
gmodule
gobject
gthread
introspection
m4macros
po
subprojects
tests
tools
.clang-format
.dir-locals.el
.editorconfig
.gitignore
.gitlab-ci.yml
.gitmodules
.lcovrc
CODE_OF_CONDUCT.md
CONTRIBUTING.md
COPYING
INSTALL.md
NEWS
README.md
SECURITY.md
glib.doap
meson.build
meson_options.txt
aa28326b87
Now that the reference documentation uses gi-docgen, it's more troublesome to generate in less standard build scenarios like cross-compiling. In distributions like Debian, reference documentation is generally packaged separately (in libglib2.0-doc in Debian's case), but man pages are generally packaged alongside the executables themselves (in the libglib2.0-bin and libglib2.0-dev-bin packages, in Debian's case). We can exclude the reference documentation when cross-compiling, but ideally we would like the man pages to still be built, so that a cross-compiled libglib2.0-bin or libglib2.0-dev-bin package has the same content as a native build. Signed-off-by: Simon McVittie <smcv@debian.org>
