-
Notifications
You must be signed in to change notification settings - Fork 22
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
Windows binaries failure #10
Comments
Happy to help out here. I'm indeed seeing some pretty odd behavior like julia> parse(Dec64, "1")
+0E-398
julia> parse(Dec64, "225")
+0E-398 |
@stevengj, if you have an example build script, I can try working on getting the windows binaries to compile. I'm trying to add this package as an ODBC dependency (for handling SQL numeric/decimal types), so I'm eager to get this resolved. |
we could also ping @tkelman about potentially helping us out here. |
@quinnj, to cross-compile the 64-bit Windows version, I believe I was using However, that directory also includes some |
The good news is that once we get 32- and 64-bit DLLs built for Windows, we probably will not have to touch them again for a long, long time. |
(Or maybe my current binaries are okay, but they are using some alternate calling convention like |
Hmmm, I tried |
Hmm, I'm having a bit of trouble with the command you gave me; it seems like it only wants to generate a |
I'm also getting to the very last step and seeing this error:
|
Bump. I have some more time tonight/tomorrow morning to play around with this. |
The However, you need to build a |
Ah, ok, I'll look into getting the |
|
no, |
The DLLs seem to be working now. |
Unfortunately, the Appveyor tests are indicating that the Windows binaries I generated (via MinGW) aren't correct. Something in my cross-compile build script must be wrong.
The text was updated successfully, but these errors were encountered: