OpenRV
OpenRV copied to clipboard
AcademySoftwareFoundation
No RV executable
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!
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.
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]
How did you write the whole msys2 output to a file? Or is there a cmake log with the complete output?
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.
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?
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.
Thanks @rogernelson. Yes, I have VS Community 2017 installed (15.9.51). Maybe the build process doesn't know where to find it?
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.
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?
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.
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?
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
Do you mean two paths printed when you do aclocal --print-ac-dir? Or you have both c:\msys64\usr\share\aclocal and /usr/share/aclocal? If its the latter, those paths should be equivalent -- one is just the msys interpretation of the windows path.
What I am mainly trying to figure out is why when building it's looking in /msys/usr/share/aclocal instead of just /usr/share/aclocal. It seems to me there is some kind of mixup between the msys path and windows path, but I don't know for sure.
I mean in my printenv it says ACLOCAL_PATH=/mingw64/share/aclocal:/usr/share/aclocal. Is two paths listed there causing a mixup?
Ok, updated ACLOCAL_PATH to just have /usr/share/aclocal. No error any more! Fingers crossed that this build attempt works.
I actually have the same ACLOCAL_PATH in my envars, but if it fixed the problem for you that is great!
No luck, sadly. Build took a lot longer, no aclocal error, looked like it was working on a lot of pyside stuff this time. Still, no executable to be found.
@rogernelson do you get any errors during build? I'm still getting errors 2 and 3 that I listed early on in the thread.
Success at last! I fired up a Windows 10 VM on Azure and built RV there. There's probably some ancient mess of settings on my laptop that was causing a problem. Downloaded the build locally and it runs great.
Final question if anybody reads this far: is it permissible to share the build on my GitHub to help others out? I know I'd need to include the license, but beyond that not sure what the protocol is. Thanks in advance for any guidance.
I have the same problem here. I had an error because I had VS Community 2022 installed. After deinstall the specific error disappeared, but now I have no idea what's the problem. A few errors still appear: Line 8179: D:\UserDatenHaggi\Documents\coding\OpenRV\cmake-build_deps\rv_deps_pyside2-src\pyside3_build\py3.9-qt5.15.2-64bit-release\pyside2\PySide2\QtRemoteObjects\PySide2\QtRemoteObjects\qremoteobjectabstractpersistedstore_wrapper.cpp : fatal error C1083: Datei (vom Compiler generiert) kann nicht ge�ffnet werden: "": Invalid argument [D:\UserDatenHaggi\Documents\coding\OpenRV\cmake-build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj] Line 8279: jom: D:\UserDatenHaggi\Documents\coding\OpenRV\cmake-build_deps\rv_deps_pyside2-src\pyside3_build\py3.9-qt5.15.2-64bit-release\pyside2\PySide2\QtRemoteObjects\CMakeFiles\QtRemoteObjects.dir\build.make [PySide2\QtRemoteObjects\CMakeFiles\QtRemoteObjects.dir\PySide2\QtRemoteObjects\qremoteobjectabstractpersistedstore_wrapper.cpp.obj] Error 1 Line 10458:CUSTOMBUILD : error : Error compiling pyside2 [D:\UserDatenHaggi\Documents\coding\OpenRV\cmake-build\cmake\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj]
I'd appreciate a hint what I could do. All of them seem to be python/pyside related.
Great news! @BrianHanke I basically asked the same question in the AMA session with the Autodesk guys. The answer was to better check with my legal department. Since I don't have a legal department that is not an option. So far there doesn't seem to be a clear answer, but it would be great if anyone could shine some light on that.
@RichardFrangenberg Thanks for the info. No legal dept here either, so I guess I'll skip it unless we hear otherwise.
@BrianHanke @RichardFrangenberg This is not official legal advise, I am not a lawyer, but I would not recommend sharing the output of your build. The complexity starts with binaries distribution, which you would then be doing. The more restrictive license being pulled by default build configuration in Open RV is LGPL, so risk is really really low, but no one is ever shielded from lawsuit even if you have 99.9% chances of being exonerated. Providing a build increase your exposure. Again, should be very low and we are talking about extreme use case here that are not likely to happen but still, you need to understand the risk. We will be working soon on facilitating consumption - stay tuned :)
@BrianHanke I am happy you got the build working! For what it's worth, I am also building on a clean Windows VM with only the components required to build installed.
I'd also echo Guillaume's advice to err on the side of caution when it comes to legal issues.
I had the same aclocal problem with the 2 paths and the same error with the build erroring.
so i ran
export ACLOCAL_PATH=/usr/share/aclocal
to only have /usr/share/aclocal
I am not sure where the second one came from but it fixed my build issue and made rv.exe appear :) This was on a very recent windows 10 install, with not much even installed ... anyhow it works now.
I had a similar issue with RV_DEPS_PYTHON3 failing to build and it was because of pyside2. There was a version mismatch between shiboken2 and numpy.
The shiboken2 version that was being downloaded was using some deprecated numpy enums.
I just hacked the sbknumpyarrayconverter.cpp file replacing NPY_ARRAY_UPDATEIFCOPY with NPY_ARRAY_WRITEBACKIFCOPY
I haven't had time to investigate it more thoroughly yet.
I had a similar issue with RV_DEPS_PYTHON3 failing to build and it was because of pyside2. There was a version mismatch between shiboken2 and numpy. The shiboken2 version that was being downloaded was using some deprecated numpy enums. I just hacked the
sbknumpyarrayconverter.cppfile replacingNPY_ARRAY_UPDATEIFCOPYwithNPY_ARRAY_WRITEBACKIFCOPYI haven't had time to investigate it more thoroughly yet.
This should have fixed the issue... Can you show the logs of when it installs NumPy into RV's python?
looks like my user install of numpy (which is 1.23) is taking precedence
CustomBuild:
"The build of 'D:\Dev\OpenRV\cmake-build\CMakeFiles\054c25e07d1b34473f031eb2389d95b6\python39.dll.rule' depends on 'D:\DEV\OPENRV\CMAKE-BUILD\RV_DEPS_PYTHON3\INSTALL\RV_DEPS_PYSIDE2-BUILD-FLAG' which is produced by the build of 'D:\Dev\OpenRV\cmake-build\CMakeFiles\88126ce37fdc28f1c62a2db9bf32c5fc\RV_DEPS_PYSIDE2-buil
d-flag.rule'. The items cannot be built in parallel."
"The build of 'D:\Dev\OpenRV\cmake-build\CMakeFiles\f6a189e125236184cf254089e1e622b8\RV_DEPS_PYTHON3-stage-target.rule' depends on 'D:\DEV\OPENRV\CMAKE-BUILD\STAGE\APP\BIN\PYTHON39.DLL' which is produced by the build of 'D:\Dev\OpenRV\cmake-build\CMakeFiles\054c25e07d1b34473f031eb2389d95b6\python39.dll.rule'. The item
s cannot be built in parallel."
Building PySide2 using D:/Dev/OpenRV/src/build/make_pyside.py
Requirement already satisfied: numpy<1.23 in d:\dev\openrv\cmake-build\rv_deps_python3\install\lib\site-packages (1.22.4)
running install
D:\Dev\OpenRV\cmake-build\RV_DEPS_PYTHON3\install\lib\site-packages\setuptools\command\install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
running build
Python architecture is 64bit
jom was found in C:/Qt/Tools/QtCreator/bin/jom\jom.exe
Adding D:/Dev/OpenRV/cmake-build/RV_DEPS_PYTHON3/build/libclang/libclang\bin as detected by LLVM_INSTALL_DIR to PATH
Inserting path 'D:\Dev\OpenRV\cmake-build\RV_DEPS_PYTHON3\install\Scripts' to environment
Inserting path 'C:\Qt\5.15.2\msvc2019_64\bin' to environment
Inserting path 'D:/Dev/OpenRV/cmake-build/RV_DEPS_PYTHON3/build/libclang/libclang\bin' to environment
==============================
Package version: 5.15.2.1
Build type: Release
Build tests: False
---
Make path: C:/Qt/Tools/QtCreator/bin/jom\jom.exe
Make generator: NMake Makefiles JOM
Make jobs: -j12
---
setup.py directory: D:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src
Build scripts directory: D:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src\build_scripts
Sources directory: D:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src\sources
Building shiboken2 will create and touch directories
in the following order:
make build directory (py*_build/*/*) ->
make install directory (py*_install/*/*) ->
setuptools build directory (build/*/*) ->
setuptools install directory
(usually path-installed-python/lib/python*/site-packages/*)
make build directory: D:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src\pyside3_build\py3.9-qt5.15.2-64bit-release
make install directory: D:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src\pyside3_install\py3.9-qt5.15.2-64bit-release
setuptools build directory: D:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src\build\lib.win-amd64-cpython-39
setuptools install directory: D:\Dev\OpenRV\cmake-build\RV_DEPS_PYTHON3\install\Lib\site-packages
make-installed site-packages directory: D:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src\pyside3_install\py3.9-qt5.15.2-64bit-release\Lib\site-packages
(only relevant for copying files from 'make install directory'
to 'setuptools build directory'
---
Python executable: D:\Dev\OpenRV\cmake-build\RV_DEPS_PYTHON3\install\bin\python.exe
Python includes: D:\Dev\OpenRV\cmake-build\RV_DEPS_PYTHON3\install\Include
Python library: D:\Dev\OpenRV\cmake-build\RV_DEPS_PYTHON3\install\libs\python39.lib
Python prefix: D:\Dev\OpenRV\cmake-build\RV_DEPS_PYTHON3\install
Python scripts: D:\Dev\OpenRV\cmake-build\RV_DEPS_PYTHON3\install\Scripts
---
Qt qmake: C:\Qt\5.15.2\msvc2019_64\bin\qmake.exe
Qt version: 5.15.2
Qt bins: C:/Qt/5.15.2/msvc2019_64/bin
Qt docs: C:/Qt/Docs/Qt-5.15.2
Qt plugins: C:/Qt/5.15.2/msvc2019_64/plugins
---
OpenSSL dll directory: D:/Dev/OpenRV/cmake-build/RV_DEPS_OPENSSL/install/bin
==============================
Building module shiboken2...
Deleting module build folder D:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src\pyside3_build\py3.9-qt5.15.2-64bit-release\shiboken2...
Creating module build folder D:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src\pyside3_build\py3.9-qt5.15.2-64bit-release\shiboken2...
Qt Source dir: C:/Qt/5.15.2\Src\qtbase
Output format will be qthelp
Configuring module shiboken2 (D:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src\sources\shiboken2)...
In directory D:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src\pyside3_build\py3.9-qt5.15.2-64bit-release\shiboken2:
Running command: "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -G "NMake Makefiles JOM" -DBUILD_TESTS=False -DQt5Help_DIR=C:/Qt/Docs/Qt-5.15.2 -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=D:\Dev\OpenRV\cmake-build\_deps\rv
_deps_pyside2-src\pyside3_install\py3.9-qt5.15.2-64bit-release D:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src\sources\shiboken2 -DPYTHON_EXECUTABLE=D:\Dev\OpenRV\cmake-build\RV_DEPS_PYTHON3\install\bin\python.exe -DPYTHON_INCLUDE_DIR=D:\Dev\OpenRV\cmake-build\RV_DEPS_PYTHON3\install\Include -DPYTHON_LIBRARY=D:\De
v\OpenRV\cmake-build\RV_DEPS_PYTHON3\install\libs\python39.lib -DQT_SRC_DIR=C:/Qt/5.15.2\Src\qtbase -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DPACKAGE_SETUP_PY_PACKAGE_VERSION=5.15.2.1 -DPACKAGE_SETUP_PY_PACKAGE_TIMESTAMP= -DCMAKE_INSTALL_RPATH_USE_LINK_PATH=yes -DUSE_PYTHON_VERSION=3.3 -DDOC_OUTPUT_FORMAT=qthelp -DFULLDOCSBU
ILD=1
Re-run cmake no build system arguments
-- The C compiler identification is MSVC 19.16.27048.0
-- The CXX compiler identification is MSVC 19.16.27048.0
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx64/x64/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx64/x64/cl.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx64/x64/cl.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx64/x64/cl.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Using Qt 5
-- Found PythonInterp: D:/Dev/OpenRV/cmake-build/RV_DEPS_PYTHON3/install/bin/python.exe (found suitable version "3.9.15", minimum required is "3.3")
-- Found PythonLibs: optimized;D:/Dev/OpenRV/cmake-build/RV_DEPS_PYTHON3/install/libs/python39.lib;debug;C:/Program Files/Python39/libs/python39_d.lib (found suitable version "3.9.15", minimum required is "3.3")
-- PYTHON_ARCH: 64
-- CLANG: D:/Dev/OpenRV/cmake-build/RV_DEPS_PYTHON3/build/libclang/libclang, D:/Dev/OpenRV/cmake-build/RV_DEPS_PYTHON3/build/libclang/libclang/lib/libclang.lib detected by LLVM_INSTALL_DIR
-- Looking for C++ include clang-c/Index.h
-- Looking for C++ include clang-c/Index.h - found
-- Found Git: C:/msys64/usr/bin/git.exe (found version "2.38.1")
-- PYTHONLIBS_FOUND: TRUE
-- PYTHON_LIBRARIES: optimizedD:/Dev/OpenRV/cmake-build/RV_DEPS_PYTHON3/install/libs/python39.libdebugC:/Program Files/Python39/libs/python39_d.lib
-- PYTHON_INCLUDE_DIRS: D:/Dev/OpenRV/cmake-build/RV_DEPS_PYTHON3/install/include
-- PYTHON_DEBUG_LIBRARIES: C:/Program Files/Python39/libs/python39_d.lib
-- PYTHONINTERP_FOUND: TRUE
-- PYTHON_EXECUTABLE: D:/Dev/OpenRV/cmake-build/RV_DEPS_PYTHON3/install/bin/python.exe
-- PYTHON_VERSION: 3.9.15
-- PYTHON_EXTENSION_SUFFIX: .cp39-win_amd64
-- PYTHON_EXTENSION_SUFFIX: .cp39-win_amd64
-- PYTHON_CONFIG_SUFFIX: .cp39-win_amd64
-- PYTHON_SHARED_LIBRARY_SUFFIX: .cp39-win_amd64
-- Could NOT find LibXml2 (missing: LIBXML2_LIBRARY) (found suitable version "2.10.3", minimum required is "2.6.32")
-- Could NOT find LibXslt (missing: LIBXSLT_LIBRARIES) (found suitable version "1.1.37", minimum required is "1.1.19")
CMake Warning at ApiExtractor/CMakeLists.txt:82 (message):
libxslt and/or libxml not found, falling back to QtXmlPatterns
(QTBUG-66925)
-- PYTHON_NUMPY_LOCATION: C:\Users\mark\AppData\Roaming\Python\Python39\site-packages\numpy
-- SHIBOKEN_PYTHON_INCLUDE_DIRS computed to value: 'D:/Dev/OpenRV/cmake-build/RV_DEPS_PYTHON3/install/include'
-- SHIBOKEN_PYTHON_LIBRARIES computed to value: 'D:/Dev/OpenRV/cmake-build/RV_DEPS_PYTHON3/install/libs/python39.lib'
CMake Warning at doc/CMakeLists.txt:47 (message):
sphinx-build - not found! doc target disabled
-- Configuring done
This is the build error I get
cl /TP -DBUILD_LIBSHIBOKEN -DHAVE_NUMPY -DNDEBUG -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -ID:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src\sources\shiboken2\libshiboken -ID:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src\pyside3_build\py3.9-qt5.15.2-64bit-release\shiboken2\libshiboken -IC:\Users\mark\AppDa
ta\Roaming\Python\Python39\site-packages\numpy\core\include -ID:\Dev\OpenRV\cmake-build\RV_DEPS_PYTHON3\install\include /Zc:wchar_t /GR /EHsc /DWIN32 /D_WINDOWS /D_SCL_SECURE_NO_WARNINGS -D QT_NO_CAST_FROM_ASCII -D QT_NO_CAST_TO_ASCII /MD /O2 /Ob2 /DNDEBUG /FoCMakeFiles\libshiboken.dir\signature\signature_globals.cpp.
obj /FdCMakeFiles\libshiboken.dir\ /FS -c D:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src\sources\shiboken2\libshiboken\signature\signature_globals.cpp
D:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src\sources\shiboken2\libshiboken\sbknumpyarrayconverter.cpp(119): error C2065: 'NPY_ARRAY_UPDATEIFCOPY': undeclared identifier cd D:\Dev\OpenRV\cmake-build\_deps\rv_deps_pyside2-src\pyside3_build\py3.9-qt5.15.2-64bit-release\shiboken2 [D:\Dev\OpenRV\cmake-build\cma
ke\dependencies\RV_DEPS_PYTHON3-stage-target.vcxproj]
This is the macro pyside2 is using to find numpy. pysides build scripts don't appear to have option to tell it numpy's location explicitly
macro(get_numpy_location)
execute_process(
COMMAND ${PYTHON_EXECUTABLE} -c "if True:
import sys
import os
numpy = ''
for p in sys.path:
if 'site-' in p:
numpy = os.path.join(p, 'numpy')
if os.path.exists(numpy):
print(os.path.realpath(numpy))
break"
OUTPUT_VARIABLE PYTHON_NUMPY_LOCATION
OUTPUT_STRIP_TRAILING_WHITESPACE)
message(STATUS "PYTHON_NUMPY_LOCATION: " ${PYTHON_NUMPY_LOCATION})
endmacro()