Windows 10 Build Tips #91
-
For those on Windows 10 platform here are some tips to make rv.exe compile. Downloading MSYS from https://www.msys2.org/ will get you a version which needs to be updated with the following commands.
Provided cmake version is 3.20, this will update to 3.25 You need to setup ONE aclocal to the aclocal PATH, do this (in same console we did the update to) Switch to /c/OpenRV and open the rvcmds.sh to edit it This will get rid of the python pip errors and make it work and install. you can then then you can try: and: The You now have a build in _builds/stage/app in bin directory there is rv.exe (or at least it should be) and you can try running it The step to install is: This will create _install dir in the openrv root dir and you can try running it from there. Stripping debug stuf for me doesnt work at all, and I end up with no rv.exe if i provide anything other than that command. It would be great if maintaniers would specify certain stuff and fix the build issues or provide a bat or sh file for windows platform. Not all users are TDs or developers, and this would help imensely to anyone who wants to run OpenRV no his machine (as many do it seems) Anyway, thanks to all devs to providing this, with a bit of pain its workable. Missing $HOME If you happen to install pacakges and the app just closes to desktop, simplest fix is to keep an _install or build app folder copied so you can restore it (packages copy files around to rv, like ftrack-connect-rv, which will botch your running app and you wont be able to run it again) Edit: Typos, and missing home-install packages |
Beta Was this translation helpful? Give feedback.
Replies: 10 comments 25 replies
-
Great tips, thanks! The aclocal one in particular seems to be a common problem and impossible to know how to fix without specialized knowledge. Would be good to have a note about it in the official docs. |
Beta Was this translation helpful? Give feedback.
-
Improving the windows build experience is one of our current priorities. You should see improvements on that front soon. The full build is aliased to This is why we don't provide a bat/sh file. It's the same command for all operating systems and should work well once you get used to it. You can We could add the Lines 29 to 36 in 2b799c5
Line 35 in 2b799c5 Redirecting to a build log is a good idea. You can redirect any alias to a file. Perhaps we could do it automatically using |
Beta Was this translation helpful? Give feedback.
-
Hi there, I'm trying to muddle my way through a windows build, I'm finding following the docs confusing, and found this thread which indeed is helpful, so thank you so much for contributing! To set the tone, I'm a TD who used RV for years in studio, but this build process is well beyond my developer skillz. A problem I'm running into: I use Anaconda to manage Python on my windows machine. I'm not an expert with it, but can successfully create various python environments to use for things like my own development or testing our various github projects like stable_diffusion and whatnot. In each case, I seem to have to launch a shell using that particular environment in order to use that particular python version. I'm getting confused with what seems to be the use of single-purpose shells that don't seem to cross-talk; I can open a Git bash shell and use unix-like commands, but can't run these rv scripts in it. The rvbootstrap or rvcmds.sh scripts also don't seem to be useful in Windows terminals, powershell, etc. This thread put me onto using MinGW64 (I have no idea what this is; looks like another new shell, with apparently a new set of available commands), which does allow me to get a bit further, but eventually the rvbootstrap process fails, with errors that appear to be related to python. I'm not all the way surprised, but my question is: is there a way to get these two things (one of anaconda's python environments and whatever MinGW64 is) to play together in order to muddle further through this build? Thank you! |
Beta Was this translation helpful? Give feedback.
-
Thank you @ddesmond for the super helpful guide. I followed it to the T and still getting build error. Looks like it might be OpenSSL related but I'm far from being an expert at this. Does anybody have an idea on what went wrong? |
Beta Was this translation helpful? Give feedback.
-
Thak you @ddesmond for this helpful guide but i am getting build error. Does anybody have an idea?
|
Beta Was this translation helpful? Give feedback.
-
cannot figure out this error... help 1>Checking Build System -- Configuring incomplete, errors occurred! |
Beta Was this translation helpful? Give feedback.
-
I've made a branch https://github.com/richardssam/OpenRV/tree/windows-config with some of the changes mentioned here, and a few others. The branch is essentially these notes, I did also add a path which seemed necessary for some of the building. Also, I ended up defaulting to MSVC 2017 for everything to make the build process easier. |
Beta Was this translation helpful? Give feedback.
-
thank everybody mentioning me but this is a group effort to find out a way to compile it! autodesk you have more devs than i am old :) up up your game (no offense to anyone, its just a positive critique to make stuff better in the OS space) |
Beta Was this translation helpful? Give feedback.
-
Hello, I hope I'm not too late to this discussion, but I'm having issues building OpenRV on Windows also. I've cleared most of them up but Note: I am using vcpkg to install Qt because that's a pain and I'm not normally involved in building on Windows. I've had to restructure the vcpkg dir a bit to build PySide2, but that build works fine so I assume it's not related to this. Error: Contents of the openssl dir:
configure file lines throwing the error:
Line from the vcxproj file: |
Beta Was this translation helpful? Give feedback.
-
How did I manage to rv build 2.1.0? here are my thoughts on getting it working "pacman -S pip" - don't worry about this I prefer building this in VM, or you chance it maynot work. Install VScode2022 with the necessary tools shown here install all necessary packages mentioned in the Windows build, it's not enough(requests & some others are missing), to find out you have to start building, make sure you write out the log and check the errors in the log, if in case its missing any modules install them through pip latest msys is not supported, you have to get a few steps down these things helped me to build successfully! |
Beta Was this translation helpful? Give feedback.
You mean you need to disable wsl or enbale it to make it work ? I got the same error and wsl is surely enabled