1. 09 Jul, 2019 1 commit
    • Marc-André Lureau's avatar
      Drop autotools · 9837f974
      Marc-André Lureau authored
      Maintaining 1 build system is hard. Maintaining 2 is even harder.
      It seems the meson build system is now in good shape to replace
      autotools. Like many desktop projects, let's move entirely to meson
      and drop autotools support.
      Known changes:
      - generating changelog files in the dist tarball. This is not strictly
        required, and can be added back later.
      - generated files are not included in the dist tarball. In some ways,
        this can be considered a good thing.
      Signed-off-by: default avatarMarc-André Lureau <marcandre.lureau@redhat.com>
      Acked-by: Victor Toso's avatarVictor Toso <victortoso@redhat.com>
  2. 22 Nov, 2018 1 commit
  3. 02 Oct, 2018 1 commit
  4. 05 Sep, 2018 1 commit
  5. 30 Aug, 2018 1 commit
    • Eduardo Lima (Etrunko)'s avatar
      Add support for building with meson/ninja · 7a87356b
      Eduardo Lima (Etrunko) authored
      In a comparison with current autotools build system, meson/ninja
      provides a huge improvement in build speed, while keeping the same
      functionalities currently available and being considered more user
      The new system coexists within the same repository with the current one,
      so we can do more extensive testing of its functionality before deciding
      if the old system can be removed, or for some reason, has to stay for
      - Meson: https://mesonbuild.com
        This is the equivalent of autogen/configure step in autotools. It
        generates the files that will be used by ninja to actually build the
        source code.
        The project has received lots of traction recently, with many GNOME
        projects willing to move to this new build system. The following wiki
        page has more details of the status of the many projects being ported:
        Meson has a python-like syntax, easy to read, and the documentation
        on the project is very complete, with a dedicated page on how to port
        from autotools, explaining how most common use cases can be
        implemented using meson.
        Other important sources of information:
      - Ninja: https://ninja-build.org
        Ninja is the equivalent of make in an autotools setup, which actually
        builds the source code. It has being used by large and complex
        projects such as Google Chrome, Android and LLVM. There is not much to
        say about ninja (other than it is much faster than make) because we
        won't interact directly with it as much, as meson does the middle man
        job here. The reasoning for creating ninja in the first place is
        explained on the following post:
        Also its manual provides more in-depth information about the design
      - Basic workflow:
        Meson package is available for most if not all distros, so, taking
        Fedora as an example, we only need to run:
          # dnf -y install meson ninja-build.
        With Meson, building in-tree is not possible at all, so we need to
        pass a directory as argument to meson where we want the build to be
        done. This has the advantage of creating builds with different options
        under the same parent directory, e.g.:
          $ meson ./build --prefix=/usr
          $ meson ./build-extra -Dextra-checks=true -Dalignment-checks=true
        After configuration is done, we call ninja to actually do the build.
          $ ninja -C ./build
          $ ninja -C ./build install
        Ninja defaults to parallel builds, and this can be changed with the -j
          $ ninja -j 10 -C ./build
      - Hacking:
        * meson.build: Mandatory for the project root and usually found under
                       each directory you want something to be built.
        * meson_options.txt: Options that can interfere with the result of the
      Signed-off-by: default avatarEduardo Lima (Etrunko) <etrunko@redhat.com>
      Acked-by: Victor Toso's avatarVictor Toso <victortoso@redhat.com>
  6. 04 Jun, 2018 1 commit
  7. 25 Apr, 2018 1 commit
    • Eduardo Lima (Etrunko)'s avatar
      tests: Shut up warnings about unitialized struct fields · 7d119752
      Eduardo Lima (Etrunko) authored
      Build complains about lots of unitialized fields in TestCase definition,
      for instance:
      ../tests/session.c:276:11: warning: missing initializer for field ‘message’ of ‘TestCase {aka const struct <anonymous>}’ [-Wmissing-field-initializers]
                 "spice://[::]:5910" },
      ../tests/session.c:11:18: note: ‘message’ declared here
           const gchar *message;
      ../tests/session.c:282:11: warning: missing initializer for field ‘unix_path’ of ‘TestCase {aka const struct <anonymous>}’ [-Wmissing-field-initializers]
                 "password may be visible in process listings"},
      Signed-off-by: default avatarEduardo Lima (Etrunko) <etrunko@redhat.com>
      Acked-by: Frediano Ziglio's avatarFrediano Ziglio <fziglio@redhat.com>
  8. 02 Mar, 2018 2 commits
  9. 13 Feb, 2018 1 commit
  10. 04 Sep, 2017 3 commits
  11. 01 Aug, 2017 1 commit
  12. 19 Oct, 2016 1 commit
  13. 17 Oct, 2016 4 commits
  14. 05 Oct, 2016 1 commit
  15. 03 Oct, 2016 1 commit
  16. 02 Sep, 2016 1 commit
  17. 03 Aug, 2016 2 commits
  18. 07 Jul, 2016 4 commits
  19. 13 Jun, 2016 1 commit
  20. 02 Jun, 2016 6 commits
  21. 01 Jun, 2016 1 commit
    • Victor Toso's avatar
      tests: fix build with smartcard enabled · 756f1fe8
      Victor Toso authored
      In file included from
      from ../src/spice-channel-priv.h:35,
      from ../src/spice-file-transfer-task-priv.h:28,
      from file-transfer.c:3:
      ../spice-common/common/messages.h:45:23: fatal error: libcacard.h: No such file or directory
      compilation terminated.
      Acked-by: default avatarPavel Grunt <pgrunt@redhat.com>
  22. 18 Mar, 2016 1 commit
  23. 15 Mar, 2016 1 commit
  24. 11 Mar, 2016 2 commits