1. 19 Jul, 2019 1 commit
    • Chun-wei Fan's avatar
      NMake Makefiles: Make gettext-runtime libname configurable · 624d6af3
      Chun-wei Fan authored
      Some people might be linking to gettext-runtime using intl.lib, while
      others might be using libintl.lib (such as vcpkg builds), depending on
      how gettext-runtime was built.  Add LIBINTL_LIB to the configurable
      items, which defaults to intl.lib, in the NMake Makefiles so that we
      can override it if needed in the NMake command line.
      See #485 (comment 556977) for a
      discussion on this.
  2. 03 Jul, 2019 1 commit
  3. 02 Jul, 2019 2 commits
  4. 01 Jul, 2019 5 commits
    • Chun-wei Fan's avatar
      Move config.h.win32.in to win32/ · ad0b367a
      Chun-wei Fan authored
      Make things more consolidated.
    • Chun-wei Fan's avatar
      Build: Drop Visual Studio projects · 0a19d08a
      Chun-wei Fan authored
      Since the NMake Makefiles are in place, we can drop everything that is
      related to the Visual Studio projects, which have been superseded.
    • Chun-wei Fan's avatar
      Visual Studio builds: Add a set of NMake Makefiles · 433088f5
      Chun-wei Fan authored
      This adds a set of NMake Makefiles, which will replace the Visual Studio
      projects, so that we can have a more flexible build setup, and would be
      usable for Visual Studio 2013 and later.
      This also has the advantage to build optional items (such as rsvg-view-3,
      which requires GTK, Introspection, and PangoFT2 support for the test
      programs) on demand in one go, and adds a target 'tests' to build and
      run the test programs in tests/ for librsvg.
      This NMake Makefile set should cover all the build features that are
      handled by the current Visual Studio projects.
      This will also enable the removal of the autotools 'dist hook'
      directives that are being used to generate the complete Visual Studio
      projects, as we are now able to share source listings with the autotools
      build files directly, which will be done in the upcoming commit(s).
    • Chun-wei Fan's avatar
      Visual Studio builds: Transition Rust builds for full NMake · 677b13aa
      Chun-wei Fan authored
      As we are going to integrate win32/rsvg-rust.mak into our NMake
      Makefiles, we need to remove its 'all' target and re-name our 'clean'
    • Chun-wei Fan's avatar
      win32/detectenv-msvc.mak: Detect Visual Studio 2019 · 5dcff598
      Chun-wei Fan authored
      We want to ensure that we can build with Visual Studio 2019 properly.
  5. 03 Apr, 2019 2 commits
  6. 23 Feb, 2018 2 commits
  7. 17 Jan, 2018 1 commit
    • Chun-wei Fan's avatar
      MSVC builds: Fix rsvg-internals.lib (Rust) linking · 0137cdf0
      Chun-wei Fan authored
      Later versions of Rust include the Rust architecture in the output
      directory by default (i.e i686-pc-windows-msvc or
      x86_64-pc-windows-msvc), so we must include that in the output path in
      both the NMake Makefile that is used to call cargo, as well as in the
      rsvg-rust project, so that the librsvg DLL can properly link, and to
      avoid running Cargo again when the Rust portion has been successfully
  8. 20 Oct, 2017 1 commit
  9. 15 Jun, 2017 2 commits
    • Chun-wei Fan's avatar
      win32/rsvg-rust.mak: Streamline Rust build process · facef142
      Chun-wei Fan authored
      As the recommended way to setup Rust is via rustup, set the default
      toolchain/target during the NMake build process, so that one will only
      need to have the Rust executables in their PATH and ensure that they
      have the needed toolchains (i686-pc-windows-msvc and/or
      x86_64-pc-windows-msvc) installed via rustup.
      Please note that we are being conservative here-we use the stable
      releases of the toolchains only.  If using a beta/nightly toolchain
      release, one needs to update this file for this purpose.
    • Chun-wei Fan's avatar
      win32/replace.py: Fix replacing items in files with UTF-8 content · fd1be778
      Chun-wei Fan authored
      Some files that this script will process might have UTF-8 items in
      there, which can cause problems on Python 3.x as it is more strict and
      careful on unicode issues.  Fix this by:
      -Doing what we did before on Python 2.x
      -Opening the file with encoding='utf-8' on Python 3.x
  10. 06 Mar, 2017 1 commit
  11. 03 Mar, 2017 2 commits
  12. 02 Mar, 2017 1 commit
  13. 01 Mar, 2017 1 commit
  14. 23 Feb, 2017 1 commit
    • Chun-wei Fan's avatar
      Visual Studio builds: Move projects to win32/ · 1bfa2d7b
      Chun-wei Fan authored
      Move the projects to win32/ from build/win32/, so that one will need to go down
      one less level down the tree to reach the project files, and will allow the
      autotools modules (Makefile.msvcproj, Makefile-newvs.am,
      Makefile.msvc-introspection) to be in sync with the ones in GLib and G-I master.
      This also makes the support of Visual Studio 2017 complete by allowing it in the
      NMake Makefiles, which is a must for this package since NMake Makefiles are used
      to build the Rust bits on Visual Studio, as well as for introspection builds.