| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
|
|
|
|
|
|
Remove static pivot from NuGet autopkg.
|
|
This pivot seemed to be causing issues because the NuGet package thought it was actually dynamic.
|
|
|
|
|
|
Include more configurations in the Nuget package.
|
|
|
|
|
|
|
|
This avoids linker warning when building the final executable and we don't
have to package the .PDB file.
|
|
|
|
|
|
Move pugixml project file for VS2015 to scripts/ and unify the output file
structure similar to old VS201x projects. Remove test projects and solution
since they are not required for building.
Provide more accurate information in the package script and handle build
errors during package construction properly.
|
|
|
|
|
