Open
Conversation
Owner
|
Hi @vespakoen, Please go a head and add necessary changes. -Ayb |
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
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.
Hey hey!
I have been trying to make prebuilds of either
node-iohookor theiohookpackage.It's been rough so far =)
However, I at least got it to start compiling something, and producing actual compilation errors that hopefully lead us to a solution soon.
Here is the failing build: https://ci.appveyor.com/project/vespakoen/node-iohook/build/3/job/1l0gc19lrpw11vwj
And here are the relevant errors:
Compiling
iohookwith the settings in this pull, yields something like this: https://ci.appveyor.com/project/vespakoen/iohook/build/job/i06vnvm59na05k0dI know I am getting closer, but this is literally the first time I am compiling C++ on Windows, so I don't really know what I am doing ;)
It would also be great if you can shed some light on the reason for there being 2 packages trying to achieve the same thing, I guess one of you simply didn't notice the other package was around?
I hope this helps!