-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Make 64-to-32 bit conversions explicit when needed (issue #296) #297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make 64-to-32 bit conversions explicit when needed (issue #296) #297
Conversation
Thanks! |
I just noticed that AppVeyor began to fail with this build: (I had assumed AppVeyor was down when I merged this change, but actually I just had to view it in another browser.) And the problem has affected someone else: #300. So I will have to revert this change, unless you have a more complete fix. |
@cdunn2001 - Sorry, I am new to AppVeyor, but I read one of the failed build logs and it looked like there were missing tools? Specifically: https://ci.appveyor.com/project/cdunn2001/jsoncpp/build/build.92/job/i2224pf8kr58y854#L55 says
I am not sure how my changes caused that. Still, if you need to revert, I understand. |
Yeah, maybe we just need the Toolset. |
fix appveyor 32-bit windows build I've backed rebased under #297 because AppVeyor has been failing since there, and because that was not properly based on master anyway.
…ed when needed This is rebased from open-source-parsers#297, where AppVeyor had been failing, and which was not properly based on the master branch.
…ed when needed This is rebased from open-source-parsers#297, where AppVeyor had been failing, and which was not properly based on the master branch.
No description provided.