From a7c4070df74e4d62cc8031ae5de9f892fe914bfc Mon Sep 17 00:00:00 2001 From: Arseny Kapoulkine Date: Sun, 18 Jun 2017 23:41:12 -0700 Subject: scripts: Switch to manual NuGet package with both CRT linkages 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. --- scripts/nuget/build/native/pugixml.targets | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 scripts/nuget/build/native/pugixml.targets (limited to 'scripts/nuget/build/native/pugixml.targets') diff --git a/scripts/nuget/build/native/pugixml.targets b/scripts/nuget/build/native/pugixml.targets new file mode 100644 index 0000000..97d13b2 --- /dev/null +++ b/scripts/nuget/build/native/pugixml.targets @@ -0,0 +1,27 @@ + + + + dynamic + + + + + + + $(MSBuildThisFileDirectory)include/;%(AdditionalIncludeDirectories) + + + $(MSBuildThisFileDirectory)include/;%(AdditionalIncludeDirectories) + + + + + $(MSBuildThisFileDirectory)lib/$(Platform)\$(PlatformToolset.Split('_')[0])\$(Linkage-pugixml)\Debug\pugixml.lib;%(AdditionalDependencies) + + + + + $(MSBuildThisFileDirectory)lib/$(Platform)\$(PlatformToolset.Split('_')[0])\$(Linkage-pugixml)\Release\pugixml.lib;%(AdditionalDependencies) + + + -- cgit v1.2.3