/mingw64/lib/pkgconfig/pyside-py2.pc
was indeed installed, but the problem came from Shiboken.
$ pkg-config --libs pyside-py2
Package shiboken was not found in the pkg-config search path.
Perhaps you should add the directory containing `shiboken.pc'
to the PKG_CONFIG_PATH environment variable
Package 'shiboken', required by 'pyside-py2', not found
So I did the same for shiboken: pacman -Ql mingw-w64-x86_64-python2-shiboken-qt4
. Turns out that the package contains a shiboken-py2.pc
but no shiboken.pc
and PySide expects the latter. I read tools/MINGW-packages/mingw-w64-pyside-qt4
and I can see in it that any reference to shiboken in PySide package should be rename into shiboken-py2. So I apparently have an inconsistency between my shiboken and pyside packages, one coming from custom repos and not the other one or something like this. I ended up dirty patching my system:
ln -s /mingw64/lib/pkgconfig/shiboken-py2.pc /mingw64/lib/pkgconfig/shiboken.pc
But I’m not happy with it. It’s not something I can release officially in a building How To.
Anyway, I kept on going, and ran qmake
. It was not clear which config I should use, since most of them were plotting a warning saying they are designed to be ran at Inria. In particular, I did not manage to set an installation target. Which qmake options would you recommend for an optimized release-like build?
For now I build in the defautl devel mode, and specify an installation path:
qmake -r target.path=/e/SourceCode/Natron/bin
This now runs well, so I go for make
then. But at linking time I ran into this issue: Alexpux’ MINGW-packages #1670, with pyside package. But greping my system for some mention to C:\building
did not return anything else than the makefiles generated by qmake. So I manually edited those in order to keep going, but again it’s not something I could advise anybody to do.
After that, the make
ended correctly. So I ran make install
, and checked out my install dir. There were only three elements in it:
Natron.exe
natron-python.exe
NatronRenderer.exe
I copied the libgcc dll it was asking for, but then could not start any of those exe: