| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Use char, int, float, double, instead of their
g-prefixed counterparts. This follows the GTK4
api style changes.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
gtk-doc uses informaltable elements for formatting
the function listings in reference pages, while
pandoc-generated docbook uses informaltable elements
for regular tables. Thankfully, they end up with
different border attributes in the html, so we can
use that to style them differently.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
GTK 4 added its own variant of G_DECLARE_
under the name of GDK_DECLARE_INTERNAL_TYPE.
Recognize it.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The "Abstract" looks irritating in the otherwise
very minimal output we produce. Just leave it out.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add tests for signal, property and action syntax
as symbols in doc comments. And make the remaining
tests robust enough to survive the addition.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is building on the work in the previous commit. The syntax chosen
for doc comments is Class|action. We also need to allow periods in symbols,
since those are commonly used to separate prefixes in action names.
Here is a typical doc comment for an action:
/**
* GtkColorChooserWidget|color.select:
* @red: the red value, between 0 and 1
* @green: the green value, between 0 and 1
* @blue: the blue value, between 0 and 1
* @alpha: the alpha value, between 0 and 1
*
* Emits the #GtkColorChooser::color-activated signal for
* the given color.
*/
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | | |
GTK4 can define actions for widget classes.
Write these out to a .actions file.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
scangobj: Don't sort an absence of signals/properties
Closes #125
See merge request GNOME/gtk-doc!53
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
qsort (NULL, 0, ...) is formally considered to be undefined behaviour,
and is diagnosed as such by the undefined behaviour sanitizer.
Resolves: #125
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
mkhtml2: Fix apparent typo "os.getcmd()"
See merge request GNOME/gtk-doc!50
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
os.getcwd() would make sense here.
This call isn't actually reached in practice, because the
gtkdoc-mkhtml2 script entry point always passes something for
options.output_dir, even if it's ".".
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | | |
build: Distribute more files from git in official release tarballs
Closes #109
See merge request GNOME/gtk-doc!55
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This allows the Autotools dist tarball to continue to be used as the
official release artifact, while still allowing distributors to try
Meson builds.
To help to debug this if it fails, the meson-build step records a
list of all files in git (ideally we'd use 'meson dist' but the
container image doesn't currently include git, so this is the next
best thing), while the meson-from-tarball step records a list of all
files in the tarball. They are in a normalized order that can be diff'ed.
Tests: #109
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Many of these are necessary for the Meson build, and some merely seem
potentially useful.
Resolves: #109
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | | |
Run tests under Meson again
See merge request GNOME/gtk-doc!52
|
| | | |
| | | |
| | | |
| | | | |
This reverts commit 1f0a7303b5158f811cea29fedd0832d333367deb.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Two tests rely on symbols in <SUBSECTION Private> and
<SUBSECTION Standard> being ignored. The Autotools build automatically
copies -sections.txt into the build directory where gtk-doc will find
it, but the Meson build does not, resulting in gtk-doc generating a
new -sections.txt that does not know which symbols to ignore, and
complaining that the private symbols are now undocumented.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
Otherwise tests will fail when we can't load external entities from it.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
Install the same files with Meson as with Autotools
See merge request GNOME/gtk-doc!48
|
| | |
| | |
| | |
| | | |
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|/ /
| |
| |
| |
| |
| |
| | |
Previously, these were installed when building with Autotools but not
when building with Meson.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
es: do not translate '<_:example-1/>'
Closes #115
See merge request GNOME/gtk-doc!46
|
|/ / |
|
| | |
|
|/ |
|
|
|
|
| |
Fixes #115
|
|\
| |
| |
| |
| | |
scan: support deprecated struct members
See merge request GNOME/gtk-doc!43
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gcc allows deprecating members of structs. For example:
struct data {
int x G_GNUC_DEPRECATED_FOR(replacement);
};
However, this currently causes the entire struct to be marked as
deprecated and confuses mkdb because it doesn't understand the
G_GNUC_DEPRECATED_FOR symbol.
Fix this by having the whole struct only be marked as deprecated if the
'_DEPRECATED' is after the closing bracket of the struct, similar to how
it already does for enums, and having scan automatically remove all
G_GNUC_* decorators from struct members, similar to how it already does
for functions.
|
|\
| |
| |
| |
| | |
Fixes to build latest glib
See merge request GNOME/gtk-doc!42
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
For some reason, glib has to put empty line before and after each of
these lines otherwise the symbol following it is undeclared.
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
scangobj: fix -Wdouble-promotion warnings
See merge request GNOME/gtk-doc!41
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If a project passes the -Wdouble-promotion CFLAG when compiling the
generated *scan.c file, then it emits some warnings. For example in the
Devhelp project:
```
Building documentation for devhelp-3
devhelp-3-scan.c: In function ‘describe_double_constant’:
devhelp-3-scan.c:595:39: warning: implicit conversion from ‘float’ to
‘gdouble’ {aka ‘double’} to match other operand of binary expression
[-Wdouble-promotion]
595 | #define GTKDOC_COMPARE_FLOAT(x, y) (x <= y && x >= y
| ^~
devhelp-3-scan.c:608:12: note: in expansion of macro ‘GTKDOC_COMPARE_FLOAT’
608 | else if (GTKDOC_COMPARE_FLOAT (value, G_MAXFLOAT))
| ^~~~~~~~~~~~~~~~~~~~
[...]
```
An example where the -Wdouble-promotion CFLAG is used is with the
AX_COMPILER_FLAGS Autotools macro, part of autoconf-archive.
-----
In the diff, the `value` variable is of type gdouble.
|
|\ \
| | |
| | |
| | |
| | | |
Remove unused libpython3 dependency
See merge request GNOME/gtk-doc!39
|
| |/
| |
| |
| |
| |
| | |
gtk-doc only requires the interpreter, and Meson itself already depends
on python3 >= 3.5, so that check we useless and breaks build on CI
docker that doesn't contain libpython3-dev.
|
| | |
|
| |
| |
| |
| |
| | |
This is a workaround for missing dtd caching in libxml2 that turns into
extrem overhead for documents with many xincludes.
|
|\ \
| | |
| | |
| | |
| | | |
Please make the output reproducible
See merge request GNOME/gtk-doc!37
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Whilst working on the Reproducible Builds effort [0] we noticed that
gtk-doc generates unreproducible output.
There will likely be more issues but this one is at least fairly
simple in that it iterates over a set structure when printing
some .devhelp2 headers, for example:
│ │ │ │ - <sub name="Index of new API in 0.99.5" link="api-index-0-99-5.html"/>
│ │ │ │ - <sub name="Index of new API in 0.9.22" link="api-index-0-9-22.html"/>
│ │ │ │ <sub name="Index of new API in 0.9.0" link="api-index-0-9-0.html"/>
│ │ │ │ - <sub name="Index of new API in 0.9.1" link="api-index-0-9-1.html"/>
│ │ │ │ + <sub name="Index of new API in 0.9.19" link="api-index-0-9-19.html"/>
│ │ │ │ <sub name="Index of new API in 0.99.8" link="api-index-0-99-8.html"/>
│ │ │ │ + <sub name="Index of new API in 0.99.5" link="api-index-0-99-5.html"/>
│ │ │ │ <sub name="Index of new API in 1.0" link="api-index-1-0.html"/>
│ │ │ │ - <sub name="Index of new API in 0.9.19" link="api-index-0-9-19.html"/>
│ │ │ │ <sub name="Index of new API in 0.9.2" link="api-index-0-9-2.html"/>
│ │ │ │ + <sub name="Index of new API in 0.9.1" link="api-index-0-9-1.html"/>
│ │ │ │ + <sub name="Index of new API in 0.9.22" link="api-index-0-9-22.html"/>
This was originally filed in Debian as #946311 [1].
[0] https://reproducible-builds.org/
[1] https://bugs.debian.org/946331
Signed-off-by: Chris Lamb <lamby@debian.org>
|
|\ \
| |/
|/|
| |
| | |
meson: Fix running tests
See merge request GNOME/gtk-doc!40
|
|/ |
|
| |
|