-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Add Windows support #38
Comments
@pkorotkov Thanks for adding the bug report. LMDB has the Windows mmap calls in there but I decided to forgo Windows support for the v0.1.0 release. It shouldn't be hard to add though since the syscalls are fairly isolated but I want to make sure the Bolt design is solid first. I also need to find a good Windows CI that I can run continuous tests against. Do you know of any? |
@benbjohnson Oh, cool! I wish you push the support somewhat quicker :) Well, our in-company Windows (along with Linux) CI is made on drone.io. We didn't even seek for Windows-only solution in the wild. Just created a few instances with Lin-n-Win (with Windows 7 X86_64) and coupled them with the drone.io service. That's it. Perhaps there is a better way but we are still fine with that one. |
Any movement on this? Bolt looks like the nicest Go KV store, but dropping Windows support by using is not always an option. :/ |
@calmh I tried adding in Windows support this morning to this branch but I'm hitting an error on the file mapping. I'm not entirely sure why. It's been a while since I've even booted my Windows VM so I'm a little rusty. Here's the error:
And the full stack trace from the test:
I don't have any more time this morning to commit to this. If you have any ideas, let me know. Some of the mmap code is borrowed from @edsrzf's mmap-go and merged with LMDB's Windows mapping code. I'll try to take another look tomorrow. |
Support for Windows added: #191 |
I landed the Windows Support PR this morning. You should be good to go. :) |
Awesome! 👍 |
Hello,
Thanks for a great project, I'm really happy that I encountered it lately.
Do you have plans to add Windows to the list of supported OSes? Correct me if I'm wrong, currently the only sticking point to port bolt is a bit tricky memory-mapping mechanism in Windows not given out of the box (standard Go syscall library). Well, if that's the case, a proper implementation of _syscall interface for Windows might not be a problem. Here you'll find a working package for handy dealing with memory-mapped files in a portable way.
Best regards,
Pavel
The text was updated successfully, but these errors were encountered: