On Tue, 2018-02-13 at 15:13 +0100, Frederic Peters wrote: > > On Tue, 2018-02-13 at 11:19 +0000, Emmanuele Bassi wrote: > > > Work is in progress to let maintainers upload tarballs with the > > > generate API reference for developer.gnome.org > > > > Hi, > > okay, how is that supposed to work in general? As Meson builds out > > of > > the source tree, is that "work in progress" meant to be Meson > > specific? > > Developer.gnome.org still looks for "markers" in source tarballs > (like > include gtk-doc.make in Makefile.am) and use those to extract the > documentation module name (ex: for gtk+ it would extract three doc > modules, gtk4, gdk4, gsk4). > > What's new and in progress is the possibility to map those modules to > external documentation tarballs that will contain the generated HTML > files. > > Some parts of the process are in place already, from manually > generated documentation tarballs for GTK+, published at: > https://download.gnome.org/docs/gtk+/3.93/ > we can now create https://developer.gnome.org/gtk4/3.93/ > > (this is very fresh, literally two days ago) > > Now no maintainer would want the burden to generate those additional > tarballs and they should be automatically created and published by a > CI system (gnome continuous or buildstream or whatever). > > Wrt evolution developer.gnome.org still lacks the code to find the > gtk-doc markers in CMakeLits.txt files. (some experimental code was > added for meson as used in GTK+)
I have a few platform-level daemons that could do with having their gtk-doc on developer.gnome.org. Is there an example of what commands would need to be run to create and package the docs, and how to get them installed on gnome.org? _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
