aboutsummaryrefslogtreecommitdiff
path: root/scripts
AgeCommit message (Collapse)AuthorFilesLines
2024-03-22Update pugixml.pc.inMiloš Komarčević1-2/+2
2024-01-26Update year to 2024 everywhereArseny Kapoulkine2-2/+2
... except .html files that will be regenerated later.
2023-09-07Update version to 1.14 everywherev1.14latestArseny Kapoulkine3-4/+4
2023-09-06Update copyright year (2022 => 2023)Arseny Kapoulkine2-2/+2
2022-10-20Update version number in preparation for 1.13Arseny Kapoulkine3-4/+4
2022-02-08Update copyright year to 2022Arseny Kapoulkine2-2/+2
2022-02-08Update version to 1.12Arseny Kapoulkine3-4/+4
2022-01-21Fix path.tobias2-16/+16
2022-01-21Add support for Visual Studio 2022 with Platform Toolset v143.tobias4-2/+354
2021-05-06fix cygwin compilationRosen Penev1-1/+1
2020-12-22Don't define pugixml import target if it already existsArseny Kapoulkine1-1/+1
This fixes duplicate target definition errors when find_package(pugixml) is called twice in a build. Fixes #393.
2020-12-18Fix compatibility issue with CMake 3.10Arseny Kapoulkine1-1/+2
target_link_libraries/INTERFACE doesn't seem to work on CMake 3.10, but directly setting the property does work. Fixes #390.
2020-12-10cmake: avoid ALIAS targetBen Boeckel1-1/+2
This is not allowed on IMPORTED targets.
2020-12-02cmake: provide a compatibility target for usersBen Boeckel1-0/+7
For users using older pugixml releases, add an ALIAS target which works with the new versions too.
2020-11-26scripts: Convert archive.py to Python 3v1.11Arseny Kapoulkine1-6/+6
The changes are mostly mechanically converting str to bytes.
2020-11-26scripts: Remove deprecated iconUrl from NuGet packageArseny Kapoulkine1-1/+0
The logo.svg link is dead anyway.
2020-11-26Update copyright year to 2020 everywhereArseny Kapoulkine2-2/+2
2020-11-25Update version to 1.11 and update documentationArseny Kapoulkine3-4/+4
2020-10-26Added fix to pugixml_dll.rc so shared lib can be built with MinGWJames McCollum1-1/+1
2020-07-15Fix debug postfix in pkgconfig fileWolfgang Stöggl1-1/+1
In case of USE_POSTFIX, the POSTFIX is dependent on the CMAKE_BUILD_TYPE. Use the correct POSTFIX also in the generated pugixml.pc file. This results in the following contents of pugixml.pc: - Release: Libs: -L${libdir} -lpugixml - RelWithDebInfo Libs: -L${libdir} -lpugixml_r - MinSizeRel: Libs: -L${libdir} -lpugixml_m - Debug: Libs: -L${libdir} -lpugixml_d
2020-04-24Add "Include pugixml.cpp" and "Header Only" linkage optionsrip.nsk3-9/+13
2019-09-30Update `check` command to output text on failureIsabella Muerte1-0/+3
Move pugixml-config.cmake.in to scripts/ to prevent polluting the root
2019-09-21Move pugixml.rc to scripts/Arseny Kapoulkine1-0/+45
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).
2019-09-15scripts: Update NuGet package specArseny Kapoulkine1-2/+2
Migrate from licenseUrl to license since licenseUrl is deprecated and fix grammar for VS version list.
2019-09-11Update version to 1.10Arseny Kapoulkine2-2/+2
Note: this chang also updates PUGIXML_VERSION macro to allow for double-digit minor versions; this preserves the continuity of versions so PUGIXML_VERSION >= 190 will still work.
2019-09-09Update nuget creation to VS2019 (#291)Joel Andres Granados4-7/+372
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.
2019-03-13Remove contrib folderArseny Kapoulkine2-0/+583
This change removes contrib folder since it doesn't seem very useful; Natvis scripts can and should go to scripts/ along with project files. foreach.hpp is supporting a severely outdated BOOST_FOREACH construct; in C++11 ranged for loop can be used with xml_node::children/attributes, and BOOST_FOREACH can work with these as well. foreach.hpp was also accidentally licensed as public domain which isn't very helpful when the actual library is MIT. We could fix the license but it seems better to just remove it. Fixes #264.
2019-01-01Happy New Year!Arseny Kapoulkine1-1/+1
2018-12-10pkg-config: Use CMake GnuInstallDirs FULL varsMillian Poquet1-2/+2
Fixes an installation problem in Nix packages, as non-FULL variables are already absolute paths in this case.
2018-11-12Update all URLs to pugixml.org to https://Arseny Kapoulkine2-4/+4
2018-11-12Update URL to https in pugixml.pc.inWolfgang Stöggl1-1/+1
2018-07-22scripts: Set file permissions when building .zip archiveArseny Kapoulkine1-0/+1
It looks like zipfile module by default uses the permission mask 0, which after unpacking on Unix-based systems leads to the files being inaccessible. We now explicitly set file mask to rw-r--r-- to match .tar.gz defaults. Fixes #217.
2018-06-26Use CMAKE_INSTALL_LIBDIR for pugixml.pc (#215)Wolfgang Stöggl1-1/+1
- Up to now, the libdir was hardcoded to "lib" inside pugixml.pc and the install directory of pugixml.pc was "lib/pkgconfig" - Adds support for lib and lib64 by using CMAKE_INSTALL_LIBDIR variable
2018-06-20fix cmake warning "Policy CMP0048 is not set" (#214)Bernd Amend1-1/+1
This also bumps the minimum CMake version to 3.0 (from 2.8.12).
2018-04-12scripts: Use LICENSE file in pugixml.podspecArseny Kapoulkine1-24/+1
We no longer need to specify the license boilerplate verbatim since we have a separate file.
2018-04-09cmake: always install the pkg-config file (#193)Eli Schwartz1-3/+3
There's really never a reason to *not* want this installed. If an option is needed to specify installing in a versioned subdirectory, this option should be explicitly described rather than hidden in something else. As an added bonus, this makes the CMake install code slightly *less* complicated.
2018-04-02Update version to 1.9Arseny Kapoulkine2-2/+2
2018-01-07Update all copyright notices to specify year 2018Arseny Kapoulkine2-2/+2
2017-08-20scripts: Fix NuGet VS2017 buildArseny Kapoulkine1-2/+2
Due to a typo in build script v141 binaries were built using VS2015 instead of VS2017. Fixes #157.
2017-08-18scripts: Disable LTCG for VS2017Arseny Kapoulkine2-5/+5
Using LTCG restricts the resulting .lib files to a specific compiler version, causing version conflicts when the compiler gets updated without changing the toolset version. VS2017 now has two incompatible compilers, 15.0 and 15.3, both of which use toolset v141...
2017-06-20scripts: Refactor nuget_build.ps1Arseny Kapoulkine5-128/+92
Unify build paths in all MSBuild VS projects and extract common build logic into functions. Note that this change changes both VS2010 and VS2013 projects to have more predictable output paths and fixed output file name (pugixml).
2017-06-20scripts: Clarify the linkage settings in package descriptionArseny Kapoulkine2-5/+6
Also improve linkage description
2017-06-20scripts: Switch to manual NuGet package with both CRT linkagesArseny Kapoulkine7-49/+476
We'd like to build pugixml with both static & dynamic CRT and put it all in one NuGet package. CoApp sort of allows us to do this via dynamic/static pivots, but it does not let us customize the names of the pivots and additionally has some bugs with the project setup. Their project modifications are also much more complicated - really, at this point we should do this ourselves. Create a simple native NuGet package with Linkage setting that picks the right library, and package all libraries appropriately. Note that we use the unified path syntax to make it simple to just get the right .lib file from the toolset/platform/configuration/linkage combo.
2017-06-18scripts: Cleanup nuget_build.ps1Arseny Kapoulkine1-26/+18
Correctly check for error codes and don't run .bat file since it doesn't work anyway (the variables it sets aren't accessible in PowerShell, and the path to the script doesn't seem to be the same in VS2017).
2017-06-15use powershell instead of cmdIvan Gagis2-17/+33
2017-06-15Appveyor image set to VS2017Ivan Gagis1-2/+1
2017-06-15set v141 tools environment for buildingIvan Gagis1-0/+1
2017-06-15VS2017 projectIvan Gagis3-1/+181
2017-01-26Update copyright year to 2017Arseny Kapoulkine2-2/+2
2016-11-28scripts: Make archive build reproducibleArseny Kapoulkine1-12/+17
We used to use the current timestamp when building the archive; switch to using the timestamp of the tag with the version we're packaging. This requires some monkey patching since tarfile module is always using current timestamp when writing gzip header... Also exclude archive.py from archive and simplify release file list in Makefile.
generated by cgit v1.1 at 2024-07-17 02:58:56 +0000