-
Notifications
You must be signed in to change notification settings - Fork 4
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 support? #2
Comments
Hello, i haven't tried to compile Xenodon on Windows yet, and i don't have much experience with visual studio. I usually either use MSYS2 or WSL. That said, the code without the xorg/direct backend should be portable enough to get it running. I will try to get a VM spinning and see if i can compile it with VS. For the record, there is nothing limiting interactive usage on Windows, it's just not implemented. GLFW would seem like the best option to do so because of its cross-platform support, but i opted for using X.org because GLFW does not support creating multiple windows on different GPUs. Currently i have no plans to implement it due to time constraints on my thesis, even though it shouldn't be much work. |
I was not able to get it working, i couldn't get meson to generate a vs project. A friend who i asked to try to compile it on windows with msys reported a few compile errors: notably, on windows std::filesystem::path seems to be a wrapper around std::wstring, instead of std::string, which doesnt work with .c_str() i used to pass it to libtiff. Also it doesnt work with {fmt}, which results in a bunch of template errors. Could those be the same as what you are getting? |
Hi, source changes:
also trying to avoid template issues:
|
Hi,
after testing on Linux would like to know how hard to build on Windows..
headless of course..
I changed meson options:
option('present-direct', type: 'feature', value: 'disabled')
option('present-xorg', type: 'feature', value: 'disabled')
and little more of meson buid and I'm able to generate VS project files..
but seems even VS2019 has issues with C++17 templates even changing standard to c++latest..
thanks..
The text was updated successfully, but these errors were encountered: