It seems that you're using a source from macports, which is dubious in the first place
As of commit 36e3a50 I changed the source from macports.org to qt-project.org, the new home for PySide releases. I used the (temporary) source from macports because at that time pyside.org was inaccessible, the change (and the reason for it) to macports can be found in the commit message of commit 4d2625d.
it also seems that you're not properly setting the pkgbuild to build for Py2. Not sure if that is necessary on the mainline shiboken package or not, but it's building for me with 3.3 despite the depends claiming it needs python2, and NOT python.
This in turn makes your manual install commands after cd generator fail, as this:
install -D -m 755 ../data/ShibokenConfig-python${_pyver}.cmake $pkgdir/usr/lib/cmake/Shiboken-$pkgver/
doesn't match a built file.
Here's the *.cmake files that get generated by your PKGBUILD on my machine:
$ find . -name ShibokenConfig* ./build/data/ShibokenConfigVersion.cmake ./build/data/ShibokenConfig.cpython-33m.cmake ./build/data/ShibokenConfig.cmake ./data/ShibokenConfigVersion.cmake.in ./data/ShibokenConfig.cmake.in ./data/ShibokenConfig-spec.cmake.in
When you have python2 and python (Python 3x) installed on your system my pkgbuild should generate the python2-shiboken-{VERSIONHERE}.pkg.tar.xz file before python-shiboken-{VERSIONHERE}.pkg.tar.xz.
So when the build finished the remaining files was generated by the python 3 build, that's why when you use find after the build you will get something like ShibokenConfig.cpython-33.cmake and not ShibokenConfig-python2.7.cmake. I think that should be the case here.
This is a screenshot of my build, finished just now on my computer:
Well, if you DO have python2 and yet you cant find any python2-shiboken-{VERSIONHERE}.pkg.tar.xz (and shiboken-common-{VERSIONHERE}.tar.xz), (or if you have any other problem with my PKGBUILDs) please let me know.
Thank you.
]]>This in turn makes your manual install commands after cd generator fail, as this:
install -D -m 755 ../data/ShibokenConfig-python${_pyver}.cmake $pkgdir/usr/lib/cmake/Shiboken-$pkgver/
doesn't match a built file.
Here's the *.cmake files that get generated by your PKGBUILD on my machine:
$ find . -name ShibokenConfig*
./build/data/ShibokenConfigVersion.cmake
./build/data/ShibokenConfig.cpython-33m.cmake
./build/data/ShibokenConfig.cmake
./data/ShibokenConfigVersion.cmake.in
./data/ShibokenConfig.cmake.in
./data/ShibokenConfig-spec.cmake.in
It seems everything work as it should be, at least it does on my end, are you sure you have installed the python2-shiboken-1.1.2-1-$ARCH.pkg.tar.xz?
I'm sorry for such late reply, but I would like to know what is the problem. Thank you.
]]>Yeah I also notice that the PySide project seems to be in a state of confusion. The web pages are obviously way out of date, and they can't even keep their download links working. I sure hope they can get things together shortly after Qt5 comes out -- this will really rock!
]]>Worked like a champ, thanks much!
I'd sure love this to make it into Arch proper. I suppose for that to happen would require a significant project to be built with it, not? I suppose it's just a matter of time until that happens.
You're welcome.
It seems like PySide, like many Qt-related projects, is in a transition state, with the change in corporate backing from Nokia to Digia some projects are being put on back seat at least until Qt (the main C++ project) settle down. I might be wrong but that is the impression that I get. Progress is slow, and much of the developers focus is on Qt moving towards Qt 5 so we might have a different PySide soon.
I can't blame the ArchLinux maintainers to see that it need to "settle down" a bit and get some big projects to use it. I also haven't seen any noteworthy open-source project(s) using PySide to justify its adoption anyway. So yes I would love to see it in Arch's community/extra repo but I'm realistic.
]]>I'd sure love this to make it into Arch proper. I suppose for that to happen would require a significant project to be built with it, not? I suppose it's just a matter of time until that happens.
]]>Question: when Python 3.3 is pushed out, is this all going to break? If so, will simply re-building the packages fix it? Or will we need to wait for updated scripts from arlx?
I tried to build python-pyside, but I can't get it working. I used the one from aur as base but changed the url (I used a mirror: https://distfiles.macports.org/py-pyside/) as pyside.org is no longer online. I also tried to change version to the latest (1.1.2), which didn't make any difference.
==> Starting build()... -- Using default python: .cpython-32mu -- libshiboken built for Release -- Detected OS: x11 CMake Error at CMakeLists.txt:148 (message): Could not detect Python module installation directory. -- Configuring incomplete, errors occurred!
Why it's using .cpython-32mu as my Python is now 3.3? Is that the reason it's failing. Right now I'm using VirtualBox and Ubuntu to do my work, but it'd nice to use Arch on bare-metal.
I also would like to get python-pysqlite which was recently replaced by python2-pysqlite (probably belongs to another discussion)(sqlite3 != pysqlite)
It seems the PySide developers still uses Python 3.2. If you look at the shiboken CMake file that is responsible for python interpreter lookup at line 30, the last time I look at it (ie. just now, today), they use a simple lookup loop up to "3.2".
The solution for this if you are using Python 3.3 is to add a "3.3" on this line, for example:
FOREACH(_CURRENT_VERSION 3.3 3.2 3.1 3.0)
and rebuild by running:
$ makepkg -e -f
on the shiboken/ directory, after that one should also rebuild and re-install pyside and pyside-tools to use the new shiboken for python 3.3. Unfortunately this small change is neccessary at least until the upstream developers add support for Python 3.3 too.
I made a small patch for shiboken PKGBUILD to automate this, I have also make changes on all PKGBUILDs to download files from the macports.org mirror because the pyside.org is unavailable at this moment. Feel free to clone/pull latest changes from the repository.
]]>==> Starting build()...
-- Using default python: .cpython-32mu
-- libshiboken built for Release
-- Detected OS: x11
CMake Error at CMakeLists.txt:148 (message):
Could not detect Python module installation directory.
-- Configuring incomplete, errors occurred!
Why it's using .cpython-32mu as my Python is now 3.3? Is that the reason it's failing. Right now I'm using VirtualBox and Ubuntu to do my work, but it'd nice to use Arch on bare-metal.
I also would like to get python-pysqlite which was recently replaced by python2-pysqlite (probably belongs to another discussion) (sqlite3 != pysqlite)
Thanks for the packages! Wish they would get integrated into Arch proper - this seems like a really important project for the future.
]]>-- Found Qt4: /usr/bin/qmake (found suitable version "4.8.3", required is "4.5.0")
-- Detected OS: x11
CMake Error at CMakeLists.txt:148 (message):
Could not detect Python module installation directory.
-- Configuring incomplete, errors occurred!
==> ERROR: A failure occurred in package_python2-pyside().
Aborting...
Anyone know how to get around this?
]]>Anyway, I just update the PKGBUILD for pyside-tools 0.2.14 .
]]>