-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
building on Windows #328
Comments
Good to know. I'd like to make the build system capable of using MSVC--though I don't really run Windows myself. But having done development in MSYS and cygwin, it much better to be as native as possible. It makes integration with other things under Windows that much easier. |
I gave it a whirl last night using MSVC 2012. Here is a quick progress report, I'm not on windows right now, but I will push some patches when I get the chance.
I'll give it another shot later, either with MSVC 2013, or by defining bool/true/false by hand. In any case if c99 is what we assume for neovim (#161) then MSVC 2013 is the way to go. |
Tested with MSVC 2013, the stdbool.h error is now gone and I'm starting to get into errors related with UNIX types (timeval, uid_t, mode_t) and since most defines are currently hardcoded in config.h.in I don't think we can proceed without porting some functions to use libuv. On a positive note
|
@mahkoh once said we're only supporting MSVC > 2013
|
We can focus on building for mingw later. Closing for now |
@tarruda this issue was also for MSVC. |
Use new Jedi API for keyword checking in goto funcs
Handle window switching around "lwindow"
[ Continuing discussion from issue #287 ]
I can build libuv on MSVC 2013, but not mingw. It seems that libuv only supports building on MSVC, not mingw, and definitely not cygwin: joyent/libuv#845
Using msys2 which bundles the latest mingw-w64:
Similar issue was reported to libuv 8 months ago. In practice, libuv only supports MSVC.
The text was updated successfully, but these errors were encountered: