-
Notifications
You must be signed in to change notification settings - Fork 31
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
compiling using msvc #27
Comments
I would try: But that wasn't enough for vs2008. Still need stdint.h. |
lz4 fails to build on Windows on Travis:
If this library is still maintained it's easy to add AppVeyor configuration to run lz4 tests on Windows to prevent issues like this. |
rutsky
added a commit
to rutsky/buildbot
that referenced
this issue
Apr 12, 2016
Currently LZ4 fails to build on Windows: steeve/python-lz4#27
tardyp
pushed a commit
to buildbot/buildbot
that referenced
this issue
Apr 12, 2016
Currently LZ4 fails to build on Windows: steeve/python-lz4#27
This was referenced Jan 22, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For compiling with MSVC on win32, you have to remove the extra_compile_args, or better still replace it with one suited for MSVC like this one:
More information on those flags can be found here:
http://msdn.microsoft.com/en-us/library/fwkeyyhe.aspx
(not sure how you would go about detecting which compiler is going to be used by distutils - I guess checking for environment variables like VCINSTALLDIR is a good bet? or maybe checking if CL.exe is on the PATH but GCC isn't?)
The text was updated successfully, but these errors were encountered: