1. 03 6月, 2019 15 次提交
  2. 17 5月, 2019 1 次提交
  3. 13 5月, 2019 1 次提交
    • A
      examples: Install under $(docdir) · 4faaaa8b
      Andrea Bolognani 提交于
      Our build system doesn't currently install the various
      example programs provided along libvirt; however, both the
      upstream .spec file and the Debian packaging go out of
      their way to make sure these useful demos are included in
      the respective documentation packages.
      
      Moreover, doing so without help from the upstream build
      system is easy to get wrong: the libvirt-docs RPM package,
      for example, ends up missing one of the examples and
      including a bunch of empty .deps/ directories.
      
      Install the examples in $(docdir) as part of our regular
      procedure, so that users and downstreams don't have to do
      anything special about them.
      Signed-off-by: NAndrea Bolognani <abologna@redhat.com>
      Acked-by: NMichal Privoznik <mprivozn@redhat.com>
      4faaaa8b
  4. 15 4月, 2019 1 次提交
  5. 05 4月, 2019 4 次提交
  6. 03 4月, 2019 1 次提交
    • D
      examples: fix 64-bit integer formatting on Windows · 11ea6266
      Daniel P. Berrangé 提交于
      The Windows printf functions don't support %llu/%lld for printing 64-bit
      integers. For most of libvirt this doesn't matter as we rely on gnulib
      which provides a replacement printf that is sane.
      
      The example code is designed to compile against the normal OS headers,
      with no use of gnulib and thus has to use the platform specific printf.
      To deal with this we must use the macros PRI* macros from inttypes.h
      to get the platform specific format string.
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      11ea6266
  7. 15 3月, 2019 1 次提交
  8. 07 3月, 2019 1 次提交
  9. 10 1月, 2019 1 次提交
  10. 09 1月, 2019 3 次提交
  11. 08 1月, 2019 3 次提交
    • E
      examples: Avoid gnulib, have standalone examples · acf522e8
      Eric Blake 提交于
      Commit 0c6ad476 updated gnulib, which rearranged some of the
      conditions in gnulib wrapper headers such that compilation
      started failing on BSD systems when the normal system <unistd.h>
      tried to include another system header but instead got a
      gnulib wrapper header in an incomplete state; this is because
      gnulib headers only work if <config.h> is included first.
      
      Commit b6f78259 papered over the symptoms of that by including
      <config.h> in all the examples.  But this logic is backwards -
      if our examples are truly meant to be stand-alone, they should
      NOT depend on how libvirt was configured, and should NOT
      depend on the gnulib fixes for system quirks.  In particular,
      if an example does not need to link against libgnulib.la,
      then it also does not need to use -Ignulib in its compile
      flags, and likewise does not need to include <config.h> since
      none of the gnulib wrapper headers should be interfering.
      
      So, revert (most of) b6f78259 (except for the bogus pre-patch
      use of "config.h" in admin/logging.c: if config.h is included,
      it should be via <> rather than "", and must be before any
      system headers); then additionally nuke all mention of
      <config.h>, -Ignulib, and -llibgnu.la, making all of the
      examples truly standalone.
      Signed-off-by: NEric Blake <eblake@redhat.com>
      Acked-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      acf522e8
    • E
      examples: Drop event-test.c dependency on gnulib <verify.h> · 6933ebc4
      Eric Blake 提交于
      Pulling in gnulib just for the <verify.h> header is rather
      expensive, especially since that header does not require us
      to link against gnulib.  It's better to make the event-test
      example be standalone by just open-coding a more limited form
      of a verify() macro that depends on modern gcc (we have enough
      CI coverage that even though the verify is now a no-op in
      older setups, we will still notice if we fail to add an event
      - as a quick test, I was still able to provoke a compile
      failure on Fedora 29 when deleting a line from domainEvents).
      Signed-off-by: NEric Blake <eblake@redhat.com>
      Acked-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      6933ebc4
    • E
      maint: Prefer AM_CPPFLAGS over INCLUDES · 1862a554
      Eric Blake 提交于
      Our use of INCLUDES in Makefile.am hearkens back to when we had to
      cater to automake 1.9.6 (thanks, RHEL 5) which lacked AM_CPPFLAGS.
      Modern Automake flags a warning that INCLUDES is deprecated, and
      now that we mandate RHEL 7 or better (see commit c1bc9c66), we no
      longer have to cater to the old spelling.  This change will also
      make it easier to do per-binary CPPFLAGS.
      Signed-off-by: NEric Blake <eblake@redhat.com>
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      1862a554
  12. 07 1月, 2019 2 次提交
  13. 03 1月, 2019 1 次提交
  14. 14 12月, 2018 1 次提交
    • D
      Remove all Author(s): lines from source file headers · 60046283
      Daniel P. Berrangé 提交于
      In many files there are header comments that contain an Author:
      statement, supposedly reflecting who originally wrote the code.
      In a large collaborative project like libvirt, any non-trivial
      file will have been modified by a large number of different
      contributors. IOW, the Author: comments are quickly out of date,
      omitting people who have made significant contribitions.
      
      In some places Author: lines have been added despite the person
      merely being responsible for creating the file by moving existing
      code out of another file. IOW, the Author: lines give an incorrect
      record of authorship.
      
      With this all in mind, the comments are useless as a means to identify
      who to talk to about code in a particular file. Contributors will always
      be better off using 'git log' and 'git blame' if they need to  find the
      author of a particular bit of code.
      
      This commit thus deletes all Author: comments from the source and adds
      a rule to prevent them reappearing.
      
      The Copyright headers are similarly misleading and inaccurate, however,
      we cannot delete these as they have legal meaning, despite being largely
      inaccurate. In addition only the copyright holder is permitted to change
      their respective copyright statement.
      Reviewed-by: NErik Skultety <eskultet@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      60046283
  15. 14 11月, 2018 2 次提交
  16. 27 8月, 2018 1 次提交
  17. 16 8月, 2018 1 次提交