-
Notifications
You must be signed in to change notification settings - Fork 14
Experimental Windows support branch #91
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
Labels
Comments
dzhoshkun
added a commit
that referenced
this issue
Apr 15, 2019
dzhoshkun
added a commit
that referenced
this issue
Apr 15, 2019
…ndows-for-91 Epiphan SDK Windows compatibility with Windows for #91
dzhoshkun
added a commit
that referenced
this issue
Apr 16, 2019
…-for-91 Run with Python 3.7 on Windows for #91
This was referenced Apr 16, 2019
dzhoshkun
added a commit
that referenced
this issue
Apr 16, 2019
…-duo-on-windows-for-91 OpenCV-free Epiphan DVI2PCIe Duo support on Windows for #91
This was referenced Apr 16, 2019
This has already been achieved, see https://github.com/gift-surg/GIFT-Grab/tree/experimental-windows But will leave it open to facilitate thought on how this can be managed w.r.t. the stable branch. |
Closing as out of date |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A lot of the work needed for supporting GIFT-Grab (in particular Epiphan DVI2PCIe Duo) has been done as part of #69. However the PRs have been polluted, as a number of compilation issues have had to be fixed on the fly.
Many of those changes can be used when supporting Windows officially in the (hopefully near) future. So possibly a good way forward is to have an experimental Windows support branch (that can be advertised on the documentation). We can cherry-pick changes from the #69 branch, and merge them onto this branch, in well-defined PRs that clearly show the changes. This will allow to document remaining issues, which can then be addressed in an orderly way to pave the way to official Windows support.
The text was updated successfully, but these errors were encountered: