How was scripts/nuget/build/native/pugixml.targets and pugixml-propertiesui.xml generated? #507
-
|
I want to publish my C++ library to NuGet, but Microsoft only provides documentation for publishing .NET libraries. I want to imitate pugixml's method to publish, but found two strange files under scripts/nuget/build/native, pugixml.targets and pugixml-propertiesui.xml. These two files don't look like they were written manually. May I ask what tools were used to generate them? Or were they really written manually? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
These were generated long time ago by CoApp: http://coapp.org/tutorials/building-a-package.html - however, since then pugixml switched to just keeping these files in the tree and hand-editing them when necessary, due to some issues with CoApp that were too difficult to resolve. |
Beta Was this translation helpful? Give feedback.
-
|
See a7c4070#diff-70995b04466875424f4eac40312188016386df10d7663d409075a54451b0f4f1 for historical reference of what was used before these files were added to the tree. |
Beta Was this translation helpful? Give feedback.
-
I see. Actually I also looked into CoApp, but found that the project has been dead for many years (and so were many documentation links), so I didn't adopt it. I guess now I can only use pugixml as a template to generate my solution … |
Beta Was this translation helpful? Give feedback.
These were generated long time ago by CoApp: http://coapp.org/tutorials/building-a-package.html - however, since then pugixml switched to just keeping these files in the tree and hand-editing them when necessary, due to some issues with CoApp that were too difficult to resolve.