1. 24 Oct, 2018 3 commits
    • Federico Mena Quintero's avatar
      (#359): Require rust 1.27 · a3254d7e
      Federico Mena Quintero authored
      The libm crate, as used by nalgebra's dependency on alga, doesn't work
      on rust 1.26.
      
      I have no idea why libm is actually being compiled by alga; AFAIK libm
      is for microcontrollers that need software floating-point.
      
      Fixes GNOME/librsvg#359
      a3254d7e
    • Federico Mena Quintero's avatar
      26edb54f
    • Antonio Ospite's avatar
      (#365): rsvg-convert: Specify pixel dimensiosn for SVG output · ff36118b
      Antonio Ospite authored
      The RsvgDimensionData structure uses pixels as unit for drawing
      dimensions (see librsvg/rsvg.h), but the default unit for SVG documents
      in cairo is pt; thus, when exporting to SVG with rsvg-convert, the
      output drawing results scaled up compared to the original one.
      
      Since rsvg already converted input units to pixels, it's safe to assume
      the SVG output is always in pixels, so set the SVG surface units to
      pixels to keep the original dimensions.
      
      Bump cairo dependency to 1.5.12 as cairo_svg_surface_set_document_unit()
      was not available before that version.
      
      Fixes GNOME/librsvg#365
      ff36118b
  2. 28 Aug, 2018 1 commit
  3. 23 Aug, 2018 1 commit
  4. 07 Aug, 2018 2 commits
  5. 31 Jul, 2018 1 commit
  6. 27 Jun, 2018 1 commit
  7. 22 Jun, 2018 1 commit
  8. 12 Jun, 2018 2 commits
  9. 02 Jun, 2018 1 commit
    • Fabrice Fontaine's avatar
      Add RUST_TARGET variable · f0b76ab6
      Fabrice Fontaine authored
      Add RUST_TARGET environment variable through AC_ARG_VAR to allow the
      user to override the rust target name. Indeed, using $host when
      cross-compiling is not always the good option especially when vendor
      part of target is not set to unknown but to another value such as
      buildroot.
      Indeed, in this case aarch64-buildroot-linux-gnu won't be recognised as
      a valid target by rust/cargo.
      Signed-off-by: Fabrice Fontaine's avatarFabrice Fontaine <fontaine.fabrice@gmail.com>
      f0b76ab6
  10. 31 Mar, 2018 1 commit
  11. 17 Mar, 2018 1 commit
  12. 16 Mar, 2018 1 commit
  13. 27 Feb, 2018 2 commits
  14. 26 Feb, 2018 1 commit
    • Brion Vibber (personal)'s avatar
      Auto-detect -Bsymbolic, fixes configure on macOS · b99891e3
      Brion Vibber (personal) authored
      The -Bsymbolic linker option is ELF-specific, and was breaking
      configure on macOS unless --disable-Bsymbolic was explicitly passed.
      
      Switching the behavior from requiring -Bsymbolic to be available
      by default to just warning and continuing on without.
      
      Fixes #211
      b99891e3
  15. 23 Feb, 2018 3 commits
  16. 22 Feb, 2018 1 commit
  17. 19 Feb, 2018 1 commit
  18. 16 Feb, 2018 1 commit
  19. 13 Feb, 2018 1 commit
  20. 08 Feb, 2018 1 commit
  21. 02 Feb, 2018 1 commit
  22. 23 Jan, 2018 1 commit
  23. 12 Jan, 2018 1 commit
  24. 08 Jan, 2018 1 commit
  25. 14 Dec, 2017 1 commit
  26. 08 Dec, 2017 1 commit
  27. 06 Dec, 2017 1 commit
  28. 30 Nov, 2017 1 commit
  29. 16 Nov, 2017 1 commit
    • David Michael's avatar
      Support cross-compiling with Rust · fd9541ad
      David Michael authored
      The primary change here is to add the --target=$(host) option to
      the cargo build command, so the Rust components are compiled for
      the target host system specified by the configure command.  The
      cargo target subdirectory also needed to be prefixed with the host
      triplet for cross-compiling.
      
      Some of the crates' build scripts require cross-pkg-config settings
      in the environment, so they are set for the cargo build command.
      
      It's worth noting that Rust targets are limited to built-in values
      by default, so the --host value given to configure may not be
      supported.  Built in targets can be found by listing the directory
      src/librustc_back/target in the rustc source.  When building with
      an unsupported target, the user will have to write a target JSON
      definition file and set the environment variable RUST_TARGET_PATH
      to its directory (as with building any Rust project).
      
      This also sneaks in prefixing the Rust library recipe line with a
      "+" character to pass the GNU Make jobserver environment and file
      descriptors, which cargo supports to act as a jobserver client.
      fd9541ad
  30. 03 Oct, 2017 1 commit
  31. 02 Sep, 2017 1 commit
  32. 09 Aug, 2017 1 commit
    • Chun-wei Fan's avatar
      build: Check for PangoFT2/FontConfig availability · 46c8688a
      Chun-wei Fan authored
      On Windows the GTK+ stack does not hard depend on PangoFT2 (thus
      Fontconfig--GTK+ uses PangoWin32 to do the Font discovery and
      configuration stuff by default, unless one uses an envvar to force
      PangoFT2 usage), unlike *NIX platforms, so we need to check for
      it by doing:
      
      -On Windows, enable the test code that uses PangoFT2/FontConfig if
       PangoFT2 and FontConfig is found during configure.  On Visual Studio
       builds, this is set to be disabled in config.h.win32(.in), and can be
       manually enabled by uncommenting #define HAVE_PANGOFT2 1 in
       config.h.win32 prior to the build (or rebuild).  This continues to have
       FontConfig and PangoFT2 to act as an optional dependency.
      
      -On non-Windows platforms, make PangoFT2 and FontConfig a hard dependency,
       which is what the current code assumes.
      
      We might probably need to make the custom TTF load via PangoWin32 and/or
      the native Windows API to run the tests when PangoFT2 and FontConfig are
      not found on Windows.
      
      Also bump the Pango dependency to 1.38 as the test code uses API that is
      introduced in 1.38.x.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=779405
      46c8688a
  33. 07 Aug, 2017 1 commit