Skip to content
Snippets Groups Projects
  1. Feb 08, 2020
  2. Feb 07, 2020
  3. Feb 01, 2020
  4. Dec 20, 2019
  5. Dec 06, 2019
  6. Dec 04, 2019
  7. Dec 02, 2019
  8. Nov 27, 2019
  9. Oct 18, 2019
  10. Oct 06, 2019
  11. Oct 01, 2019
  12. Sep 28, 2019
    • Isabella Muerte's avatar
      :sparkles: Update CMake to modern approach · 1c5a0bb3
      Isabella Muerte authored
      New Features:
      
      pugixml-shared and pugixml-static are "always" available, but not always
      built. This allows downstream projects to still use them, and to make
      sure our configurations are correct regardless of if they are being
      built. They are not always installed however.
      
      pugixml-shared and pugixml-static have ALIAS libraries of
      pugixml::shared and pugixml::static respectively. These names are also
      respected in the `find_package(pugixml CONFIG)` generated files, so its
      safe to use pugixml in a CMake project regardless of whether it is
      installed locally, or if its a subproject via `add_subdirectory`.
      
      pugixml will automatically select the correct library type based on
      BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available.
      
      CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported.
      
      CMake will now rely on generator expressions (a powerful abstraction in
      large projects with many subdirectories) for most work. This offloads
      work from the single-threaded configure stage to the multithreaded
      generation stage.
      
      pugixml now uses CTest as the runner.
      
      Some settings are automatically disabled if pugixml is used as a
      subdirectory. These are still able to be manually set, but are hidden
      from folks who choose to use CMake GUI.
      1c5a0bb3
    • Isabella Muerte's avatar
      :construction: Begin moving pugixml to modern(ish) CMake · 195dfe1d
      Isabella Muerte authored
      :arrow_up: Bump CMake minimum to 3.4
      :bug: pugixml no longer requires a C compiler to be found or set to
      compile correctly. This speeds up configuration and building on windows.
      :construction: Begin laying groundwork to backport MSVC_RUNTIME_LIBRARY
      property
      195dfe1d
  13. Sep 22, 2019
  14. Sep 21, 2019
    • Arseny Kapoulkine's avatar
      Move pugixml.rc to scripts/ · 6934b123
      Arseny Kapoulkine authored
      This keeps src/ folder clean of auxiliary files only required for
      special builds; note that CMakeLists.txt already depends on scripts/
      (specifically for pkgconfig setup).
      6934b123
  15. Sep 19, 2019
  16. Sep 18, 2019
  17. Sep 16, 2019
  18. Sep 12, 2019
  19. Sep 09, 2019
    • Joel Andres Granados's avatar
      Update nuget creation to VS2019 (#291) · 84e32273
      Joel Andres Granados authored
      Create visual studio projects that are vs2019 compliant.
      * nuget_build.ps1 :
      Introduce a new argument that will define how we implement the nuget
      build. For now we accept 201{9,7.5.3} as possible argument values.
      
      * pugixml_vs2019{,_static}.vcxproj :
      Add two visual studio projects that build pugi with the latest SDK and
      build tools
      
      * appveyor.yml
      - Add Visual Studio 2019 to build targets
      - Add Visual Studio 201{9,3,5} to build_scripts. And call
        nuget_build.ps1 with a new argument.
      - Add Visual Studio 2019 to the test_scripts.
      84e32273
  20. Aug 21, 2019
  21. Aug 04, 2019
    • Matan Nassau's avatar
      fix cmake option USE_POSTFIX (#283) · 4f6e7454
      Matan Nassau authored
      appending the suffix to the build product need not be a function of
      whether CMAKE_CONFIGURATION_TYPES is set.  for example, having two ninja
      build trees---one for debug and another for release---is a fine use-case
      for USE_POSTFIX.
      4f6e7454
  22. Jul 26, 2019
  23. Jun 19, 2019
  24. Jun 09, 2019
Loading