-
Notifications
You must be signed in to change notification settings - Fork 62
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
Provide Windows build #106
Comments
Sure go ahead, but I don't have any windows environment or whatsoever to test on nor plan to do so & with virtualized env you can use the unix version as well. |
I got Fpocket working on Windows. But didn't managed to get "molfile" plugins working, so It was a cross-compilation from Fedora Linux 39, the required modifications were:
|
On my proof of concept, it works well on my machine . But before introducing proper Windows support, I have to refactor the Makefile so it doesn't grow bad. At my fork's master all testes are passing. Added explicit casts, multiplatform mkdir, conditional chmod, and much saner Makefile and Dockerfile. Next steps are
Best regards |
I updated to latest molfile plugin but it doesn't has the I ran tested the WIN64 build and it worked after setting the TMPDIR environment variable. But tests didn't passed because there are some differences on the The refactored Makefile dosn't support Mac yet, and there is the need to specify the target OS: make -j8 TARGET_OS=WIN64
# or
make -j8 TARGET_OS=LINUXAMD64 I also tested the So everything is working in Linux and Windows builds with my changes, except support for mmCIF and Mac. Se updated changes at: master...pslacerda:fpocket:master |
@pschmidtke, can you feedback? |
We would like to build fpocket with CMake as part of your official release.
Currently we have our own
CMakeLists.txt
file for building, which we have working with Visual Studio 2019, but we have attempted to upgrade this to Visual Studio 2022 and the source code for fpocket is crash the Microsoft Compiler.Visual Studio 2022 is also provide a lot of warnings, and before I wish to report any bug, I will need to eliminate our configuration as being the cause.
I can provide the list of compiler warnings and the compiler crash for Visual Studio 2022, if requested, but it would seem to be helpful to have an official
CMakeLists.txt
configuration that supports Windows build.The text was updated successfully, but these errors were encountered: