1. 21 Feb, 2018 1 commit
  2. 10 Jul, 2017 1 commit
  3. 09 Jan, 2017 3 commits
    • Chun-wei Fan's avatar
      Visual Studio builds: Move project files to win32/ · 6dfc6fee
      Chun-wei Fan authored
      It was suggested that the project files be moved here as we don't actually
      need to go two directory layers from $(srcroot), and would help us to
      standardize on things in the future across the board.
      6dfc6fee
    • Chun-wei Fan's avatar
      Makefile.msvcproj: Document further · b14b09c8
      Chun-wei Fan authored
      Mention that the *.headers are needed only if headers need to be installed
      with the project/module after the build.  Also, use a generic "YourProject"
      rather than the "gdk-4" project file name--I missed changing the name in the
      process.
      b14b09c8
    • Chun-wei Fan's avatar
      Makefile.msvcproj: Document things a bit better · 7d26e9ef
      Chun-wei Fan authored
      If Visual Studio 2013 or later is required, let people know how this
      autotools module should be used.
      7d26e9ef
  4. 20 Dec, 2016 1 commit
    • Chun-wei Fan's avatar
      build/Makefile.msvcproj: Fix cleanup · c5754bdc
      Chun-wei Fan authored
      When we make Visual Studio 2013 the baseline Visual Studio version, we need to
      the *.vs12.sourcefiles that are generated along the way so that 'make distcheck'
      won't complain about the leftover files.  This was not caught in GLib as we do
      not yet require Visual Studio 2013, but we update this here as this module is
      intended to be used in projects that support Visual Studio project builds.
      c5754bdc
  5. 23 Nov, 2016 1 commit
  6. 01 Nov, 2016 2 commits
    • Chun-wei Fan's avatar
      build/Makefile-newvs.am: Do not hardcode the baseline MSVC version · acd07cfc
      Chun-wei Fan authored
      This is to allow specification of the baseline Visual Studio 201x version as
      the baseline version may not be 2010 anymore as we begin to require C99
      features that will require Visual Studio 2013 or later.
      acd07cfc
    • Chun-wei Fan's avatar
      build/Makefile.msvcproj: Add rules for MSVC 2013 to be the baseline version · 1f33b36c
      Chun-wei Fan authored
      We are starting to require C99 features that can only be supported in
      Visual Studio 2013 and later, so we need to prepare rules for Visual Studio
      2013 to be our baseline version for Visual Studio builds, so that we can
      move the templates from Visual Studio 2010 to Visual Studio 2013.
      
      As this strives to be a shared autotools module between projects, there is
      duplication at this point, though, because we still want to support
      2008~2012 for projects that do not yet require the C99 features and depends
      on GLib-2.50.x/GTK+-3.22.x or earlier.
      1f33b36c
  7. 19 Oct, 2016 2 commits
    • Chun-wei Fan's avatar
      build/win32/vs10/Makefile.am: Delete glib-install.props's on re-generation · c718bf88
      Chun-wei Fan authored
      This is to ensure the changes that is applied to glib-install.props here is
      applied to the projects files in build/win32/vs[11|12|14] as well.
      c718bf88
    • Chun-wei Fan's avatar
      build/: Force MSVC project file generation on Makefile.am changes · 70040b40
      Chun-wei Fan authored
      Make the Makefile.am targets for generating the Visual Studio projects re-generate the
      project files and the header listings whenever the Makefile.am's that include
      build/Makefile.msvcproj changes, so that whenever a source/header is added, they will
      be reflected in the projects and in the property sheets that are used to copy the
      headers.
      
      Also ensure that these are applied to the vs11, vs12 and vs14 projects when this
      happens, as they are copied and processed from the Visual Studio 2010 projects.
      70040b40
  8. 20 Sep, 2016 1 commit
  9. 18 Jul, 2016 1 commit
  10. 20 Jun, 2016 1 commit
  11. 15 Jun, 2016 3 commits
  12. 21 Apr, 2016 1 commit
    • Chun-wei Fan's avatar
      build/win32/pc_base.py: Allow custom options · bd0911af
      Chun-wei Fan authored
      Some packages might have some parts that are built for certain build
      configs, meaning that they could have .pc files of their own, such as
      Pango, where PangoFT2 is optionally built.  Allow such an option if
      needed.
      
      Also remove some trailing whitespaces.
      bd0911af
  13. 11 Mar, 2016 1 commit
  14. 10 Mar, 2016 1 commit
    • Chun-wei Fan's avatar
      MSVC builds: Add scripts to generate .pc files · 374a61f2
      Chun-wei Fan authored
      Add a generic script, pc_base.py, which can be utilized to obtain path
      info, along with user-input version info, which can be used to generate
      pkg-config .pc files.  Also enhance replace.py a bit so that it can also
      be used in the future to replace multiple items in a file in one shot.
      This is done to make building introspection files easier, as it depends
      much on the pkg-config .pc files to work.
      
      Update the project files so that when Python is available, we can generate
      the full, usable .pc files when we complete and 'install' the builds, and
      copy them to appropriate locations so that pkg-config can be set to find
      them easily.
      374a61f2
  15. 25 Feb, 2016 1 commit
    • Chun-wei Fan's avatar
      Visual Studio builds: Move @GLIB_VERSION@ usage · 99b30f38
      Chun-wei Fan authored
      ... from glib-gen-srcs.[vsprops|props].in to
      glib-version-paths.[vsprops|props].in, and instead let autotools generate
      glib-version-paths.[vsprops|props] rather than
      glib-gen-srcs.[vsprops|props], as this will need to be referenced for
      other items as well, namely generating the .pc files which will become
      useful for introspection builds.
      99b30f38
  16. 20 Jan, 2016 1 commit
  17. 18 Jan, 2016 1 commit
    • Chun-wei Fan's avatar
      Visual Studio builds: Rearrange build configs · e3ab6ab3
      Chun-wei Fan authored
      This is a follow-up commit for commit 82c2461e, where the default build is
      to use the PCRE that is installed in the system, if it is available and is
      not overridden with --with-internal-pcre.
      
      For Visual Studio builds, this means that the new 'Debug' and 'Release'
      configs will now use PCRE that is found on the system, which were renamed
      from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE'
      and 'Release_BundledPCRE' configs which make use of the PCRE that is
      supplied with the GLib sources, which, replaces the former 'Debug' and
      'Release' configs.
      e3ab6ab3
  18. 02 Dec, 2015 1 commit
    • Chun-wei Fan's avatar
      build/win32: Add NMake Makefile module for building tests and introspection · 244f9e66
      Chun-wei Fan authored
      This adds a NMake Makefile module that can be used for building tests and
      introspection using, NMake.  This is not yet distributed in the main GLib
      tarballs, but this is placed here as the base location as this is
      intended to be used in projects that support Visual Studio builds and
      support the build of tests and/or introspection under Visual Studio using
      NMake.
      244f9e66
  19. 12 Nov, 2015 1 commit
    • Chun-wei Fan's avatar
      MSVC 2010+ builds: Do not explicitly use /LTCG · c50bb218
      Chun-wei Fan authored
      This partially reverts dc4361f4.
      
      As we now ensure that items using GResources and GConstructors are always
      referenced so that the linker does not optimize them out in a default
      Release build, we no longer need to enforce the use of /LTCG, so
      /LTCG:incremental will work as well.
      c50bb218
  20. 23 Oct, 2015 1 commit
  21. 13 Oct, 2015 1 commit
    • Chun-wei Fan's avatar
      MSVC 2010+ builds: Explicitly use /LTCG · dc4361f4
      Chun-wei Fan authored
      The Visual Studio projects used a default setting for link-time code
      generation, which is a part of the various linker optimizations that is
      available, which is set as /LTCG for Visual Studio 2013 and earlier.
      
      This changed in Visual Studio 2015 to become /LTCG:incremental, which would
      cause GResources-generated code to be optimized out during linking, unless
      they were referred to directly in the main line code (such as when the
      GResource is manually registered), causing programs to crash as a result as
      they can't find the needed code/data at run time.
      
      Fix this by explicitly setting /LTCG for all release builds, for Visual
      Studio 2010 and later.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=752837
      dc4361f4
  22. 12 Oct, 2015 2 commits
  23. 25 Sep, 2015 3 commits
  24. 23 Sep, 2015 1 commit
    • Chun-wei Fan's avatar
      build/win32: Make "Install" Property Sheet Generation More Robust · aef2d0c5
      Chun-wei Fan authored
      List the files that are generated in the process to generate the
      glib-install property sheets, so that we can use that list as a
      depedency, as well as deleting those files in one shot after the
      property sheet is generated, so we don't need to worry about those
      in 'make distclean' or so.
      aef2d0c5
  25. 17 Sep, 2015 1 commit
  26. 09 Sep, 2015 2 commits
    • Chun-wei Fan's avatar
      MSVC Builds: "Add" MSVC 2015 Projects · 4025b5a5
      Chun-wei Fan authored
      This "adds" the Visual Studio 2015 Project files by doing what we did
      before: copying the Visual Studio 2010 projects and replacing items
      in them, as the formats of the Visual Studio 201x projects are largely
      the same.
      4025b5a5
    • Chun-wei Fan's avatar
      MSVC Builds: Simplify Script to Generate glib-mkenums · 9c7df09c
      Chun-wei Fan authored
      Use a simple all-purpose utility script to generate the glib-mkenums
      PERL script with the version info, and stop using the script that
      tries to parse the autotools files.  Move the things that
      were taken out from build/win32/setup.py back there.
      9c7df09c
  27. 08 Sep, 2015 1 commit
    • Chun-wei Fan's avatar
      MSVC Builds: Prepare For Visual Studio 2015 · 0be6766d
      Chun-wei Fan authored
      Update the autotools module so that we can use it to upgrade the
      Visual Studio 2010 projects to become Visual Studio 2015-compatible.
      
      Note that this will make the MSVC 2015 builds use the the the latest
      VC140 CRT.
      0be6766d
  28. 03 Sep, 2015 3 commits