Added debug build instructions.#349
Merged
Conversation
Member
|
Thanks! |
Collaborator
|
Gracias amigo! :D |
Collaborator
|
One concern from my corner: I'm hoping to push a pretty large restructure of the build process this afternoon, which will invalidate these particular instructions (down to a simple "npm run build-debug" or such). |
Collaborator
|
Eh, that requires some bigger discussion before it can land. I'm merging this, no way did your readme change cause appveyor to fail. |
maxkorp
added a commit
that referenced
this pull request
Jan 14, 2015
Added debug build instructions.
Collaborator
Author
|
appveyor fails almost every time :(, what's is purpose once we get travis? |
Collaborator
|
It's the only real CI we have for windows. I can't figure out why it dies On Wed, Jan 14, 2015, 2:33 AM Matteo Collina notifications@github.com
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
As discussed in #331.