No RV executable

[BrianHanke]

I followed the Windows build guide carefully and everything seems to finish, but there is no RV executable in the 174,433 files in cmake-build. Installing doesn't help, no executable gets copied there either. Let me know what info I can provide to help troubleshoot.

Windows 10, VS Community 2017 and 2019, Qt 5.15.2. All other required apps and packages installed per the instructions.

Thank you!

[la0011]

Same Problem here, with exactly the same setup and procedure.

[RichardFrangenberg]

I have a similar problem here. The build seems to finish, but no RV executable got created.

However it seems that some targets were not built successfully (i.e. boost). Still trying to figure out why.
On Windows 11 here.

[BrianHanke]

Thanks for the comments. I get three errors during the build, but it still continues and finishes. There are also a ton of warnings about variable types and such, but I assume that doesn't matter. I attached the full wall o' text if it helps.

aclocal-1.16 : error : aclocal: file '/msys64/usr/share/aclocal/tcl.m4' does not exist [C:\OpenRV\cmake-build\cmake\dependencies\RV_DEPS_ATOMIC_OPS.vcxproj]
autoreconf-2.71 : error : aclocal failed with exit status: 1 [C:\OpenRV\cmake-build\cmake\dependencies\RV_DEPS_ATOMIC_OPS.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(241,5): error MSB8066: Custom build for 'C:\OpenRV\cmake-build\CMakeFiles\21d6eda14
8353c9194aa30467b92b5cc\RV_DEPS_ATOMIC_OPS-mkdir.rule;C:\OpenRV\cmake-build\CMakeFiles\21d6eda148353c9194aa30467b92b5cc\RV_DEPS_ATOMIC_OPS-download.rule;C:\OpenRV\cmake-build\CMakeFiles\21d6eda148353
c9194aa30467b92b5cc\RV_DEPS_ATOMIC_OPS-update.rule;C:\OpenRV\cmake-build\CMakeFiles\21d6eda148353c9194aa30467b92b5cc\RV_DEPS_ATOMIC_OPS-patch.rule;C:\OpenRV\cmake-build\CMakeFiles\21d6eda148353c9194a
a30467b92b5cc\RV_DEPS_ATOMIC_OPS-configure.rule;C:\OpenRV\cmake-build\CMakeFiles\21d6eda148353c9194aa30467b92b5cc\RV_DEPS_ATOMIC_OPS-build.rule;C:\OpenRV\cmake-build\CMakeFiles\21d6eda148353c9194aa30
467b92b5cc\RV_DEPS_ATOMIC_OPS-install.rule;C:\OpenRV\cmake-build\CMakeFiles\d6fd5551bcb9c62863b0231a2589ed33\RV_DEPS_ATOMIC_OPS-complete.rule;C:\OpenRV\cmake-build\CMakeFiles\192fb834f1f29087f0916065
13b4f96a\RV_DEPS_ATOMIC_OPS.rule;C:\OpenRV\cmake\dependencies\CMakeLists.txt' exited with code 1. [C:\OpenRV\cmake-build\cmake\dependencies\RV_DEPS_ATOMIC_OPS.vcxproj]

CUSTOMBUILD : error : pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. [C:\OpenR
V\cmake-build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj]

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(241,5): error MSB8066: Custom build for 'C:\OpenRV\cmake-build\CMakeFiles\cb4d089da
e717fd84e04b4e982add3af\RV_DEPS_PYTHON3-requirements-flag.rule;C:\OpenRV\cmake-build\CMakeFiles\cb4d089dae717fd84e04b4e982add3af\RV_DEPS_PYSIDE2-build-flag.rule;C:\OpenRV\cmake-build\CMakeFiles\a5a8a
cf88d2aff6b15bd538c9b1cdcc7\python39.dll.rule;C:\OpenRV\cmake-build\CMakeFiles\192fb834f1f29087f091606513b4f96a\RV_DEPS_PYTHON3-stage-target.rule;C:\OpenRV\cmake\dependencies\CMakeLists.txt' exited w
ith code -1. [C:\OpenRV\cmake-build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj]

wall-o-text.txt

[RichardFrangenberg]

How did you write the whole msys2 output to a file? Or is there a cmake log with the complete output?

[BrianHanke]

How did you write the whole msys2 output to a file? Or is there a cmake log with the complete output?

I set the max scrollback to like 100 billion lines, right click select all, copy and paste into a text document.

[rogernelson]

Hi @BrianHanke The build doesn't actually finish, but it can be hard to tell when it's building multi-threaded since the log does not always contain the errors necessarily at the end.

From looking at your log it seems the errors were building pyside. Pyside unfortunately will only build on Windows with VS 2017, so we recommend installing both 2017 and 2019. Do you have VS 2017 installed as well?

[rogernelson]

Also if you don't want to capture all the output from your shell, you can redirect the output to a file by doing something like

rvmk > /tmp/build.log

If you want to see that log while its build you can also do tail -f /tmp/build.log in another shell to follow it as it goes.

[BrianHanke]

Thanks @rogernelson. Yes, I have VS Community 2017 installed (15.9.51). Maybe the build process doesn't know where to find it?

[rogernelson]

It should find it automatically. Let me build it on my Windows machine and capture the log and compare it to yours to hopefully give us some idea of what is going on.

[BrianHanke]

Cool, looking forward to your results.

[rogernelson]

I had a few minutes to look and one definite difference between your output and mine is the aclocal error. For some reason on your system it's looking for the m4 file at /msys64/usr/share/aclocal/tcl.m4. I have this file, but it's located at /usr/share/aclocal/tcl.m4. Do you have the file there as well? What does this command give you: aclocal --print-ac-dir?

[BrianHanke]

The strange thing about that error is that tcl.m4 IS located in C:\msys64\usr\share\aclocal but it still says it can't find it.

Running aclocal --print-ac-dir gives me /usr/share/aclocal

No, I don't have any files there, assuming /usr/... translates to C:\usr. There is no folder there.

[rogernelson]

The paths are close, but not exactly the same the msys equivalent of C:\msys64\usr\share\aclocal is not /msys64/usr/share/aclocal/tcl.m4, it's actually /c/msys64/usr/share/aclocal/tcl.m4.

That said alocal should be looking in the directory given by aclocal --print-ac-dir. Is it possible you may have more than one copy of aclocal in your path? Like one installed by some other kind of Linux-like application like wsl or cygwin or anything like that?

[BrianHanke]

No I've never had wsl or cygwin or similar on this PC.

This does remind me that I wanted to ask about my environment variables being a potential source of problems. I've got some Maya/Houdini/Nuke/Python stuff although not sure those are picked up by MSYS2. Here is printenv from there. I notice some /usr/ references in PATH which point to nothing I assume since there is no folder at /c/usr

CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
SHELL=/usr/bin/bash
NUMBER_OF_PROCESSORS=16
PROCESSOR_LEVEL=23
TERM_PROGRAM_VERSION=3.6.2
DELIGHT=C:\Program Files\3Delight
MINGW_PREFIX=/mingw64
ACSvcPort=17532
PKG_CONFIG_PATH=/mingw64/lib/pkgconfig:/mingw64/share/pkgconfig
USERDOMAIN_ROAMINGPROFILE=LAPTOP-CG6AHFUQ
HOSTNAME=LAPTOP-CG6AHFUQ
PROGRAMFILES=C:\Program Files
MSYSTEM=MINGW64
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY;.PYW
ORIGINAL_TEMP=/c/Users/Brian/AppData/Local/Temp
VRAY_FOR_MAYA2023_PLUGINS=C:\Program Files\Chaos Group\V-Ray\Maya 2023 for x64\maya_vray/vrayplugins
MINGW_CHOST=x86_64-w64-mingw32
OS=Windows_NT
HOMEDRIVE=C:
INTEL_DEV_REDIST=C:\Program Files (x86)\Common Files\Intel\Shared Libraries\
MSYSTEM_CARCH=x86_64
OCIO=C:\onedrive\main_projects\data\ocio\bhgc_v2.ocio
USERDOMAIN=LAPTOP-CG6AHFUQ
GPU_USE_SYNC_OBJECTS=1
PWD=/home/Brian
RMANTREE=C:\Program Files\Pixar\RenderManProServer-24.4\
MAYA_LOCATION=C:\Program Files\Autodesk\Maya2023
USERPROFILE=C:\Users\Brian
ARNOLD_ROOT=C:\onedrive\Software\gaffer\arnold\sdk
OneDriveConsumer=C:\onedrive
DEFAULT_RENDERER=dl
MANPATH=/mingw64/local/man:/mingw64/share/man:/usr/local/man:/usr/share/man:/usr/man:/share/man
PRINTER=Canon D570 UFRII LT
GPU_MAX_HEAP_SIZE=100
TZ=America/New_York
MINGW_PACKAGE_PREFIX=mingw-w64-x86_64
tmp=C:\Users\Brian\AppData\Local\Temp
ALLUSERSPROFILE=C:\ProgramData
ORIGINAL_PATH=/c/Windows/System32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/
CommonProgramW6432=C:\Program Files\Common Files
HOME=/home/Brian
USERNAME=Brian
MARI_MAX_WRITE_PENDING_SIZE_FACTOR=0.75
VBOX_MSI_INSTALL_PATH=C:\Program Files\Oracle\VirtualBox\
OneDrive=C:\onedrive
COMSPEC=C:\Windows\system32\cmd.exe
APPDATA=C:\Users\Brian\AppData\Roaming
SYSTEMROOT=C:\Windows
LOCALAPPDATA=C:\Users\Brian\AppData\Local
ACSetupSvcPort=23210
COMPUTERNAME=LAPTOP-CG6AHFUQ
INFOPATH=/mingw64/local/info:/mingw64/share/info:/usr/local/info:/usr/share/info:/usr/info:/share/info
g_additionalModulePath=C:\Program Files\3Delight\cinema4d\R25
TERM=xterm
LOGONSERVER=\\LAPTOP-CG6AHFUQ
VRAY_OSL_PATH_MAYA2023=C:\Program Files\Chaos Group\V-Ray\Maya 2023 for x64\vray/opensl
ACLOCAL_PATH=/mingw64/share/aclocal:/usr/share/aclocal
USER=Brian
PSModulePath=C:\Program Files\WindowsPowerShell\Modules;C:\Windows\system32\WindowsPowerShell\v1.0\Modules
RlsSvcPort=22112
TEMP=/tmp
temp=C:\Users\Brian\AppData\Local\Temp
MSYSTEM_CHOST=x86_64-w64-mingw32
MAYA_MODULE_PATH=C:\Program Files\Common Files\Autodesk Shared\Modules\maya
ORIGINAL_TMP=/c/Users/Brian/AppData/Local/Temp
SHLVL=1
PROCESSOR_REVISION=6001
DriverData=C:\Windows\System32\Drivers\DriverData
COMMONPROGRAMFILES=C:\Program Files\Common Files
GPU_SINGLE_ALLOC_PERCENT=100
LC_CTYPE=en_US.UTF-8
CUDA_CACHE_MAXSIZE=268435456
PROCESSOR_IDENTIFIER=AMD64 Family 23 Model 96 Stepping 1, AuthenticAMD
SESSIONNAME=Console
VRAY_SEND_FEEDBACK=1
PS1=\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[35m\]$MSYSTEM\[\e[0m\] \[\e[33m\]\w\[\e[0m\]\n\$
MAYA_RENDER_DESC_PATH=C:\Program Files\3Delight\maya\render_desc
PKG_CONFIG_SYSTEM_LIBRARY_PATH=/mingw64/lib
HOMEPATH=\Users\Brian
XDG_DATA_DIRS=/mingw64/share/:/usr/local/share/:/usr/share/
MSYSCON=mintty.exe
TMP=/tmp
GPU_FORCE_64BIT_PTR=0
CONFIG_SITE=/etc/config.site
PATH=/mingw64/bin:/usr/local/bin:/usr/bin:/bin:/c/Windows/System32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
ProgramW6432=C:\Program Files
GPU_MAX_ALLOC_PERCENT=100
MSYSTEM_PREFIX=/mingw64
WINDIR=C:\Windows
PROCESSOR_ARCHITECTURE=AMD64
PUBLIC=C:\Users\Public
PKG_CONFIG_SYSTEM_INCLUDE_PATH=/mingw64/include
RFMTREE=C:\Program Files\Pixar\RenderManForMaya-24.4\
SYSTEMDRIVE=C:
KATANA_RESOURCES=C:\Program Files\3Delight\3DelightForKatana
OLDPWD=/
TERM_PROGRAM=mintty
ProgramData=C:\ProgramData

[BrianHanke]

Oh! There are two aclocal paths, just noticed. Is that a problem?

[rogernelson]

Hi @rajiv-hqvfx. I would recommend stick with your first build command. To build pyside, you need to have VS2017 installed, but it will find it automatically. You should still keep VS2019 for building everything else.

If there is no executable, there likely was an error somewhere. Since RV is building multi-threaded (the -j8 parameter) it might not be the last line of output that contains the error. You may have to scroll up to see it, or you can redirect your build output to a log file (by adding > [path to log file] at the end of the build command) and search the log if that is easier.

[vfxbyjohn]

Hey all, I've been having similar issues, I've setup a VM of Windows 10 and followed the build instructions with VS17+19 etc and still no luck..

Here are some snippets of my build log with error in it
rv_errors.txt

They all seem to be related too:
`Unable to translate type "Qt3DRender::QTextureImageDataPtr": Cannot find type entry for "QSharedPointer".

warning C4996: 'QXmlDefaultHandler::fatalError':

'QXmlSimpleReader::setErrorHandler'`

Not really sure where to go from here

[rajivfx]

I Did follow all instructions given on this documentation:
https://github.com/AcademySoftwareFoundation/OpenRV/blob/main/doc/build_system/config_windows.md
After build process finish there is no RV executable file.
Anyone successfully build RV on Window 11 ?

[rogernelson]

I think a number of people have build successfully on Win11, yes. There are a number of traps that people have fallen into. We know there are incompatibilities with wsl and VS2022, so we recommend not having those installed. Also if your root path to the build is too long, you can run into problems with some third-parties generating paths over the Windows limit of 260 characters.

If all those things are okay, could you please try the following and send us the resulting /tmp/build.log.

source rvcmds.sh
rvmk > /tmp/build.log

[rogernelson]

Hi @johnperrigo-vfx -- you seem to be getting Qt errors, perhaps due to a wrong version being installed? Have you downloaded and installed Qt5.15.2?

[BrianHanke]

One thing that might help people is having download links to VS Community 2017 and 2019 and Qt. They are all rather difficult to find. I'll include them here:

https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=15
https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=16
https://download.qt.io/official_releases/online_installers/

You'll need a Qt account to install. Also carefully note their licensing agreement for open source/non-commercial software.

[vfxbyjohn]

Hi @johnperrigo-vfx -- you seem to be getting Qt errors, perhaps due to a wrong version being installed? Have you downloaded and installed Qt5.15.2?

Hi Roger, thanks and yes that seems likely the culprit, I'll try a fresh install of Qt and see if it fixes it. In the meantime I did manage to get it to compile under a version of CentOS I got running in WSL, copied it over to Ubuntu 22.04 and its running fairly well passing the GUI back into Windows!

[rogernelson]

Oh wow, that is quite the setup! I never would have expected that to work, so max points for creativty!

Please let us know if a fresh Qt fixes the problem.

[vfxbyjohn]

Oh wow, that is quite the setup! I never would have expected that to work, so max points for creativty!

Please let us know if a fresh Qt fixes the problem.

haha thanks, I had very little expectation it would work but its quite amazing that it is, and for my use case it might actually be the best way to run it as part of the Ubuntu WSL. Performance seems totally fine within RV, 4K exr playback without issues, just moving the window around can be a little tricky sometimes, probably something todo with Windows deciding where the focus of the cursor is.

[17matejka]

I followed the Windows build guide carefully and everything seems to finish, but there is no RV executable in the 174,433 files in cmake-build. Installing doesn't help, no executable gets copied there either. Let me know what info I can provide to help troubleshoot.

Windows 10, VS Community 2017 and 2019, Qt 5.15.2. All other required apps and packages installed per the instructions.

Thank you!

PREP before building

This tutorial referencing the oficial Windows build tutorial
https://github.com/AcademySoftwareFoundation/OpenRV/blob/main/doc/build_system/config_windows.md

After 1. Step

Install Visual Studio Build Tools 2019 if your VS installation does not have it (check this path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\bin\Hostx64\x64)
If you have VS 2022 installed, I recommend uninstalling it, during building process, it was prioritizing this 2022 version instead of 2017

After 4. Step

• Do not forget to disable WSL/WSL 2 if you have it (it is not default part of Win)
• This is part of official MSYS2 installation tutorial, it will install build tools:

pacman -S mingw-w64-ucrt-x86_64-gcc

• For up-to-date MSYS2 etc. use this:

pacman -Suy

• One of my builds needed this:

pacman -S clang

After 5. Step

• Export these envs in your MINGW64, path to folders depends on your locations
• With PYTHONPATH a ACLOCAL_PATH, we are making sure, that MINGW64 knows the right PATHs, sometimes it is looking elsewhere Unsuccessful build on Win10 - aclocal-1.16 : error #59
• We are adding to PATH path to .exe necessary for PySide2 build (cl.exe, nmake.exe, jom.exe)
• Instead of adding PATH to /c/'Program Files (x86)'/'Microsoft Visual Studio'/2019/BuildTools/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64 you can probably use /c/'Program Files (x86)'/'Microsoft Visual Studio'/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64

export PYTHONPATH=/c/msys64/mingw64/bin:/c/msys64/mingw64/lib/python3.10/site-packages
export ACLOCAL_PATH=/usr/share/aclocal
export PATH=$PATH:/c/'Program Files (x86)'/'Microsoft Visual Studio'/2019/BuildTools/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64:/c/Qt/Tools/QtCreator/bin

BUILD

cmake -B cmake-build -G "Visual Studio 16 2019" -A x64 -DCMAKE_BUILD_TYPE=Release -DRV_DEPS_WIN_PERL_ROOT=/c/Strawberry/perl/bin -DRV_DEPS_QT5_LOCATION=/c/Qt/5.15.2/msvc2019_64

• Find this .cpp file in C:\OpenRV\cmake-build_deps\rv_deps_pyside2-src\sources\shiboken2\libshiboken\ sbknumpyarrayconverter.cpp in your Open RV folder and modify it: replace NPY_ARRAY_UPDATEIFCOPY with NPY_ARRAY_WRITEBACKIFCOPY as @geffrak saying in this discussion

cmake --build cmake-build --config Release --target rv -j8
cmake --install cmake-build --config Release

• For instalation I recommend running MINGW64 as admin

[rubikstriangle]

I finally got a build to generate rv.exe!
I'm curious if it is normal to get hundreds if not thousands of yellow warnings in the cmake --build process? I noticed that hundreds of my warnings ended in RV_DEPS_FFMPEG.vcxproj like the one below. I haven't thoroughly tested the build so it may be fine. Just curious if the warnings are to be expected?

C:\OpenRV\cmake-build\RV_DEPS_FFMPEG\src\libavcodec\qcelpdata.h(204): warning C4267: 'initializing': conversion from 'size_t' to 'uint8_t', possible loss of data [C:\OpenRV\cmake-build\cmake\dependencies\RV_DEPS_FFMPEG.vcxproj]

[BrianHanke]

@rubikstriangle Congrats on the successful build! I get billions of yellow warnings and RV still seems to work fine.

[ericcunha]

@17matejka thank you for these instructions, they've resolved most of the errors I've been getting!
The last thing I'm getting stuck on is getting all of the python requirements properly installed though. I'm specifically having trouble with pycryptodomex, a requirement of py7zr, to install. I ultimately get this error:

  │ exit code: 1
  ╰─> [17 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "C:/msys64/tmp/pip-install-m8f7xura/pycryptodomex_d8a83e09111146459aecd1b59f599427/setup.py", line 488, in <module>
          set_compiler_options(package_root, ext_modules)
        File "C:/msys64/tmp/pip-install-m8f7xura/pycryptodomex_d8a83e09111146459aecd1b59f599427/compiler_opt.py", line 327, in set_compiler_options
          clang = compiler_is_clang()
        File "C:/msys64/tmp/pip-install-m8f7xura/pycryptodomex_d8a83e09111146459aecd1b59f599427/compiler_opt.py", line 251, in compiler_is_clang
          return test_compilation(source, msg="clang")
        File "C:/msys64/tmp/pip-install-m8f7xura/pycryptodomex_d8a83e09111146459aecd1b59f599427/compiler_opt.py", line 82, in test_compilation
          objects = compiler.compile([fname], extra_postargs=extra_cc_options)
        File "C:/Users/User/.local/lib/python3.10-mingw_x86_64/site-packages/setuptools/_distutils/_msvccompiler.py", line 343, in compile
          self.initialize()
        File "C:/Users/User/.local/lib/python3.10-mingw_x86_64/site-packages/setuptools/_distutils/_msvccompiler.py", line 246, in initialize
          raise DistutilsPlatformError(
      distutils.errors.DistutilsPlatformError: --plat-name must be one of ('win32', 'win-amd64', 'win-arm32', 'win-arm64')
      Testing support for clang
      [end of output]

I'm building on a fresh Windows 11 VM and have followed all of the directions that I'm aware of. Anybody else have issues installing py7zr? This is my first time trying to build any kind of software and I've never used mingw64, so forgive me if this is something trivial, but I can't seem to find any information on how to resolve.

[17matejka]

Hi @ericcunha, just guessing by this line distutils.errors.DistutilsPlatformError: --plat-name must be one of ('win32', 'win-amd64', 'win-arm32', 'win-arm64') ... was your VM properly set up? Or is there anything that could effect the platform settings etc?

[ericcunha]

Thanks for the reply! Looks like my issue was actually discussed here: #91

Specifically, I needed this in my environment before installing the python packages:
export SETUPTOOLS_USE_DISTUTILS=stdlib

Now all of the python packages install correctly.

[StefanKirste]

after doing all stuff mentioned here , and in other threads,
When i run:
cmake -B cmake-build -G "Visual Studio 16 2019" -A x64 -DCMAKE_BUILD_TYPE=Release -DRV_DEPS_WIN_PERL_ROOT=/c/Strawberry/perl/bin -DRV_DEPS_QT5_LOCATION=/c/Qt/5.15.2/msvc2019_64
all is fine.
but the next step:
cmake --build cmake-build --config Release --target rv -j8
i Got an Error again, i attached the logfile.

May you can help me?
Build.log

[munkybutt]

Hey - I have followed the Windows instructions and have tried the various things in this thread but I am having no luck.
I am on Windows10 with a fresh install.
The only thing I have that is potentially problematic is I have VS2022 still installed but I need this for my day to day work so uninstalling isn't really an option :/
The error message I am getting is:

"C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\main_executable.vcxproj" (default target) (1) ->
       "C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\src\bin\apps\rv\rv.vcxproj" (default target) (3) ->
       "C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\image_formats.vcxproj" (default target) (8) ->
       "C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\src\lib\image\io_oiio\io_oiio.vcxproj" (default target) (130) ->
       "C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\cmake\dependencies\RV_DEPS_OIIO.vcxproj" (default target) (134) ->
       (CustomBuild target) ->
         C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(241,5): error MSB8066: Custom build for 'C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\CMakeFiles\844105fe84481bb9e
       a09d1e8324a7f97\RV_DEPS_OIIO-configure.rule;C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\CMakeFiles\844105fe84481bb9ea09d1e8324a7f97\RV_DEPS_OIIO-build.rule;C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\CMakeFiles\844105fe844
       81bb9ea09d1e8324a7f97\RV_DEPS_OIIO-install.rule;C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\CMakeFiles\018a3d8a9bcaed0de52a08effb2d97a8\RV_DEPS_OIIO-complete.rule;C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\CMakeFiles\5fa4
       33052c3497ebac228a2c81d461b4\RV_DEPS_OIIO.rule' exited with code 1. [C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\cmake\dependencies\RV_DEPS_OIIO.vcxproj]


       "C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\main_executable.vcxproj" (default target) (1) ->
       "C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\src\bin\apps\rv\rv.vcxproj" (default target) (3) ->
       "C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\cmake\dependencies\dependencies.vcxproj" (default target) (42) ->
       "C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj" (default target) (66) ->
         C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\_deps\rv_deps_pyside2-src\pyside3_build\py3.10-qt5.15.2-64bit-release\pyside2\PySide2\QtRemoteObjects\PySide2\QtRemoteObjects\qremoteobjectabstractpersistedstore_wrapper.cpp : fatal error
       C1083: Cannot open compiler generated file: '': Invalid argument [C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj]
         C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\_deps\rv_deps_pyside2-src\pyside3_build\py3.10-qt5.15.2-64bit-release\pyside2\PySide2\QtWebEngineCore\PySide2\QtWebEngineCore\qwebengineurlrequestinterceptor_wrapper.cpp : fatal error C108
       3: Cannot open compiler generated file: '': Invalid argument [C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj]
         CUSTOMBUILD : error : Error compiling pyside2 [C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj]
         C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(241,5): error MSB8066: Custom build for 'C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\CMakeFiles\49197400bb9984a89
       23b135d9d814d86\RV_DEPS_PYSIDE2-build-flag.rule;C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\CMakeFiles\d85790f5a56b88f817789a317effa0fb\python310.dll.rule;C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\CMakeFiles\5fa433052c34
       97ebac228a2c81d461b4\RV_DEPS_PYTHON3-stage-target.rule' exited with code 1. [C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj]

[munkybutt]

I have an updated set of errors after getting latest this morning

"C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\main_executable.vcxproj" (default target) (1) ->
       "C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\src\bin\apps\rv\rv.vcxproj" (default target) (3) ->
       "C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\cmake\dependencies\dependencies.vcxproj" (default target) (7) ->
       "C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj" (default target) (117) ->
       (CustomBuild target) ->
         C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\_deps\rv_deps_pyside2-src\pyside3_build\py3.10-qt5.15.2-64bit-release\pyside2\PySide2\QtRemoteObjects\PySide2\QtRemoteObjects\qremoteobjectabstractpersistedstore_wrapper.cpp : fatal error
       C1083: Cannot open compiler generated file: '': Invalid argument [C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj]
         C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\_deps\rv_deps_pyside2-src\pyside3_build\py3.10-qt5.15.2-64bit-release\pyside2\PySide2\QtWebEngineCore\PySide2\QtWebEngineCore\qwebengineurlrequestinterceptor_wrapper.cpp : fatal error C108
       3: Cannot open compiler generated file: '': Invalid argument [C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj]
         CUSTOMBUILD : error : Error compiling pyside2 [C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj]
         C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for 'C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\CMakeFiles\49197400bb9984a8923b135
       d9d814d86\RV_DEPS_PYTHON3-requirements-flag.rule;C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\CMakeFiles\49197400bb9984a8923b135d9d814d86\RV_DEPS_PYSIDE2-build-flag.rule;C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\CMakeFile
       s\d85790f5a56b88f817789a317effa0fb\python310.dll.rule;C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\CMakeFiles\5fa433052c3497ebac228a2c81d461b4\RV_DEPS_PYTHON3-stage-target.rule;C:\Users\shea.richardson\Documents\GitHub\OpenRV\cmake\dep
       endencies\CMakeLists.txt' exited with code 1. [C:\Users\shea.richardson\Documents\GitHub\OpenRV\_build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj]

[munkybutt]

I noticed that python in mngw64 is 3.11 but pyside is building against 3.10 - will this be a problem?

[geffrak]

No. OpenRV is building a 3.10 and building PySide for it.

[krishnaavril]

       "C:\OpenRV\_build\src\bin\apps\rv\rv.vcxproj" (default target) (3) ->
       "C:\OpenRV\_build\cmake\dependencies\dependencies.vcxproj" (default target) (15) ->
       "C:\OpenRV\_build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj" (default target) (164) ->
       (CustomBuild target) ->
         C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for 'C:\OpenRV\_build\CMakeFiles\2
       7ffb7829657fcab58aa9f832fd8f307\RV_DEPS_PYTHON3-requirements-flag.rule;C:\OpenRV\_build\CMakeFiles\27ffb7829657fcab58aa9f832fd8f307\RV_DEPS_PYSIDE2-build-flag.rule;C:\OpenRV\_build\C
       MakeFiles\6ef89c14370471f72f972cb264110d52\python310.dll.rule;C:\OpenRV\_build\CMakeFiles\dc0b82080efe119cccb8b58ef9885864\RV_DEPS_PYTHON3-stage-target.rule;C:\OpenRV\cmake\dependenc
       ies\CMakeLists.txt' exited with code 1. [C:\OpenRV\_build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj]

    4879 Warning(s)
    1 Error(s)

I caught the same error, did you managed to solveit? I'm in VS2022

[munkybutt]

I got it to work by building from the C drive on a fresh windows 11 virtual machine

[up1415]

buildlog - CL.log

I built with VS2022 and seems pyside is not built successfully. I attach my build log.

"E:\OpenRV_build\main_executable.vcxproj" (default target) (1) ->
"E:\OpenRV_build\src\bin\apps\rv\rv.vcxproj" (default target) (3) ->
"E:\OpenRV_build\cmake\dependencies\dependencies.vcxproj" (default target) (18) ->
"E:\OpenRV_build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj" (default target) (133) ->
(CustomBuild target) ->
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for 'E:\OpenRV_build\CMakeFiles\ba9056a2e12bbb280c19368b23728de1\RV_DEPS_PYTHON3-requirements-flag.rule;E:\OpenRV_build\CMakeFiles\ba9056a2e12bbb280c19368b23728de1\RV_DEPS_PYSIDE2-build-flag.rule;E:\OpenRV_build\CMakeFiles\ed214e5487734762d00e67784b1bbf86\python310.dll.rule;E:\OpenRV_build\CMakeFiles\b2670343e3e6d13858c550f7afcec460\RV_DEPS_PYTHON3-stage-target.rule;E:\OpenRV\cmake\dependencies\CMakeLists.txt' exited with code -1073741819. [E:\OpenRV_build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj]

3905 Warning(s)
1 Error(s)

[mingvfx]

how to fix this error , i have the same error,only this one

[mingvfx]

but i build with vs2019

[yeoldebrian]

Thanks so much! I had to add export SETUPTOOLS_USE_DISTUTILS=stdlib to get py7zr to install. That was driving me crazy, and should be in the windows build instructions.

[cedrik-fuoco-adsk]

It is in the rvcmd.sh script.

Note: When using the Python from msys2, it has to re-build some of the Python requirements from source and it needs more requirement to build them. It is best to use Python from the Windows environment itself if that works for you.

[mingvfx]

构建日志 - CL.log

我用 VS2022 构建，似乎 pyside 没有构建成功。我附上我的构建日志。

“E:\OpenRV_build\main_executable.vcxproj”（默认目标）(1) -> “E:\OpenRV_build\src\bin\apps\rv\rv.vcxproj”（默认目标）(3) -> “E:\ OpenRV_build\cmake\dependencies\dependency.vcxproj"（默认目标）(18) -> "E:\OpenRV_build\cmake\dependency\RV_DEPS_PYTHON3-stage-target.vcxproj"（默认目标）(133) -> （CustomBuild 目标） - > C：\ Program Files \ Microsoft Visual Studio \ 2022 \ Community \ MSBuild \ Microsoft \ VC \ v170 \ Microsoft.CppCommon.targets（254,5）：错误MSB8066：'E：\ OpenRV_build \ CMakeFiles \ ba9056a2e12bbb280c19368b23728de1的自定义构建\RV_DEPS_PYTHON3-requirements-flag.rule;E:\OpenRV_build\CMakeFiles\ba9056a2e12bbb280c19368b23728de1\RV_DEPS_PYSIDE2-build-flag.rule;E:\OpenRV_build\CMakeFiles\ed214e5487734762d00e67784b1bbf86 \python310.dll.rule;E:\OpenRV_build\CMakeFiles\b2670343e3e6d13858c550f7afcec460\ RV_DEPS_PYTHON3-stage-target.rule;E:\OpenRV\cmake\dependencies\CMakeLists.txt' 退出，代码为 -1073741819。[E：\ OpenRV_build \ cmake \ dependencys \ RV_DEPS_PYTHON3-stage-target.vcxproj]

3905 Warning(s)
1 Error(s)

i have the same errror,have you solved it ?