1. 17 Sep, 2018 1 commit
  2. 16 Dec, 2017 1 commit
    • Inigo Martínez's avatar
      build: Make generate-plugin-docs.pl independent of autotools · 28914f6a
      Inigo Martínez authored
      `generate-plugin-docs.pl` script which is used to parse
      `nm-setting-c*.c` files depends on autotools. This is because it
      parses the `Makefile.am` in order to figure out the setting files
      it needs to parse.
      
      This patch makes the script independent of autotools by passing
      the necessary setting files by command line instead of parsing the
      `Makefile.am` file. It also changes the autotools' and meson's
      accordingly.
      28914f6a
  3. 05 Sep, 2017 1 commit
  4. 21 Nov, 2016 2 commits
  5. 19 Oct, 2016 1 commit
  6. 19 Nov, 2014 3 commits
    • Jiří Klimeš's avatar
      af525e8a
    • Dan Winship's avatar
      libnm: Override parts of nm-setting-docs.xml · 36156b70
      Dan Winship authored
      Add "---dbus---" sections to the NMSetting property docs, in the same
      style as the plugin docs, parse them out into a file
      "nm-setting-docs-overrides.xml", and use them to override the GObject
      property docs in nm-setting-docs.xml.
      
      This lets us put more D-Bus-specific information in the setting docs,
      without cluttering up the property docs, and it also lets us document
      dbus-only properties.
      36156b70
    • Dan Winship's avatar
      libnm, libnm-util: move settings doc generation to libnm-core · c1448698
      Dan Winship authored
      Move the settings/plugins doc generation from libnm-util to
      libnm-core, since libnm-util isn't being updated for all new
      properties.
      
      With this commit, the keyfile and ifcfg-rh documentation is basically
      unchanged, except that deprecated properties are now gone, and new
      properties have been added, and the sections are in a different order.
      (generate-plugin-docs.pl just outputs the settings in Makefile order,
      and they were unsorted in libnm-util, but are sorted in libnm-core).
      
      The settings documentation used for nm-settings.5, the D-Bus API docs,
      and the nmcli help is changed a bit more at this point, and mostly for
      the worse, since the libnm-core setting properties don't match up with
      the D-Bus API as well as the libnm-util ones do. To be fixed...
      
      (I also removed the "plugins docs" line in each plugin docs comment
      block while moving them, since those blocks will be used for more than
      just plugins soon, and it's sort of obvious anyway.)
      c1448698
  7. 04 Sep, 2014 1 commit
  8. 29 Aug, 2014 1 commit
    • Jiří Klimeš's avatar
      libnm-util: generate-plugin-docs.pl script for extracting plugin docs · 1c2174a8
      Jiří Klimeš authored
      The scripts extracts plugin description from document comments for particular
      properties and builds a XML file out of the data. The XML file can be used
      later for generating manual pages or other documentation.
      
      Unfortunately, gtk-doc won't allow descriptions that would be separated from
      the main gtk-doc stuff. But it is still useful to have plugin description bits
      co-located with property definitions. We use our home-grown comments and parse
      them ourself. Afterall it's not that bad, and in addition it brings us a
      freedom in shaping the comments to our needs.
      1c2174a8