-
Notifications
You must be signed in to change notification settings - Fork 358
Closed
Labels
type:bugSomething isn't workingSomething isn't working
Description
Make sure to follow our issue report guidelines
- I'm using the latest version of Natron (not required but recommended)
- I've restarted Natron and the issue persists
- I've run Natron via the command line and the issue persists
- I've followed the contributing guidelines to the best of my understanding
- My issue is not on the issue tracker or in a pull request already (go search for it and dig around a little bit!)
- This bug is reproducible
Natron version
Natron 2.5
Operating system
Windows 10
System specs
Ram: 64 Gigs
CPU: Ryzen 5600x
GPU: EVGA RTX2060
Did you install Natron using the official installer?
- Yes, I used the official installer
- No, I installed from a binary archive
- No, I compiled Natron from sources
- No, I installed Natron via another method
Custom installation path
/home/Username/src/Natron/
What were you trying to do?
I was trying to compile Natron using CMake Ninja workflow (cmake -DCMAKE_BUILD_TYPE=Debug ..) from a created build folder in Natron's repo folder, and the shiboken blender libraries evaluates to "Not Found".
Build fails after Ninja
command in the folder due to linking errors because of apparent missing Qt dependencies (if I'm understanding correctly).
What did you expect to happen? What happened instead?
I expected the debug build to succeed.
Step-by-step reproduction instructions
- Git pull Natron recursive (git clone --recursive https://github.com/NatronGitHub/Natron.git). After installing dependencies through msys2
man -S mingw-w64-x86_64-natron-build-deps-qt5
, as laid out in comment here - install cmake and ninja through pacman,
cd
to repo andmkdir Build && cd Build
- use command
cmake -DCMAKE_BUILD_TYPE=debug ..
after which you should get this output
-- SHIBOKEN_PYTHON_LIBRARIES computed to value: 'PYTHON_DEBUG_LIBRARY-NOTFOUND'
-- libshiboken built for Release
-- Configuring done (0.4s)
-- Generating done (0.2s)
ninja
command fails with linking errors.
Error output:
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/14.1.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
cannot find -lPYTHON_DEBUG_LIBRARY-NOTFOUND: No such file or directory
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
Additional details
Release build type works just fine according to the build process.
I tried to debug the cmake issue but it's a bit too complicated as I don't fully understand how Shiboken is being used.
Metadata
Metadata
Assignees
Labels
type:bugSomething isn't workingSomething isn't working