1. 11 May, 2020 1 commit
  2. 01 Apr, 2020 1 commit
  3. 14 Mar, 2020 1 commit
    • cmake: use install directories provided via GNUInstallDirs · 87fc539f
      We currently hand-code logic to configure where to install our artifacts
      via the `LIB_INSTALL_DIR`, `INCLUDE_INSTALL_DIR` and `BIN_INSTALL_DIR`
      variables. This is reinventing the wheel, as CMake already provide a way
      to do that via `CMAKE_INSTALL_<DIR>` paths, e.g. `CMAKE_INSTALL_LIB`.
      This requires users of libgit2 to know about the discrepancy and will
      require special hacks for any build systems that handle these variables
      in an automated way. One such example is Gentoo Linux, which sets up
      these paths in both the cmake and cmake-utils eclass.
      
      So let's stop doing that: the GNUInstallDirs module handles it in a
      better way for us, especially so as the actual values are dependent on
      CMAKE_INSTALL_PREFIX. This commit removes our own set of variables and
      instead refers users to use the standard ones.
      
      As a second benefit, this commit also fixes our pkgconfig generation to
      use the GNUInstallDirs module. We had a bug there where we ignored the
      CMAKE_INSTALL_PREFIX when configuring the libdir and includedir keys, so
      if libdir was set to "lib64", then libdir would be an invalid path. With
      GNUInstallDirs, we can now use `CMAKE_INSTALL_FULL_LIBDIR`, which
      handles the prefix for us.
      Patrick Steinhardt committed
  4. 23 Feb, 2020 1 commit
  5. 19 Feb, 2020 1 commit
  6. 30 Jan, 2020 1 commit
  7. 15 Sep, 2019 1 commit
  8. 20 Jun, 2019 1 commit
  9. 24 May, 2019 1 commit
  10. 05 Mar, 2019 1 commit
  11. 13 Feb, 2019 1 commit
  12. 12 Feb, 2019 1 commit
  13. 28 Jan, 2019 1 commit
  14. 17 Jan, 2019 1 commit
    • Use cdecl calling conventions on Win32 · a74dd39b
      The recommendation from engineers within Microsoft is that libraries
      should have a calling convention specified in the public API, and that
      calling convention should be cdecl unless there are strong reasons to
      use a different calling convention.
      
      We previously offered end-users the choice between cdecl and stdcall
      calling conventions.  We did this for presumed wider compatibility: most
      Windows applications will use cdecl, but C# and PInvoke default to
      stdcall for WINAPI compatibility.  (On Windows, the standard library
      functions are are stdcall so PInvoke also defaults to stdcall.)
      
      However, C# and PInvoke can easily call cdecl APIs by specifying an
      annotation.
      
      Thus, we will explicitly declare ourselves cdecl and remove the option
      to build as stdcall.
      Edward Thomson committed
  15. 22 Sep, 2018 2 commits
  16. 18 Sep, 2018 2 commits
  17. 03 Sep, 2018 1 commit
  18. 09 Aug, 2018 1 commit
  19. 02 Aug, 2018 1 commit
  20. 30 May, 2018 4 commits
  21. 29 Jan, 2018 1 commit
  22. 24 Nov, 2017 6 commits
  23. 09 Sep, 2017 1 commit
  24. 11 May, 2017 1 commit
  25. 11 Apr, 2017 1 commit
  26. 05 Mar, 2017 1 commit
  27. 19 Dec, 2016 2 commits
  28. 29 Aug, 2016 1 commit
  29. 20 Jun, 2016 1 commit