Add msvcr100 to output and to nuget package #45
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This should partially fix issue #32
- Make it cope with paths containing spaces - Replace <authors/> with a NuGet token
Member
Thanks a lot, David. I was a little bit concerned with the manifest and the Eula... :-)
RunBuild.cmd copies the binaries into the Build folder. I suppose that the last time you tried, the folder was existing and was containing the result of a previous build. This has been merged into nulltoken/vNext. |
Contributor
Author
|
What I meant is that when starting clean and running runBuild.cmd, I don't get those files in Build folder. Only file I get is Test-result.xml. |
Member
|
That's indeed very weird. Can you redirect its output to a file and send it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Nothing fancy here; I just did the same thing with msvcr100.dll as we do with git2.dll.
One strange thing though: the nuspec was copying git2.dll from ..\build\git2.dll, but for some reason I'm not getting any files copied in the build folder. So I changed the nuspec to copy from the ..\Lib folder. I'm puzzzled as that was working when I made my previous change. Do you know what's the deal with the Build folder?