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.

1 files changed, 15 insertions, 0 deletions

diff --git a/scripts/nuget/build/native/pugixml-propertiesui.xml b/scripts/nuget/build/native/pugixml-propertiesui.xml
new file mode 100644
index 0000000..b2e02bb
--- /dev/null
+++ b/scripts/nuget/build/native/pugixml-propertiesui.xml
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="utf-8"?>

+<ProjectSchemaDefinitions xmlns="clr-namespace:Microsoft.Build.Framework.XamlTypes;assembly=Microsoft.Build.Framework">

+  <Rule Name="ReferencedPackages05032e35-86af-4ab2-a3dc-d3e348583165" PageTemplate="tool" DisplayName="Referenced Packages" SwitchPrefix="/" Order="1">

+    <Rule.Categories>

+      <Category Name="pugixml" DisplayName="pugixml" />

+    </Rule.Categories>

+    <Rule.DataSource>

+      <DataSource Persistence="ProjectFile" ItemType="" />

+    </Rule.DataSource>

+    <EnumProperty Name="Linkage-pugixml" DisplayName="Linkage" Description="Which version of the .lib file to link to this library" Category="pugixml">

+      <EnumValue Name="dynamic" DisplayName="dynamic" />

+      <EnumValue Name="static" DisplayName="static" />

+    </EnumProperty>

+  </Rule>

+</ProjectSchemaDefinitions>