-
Notifications
You must be signed in to change notification settings - Fork 17
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 installation? #17
Comments
Interesting question, thanks! There shouldn't be any platform specific build instructions required - cmake, git and vcpkg should mean that the same process is followed for all platforms; you can see this in the .github/workflows/cmake.yml file. Having said that, I'll try and do a local build on windows to see if this indeed as straight forward as it should be! |
FYI, the windows installation went very smooth, even when I thought Microsoft vcpkg was a package manager and compiler. |
Please write a short doc or screenshot the way you used. @ErichZimmer |
I compiled openpiv with a different Windows laptop, but this time, no executables are made. |
I get these errors which clearly point to missing packages:
|
For spdlog, I installed it with vcpkg and everything compiled. When trying to compile openpiv on my personal laptop, no executables or dlls are made and there are no messages that I observed detailing why. |
spdlog is no longer required, and I suspect cmake has cached config info in build that should be removed; simplest way to do this is completely remove the build directory and rerun: cd <directory to openpiv-c>
cmake -B build -S .
cmake --build build |
Are there supposed to be a DLL in build/openpiv? The only place where I found the DLL and executable files were in build/out/Debug |
You're right. yet, there are other errors after I removed the folder, clone the present git master branch and run the build:
|
@alexlib I wonder if that could be a stale non-recursive clone or something similar - something is looking for fmt still but there isn't a requirement. I'm fairly sure the code in master is good because the builds for all platforms are working, including windows. I don't have the ability to try this locally at the moment, I will try and do a local windows build in the next few days. |
@ErichZimmer I haven't put much (any?) effort into making the post build step do anything useful; build artefacts will probably appear in config specific directories i.e. Debug, Release, ... |
@timdewhirst All build related files are in the out/Debug directory. To execute the example files, I use |
I recently noticed that cmake behaves differently on windows: on unix it will create a configuration and then when you build, you build that configuration. Windows appears to make a number of configurations up front, and then you can select which configuration to build with an additional --config option i.e.
Worth knowing as the Release build will contain significant compiler optimizations. I'll update the README.md |
@timdewhirst Should we add a |
CMake should take care of applying optimizations for us; running
The \O2 flag is present; if after some experiments \O3 was found to be better then by all means we could modify. |
On windows 11 with MSVC 2022 compiler, I get the following error now.
|
Nevermind, I simply misinterpreted the warning and everything works. |
I should probably clean that up... |
Are there tips to install it on Windows ?
The text was updated successfully, but these errors were encountered: