From tismer at stackless.com Sat Oct 3 20:28:38 2015 From: tismer at stackless.com (Christian Tismer) Date: Sat, 3 Oct 2015 20:28:38 +0200 Subject: [PySide] Gone! (was: PySide 2.0.0.dev0 build issue) In-Reply-To: <901E34AC-B294-4C85-ADD5-8D3C68CEEE76@stackless.com> References: <55E7613F.6030809@comcast.net> <55E888DE.8020009@comcast.net> <55E92038.8060703@stackless.com> <901E34AC-B294-4C85-ADD5-8D3C68CEEE76@stackless.com> Message-ID: <56101E56.5070905@stackless.com> Howdy, the windows build issue is gone. There is still a flaw in 'jom', but I have worked around that in cmake. Also, PySide2 builds on Windows with Qt5.3 - Qt5.5 . I am starting now to integrate some fixes from helpers that will make PySide2 much more into a beta, soon ;-) cheers -- Chris On 04/09/15 07:20, Christian Tismer wrote: > Please replace "beneath" by "besides". Where you find the shiboken > folder, create some file "shiboken-skip". > > Sent from my iPad > > On 04 Sep 2015, at 06:38, Christian Tismer > wrote: > >> Hi, >> >> but you know that this is not ready for use, yet? >> Don't use install, use >> >> python setup.py develop --ignore-git --qmake=... >> >> The problems that you have are known, and right now I have the following >> work-arounds: >> >> 1. Yom problem: >> >> This only happens on Windows, and I don't know the reason, yet. >> but this works (hackish): >> >> Do a build without yom, but kill the job as soon as shiboken is built. >> Then, create a file in the pyside-build dir named "shiboken-off", >> right beneath >> the subfolder "shiboken". >> >> Then start the same build command with yom. This time, setup.py will skip >> the faulty shiboken part. >> >> 2. Link problem: >> >> This is a known problem that was also existent on Pyside 1.2.2/Qt4.8. >> For some reason, the Pyside devs decided in 2010 to add the option >> "/Zc:wchar_t-". On windows, that means that you have to build your own >> Qt5, >> which takes many hours. >> >> For the moment, you can switch to the branch "qt5-win-fix" and build >> again. >> >> In any case, there are still some serious problems that are a showstopper >> for any use, because internal protocols are not completely adjusted. >> For instance, the implementation of dynamicmetaobject.cpp ist >> completely broken, >> and this crashes any instantiation of a widget. >> >> I am currently in the debugging phase and can use a lot of help. >> >> Cheers - Chris >> >> >> On 03.09.15 19:52, Bob Hood wrote: >>> On 9/2/2015 9:48 PM, E Smitty wrote: >>>> Well, did you compile Python 2.7.9 yourself? Because it is >>>> incompatible with extensions compiled with Visual Studio 2013. >>> >>> Well, that was certainly something that might have caused a problem, >>> but it wasn't causing these specific issues. Using Python 2.7.10 >>> built using VS2013, I still get the error about a "doc" target when >>> using jom: >>> >>> ... >>> [100%] Built target shibokenmodule >>> Generating Shiboken documentation shiboken... >>> Running process: E:\jom_1_0_16\jom.exe doc >>> Error: Target doc doesn't exist. >>> error: Error generating documentation shiboken >>> >>> and the link error when I switch back to "nmake": >>> >>> Linking CXX shared module ..\QtCore.pyd >>> Creating library QtCore.lib and object QtCore.exp >>> >>> qtcore_module_wrapper.cpp.obj : error LNK2019: unresolved >>> external symbol >>> "__declspec(dllimport) public: int __cdecl QString::toWCharArray(unsigned >>> short *)const " (__imp_?toWCharArray at QString@@QEBAHPEAG at Z) referenced in >>> function "struct _object * __cdecl QStringRef_CppToPython_QStringRef(void >>> const *)" (?QStringRef_CppToPython_QStringRef@@YAPEAU_object@@PEBX at Z) >>> >>> ..\QtCore.pyd : fatal error LNK1120: 1 unresolved externals >>> >>> Does anybody know what specific version of Qt PySide 2.0.0.dev0 is >>> only developed against? This particular method >>> (QString::toWCharArray) has exactly the same signature in both Qt >>> 5.4.2 and 5.5.0, so there wasn't a change between those two versions. >>> >>> >>> >>> _______________________________________________ >>> PySide mailing list >>> PySide at qt-project.org >>> http://lists.qt-project.org/mailman/listinfo/pyside >> >> >> -- >> Christian Tismer :^) tismer at stackless.com >> Software Consulting : http://www.stackless.com/ >> Karl-Liebknecht-Str. 121 : https://github.com/PySide >> 14482 Potsdam : GPG key -> 0xFB7BEE0E >> phone +49 173 24 18 776 fax +49 (30) 700143-0023 >> _______________________________________________ >> PySide mailing list >> PySide at qt-project.org >> http://lists.qt-project.org/mailman/listinfo/pyside > > > _______________________________________________ > PySide mailing list > PySide at qt-project.org > http://lists.qt-project.org/mailman/listinfo/pyside > -- Christian Tismer :^) tismer at stackless.com Software Consulting : http://www.stackless.com/ Karl-Liebknecht-Str. 121 : https://github.com/PySide 14482 Potsdam : GPG key -> 0xFB7BEE0E phone +49 173 24 18 776 fax +49 (30) 700143-0023 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 522 bytes Desc: OpenPGP digital signature URL: From bhood2 at comcast.net Sat Oct 3 22:50:50 2015 From: bhood2 at comcast.net (Bob Hood) Date: Sat, 3 Oct 2015 14:50:50 -0600 Subject: [PySide] Gone! In-Reply-To: <56101E56.5070905@stackless.com> References: <55E7613F.6030809@comcast.net> <55E888DE.8020009@comcast.net> <55E92038.8060703@stackless.com> <901E34AC-B294-4C85-ADD5-8D3C68CEEE76@stackless.com> <56101E56.5070905@stackless.com> Message-ID: <56103FAA.8070608@comcast.net> Excellent! Thanks for the update, Chris. :) On 10/3/2015 12:28 PM, Christian Tismer wrote: > Howdy, > > the windows build issue is gone. > There is still a flaw in 'jom', but I have worked around that in cmake. > > Also, PySide2 builds on Windows with Qt5.3 - Qt5.5 . > > I am starting now to integrate some fixes from helpers that will make > PySide2 much more into a beta, soon ;-) > > cheers -- Chris > > > On 04/09/15 07:20, Christian Tismer wrote: >> Please replace "beneath" by "besides". Where you find the shiboken >> folder, create some file "shiboken-skip". >> >> Sent from my iPad >> >> On 04 Sep 2015, at 06:38, Christian Tismer > > wrote: >> >>> Hi, >>> >>> but you know that this is not ready for use, yet? >>> Don't use install, use >>> >>> python setup.py develop --ignore-git --qmake=... >>> >>> The problems that you have are known, and right now I have the following >>> work-arounds: >>> >>> 1. Yom problem: >>> >>> This only happens on Windows, and I don't know the reason, yet. >>> but this works (hackish): >>> >>> Do a build without yom, but kill the job as soon as shiboken is built. >>> Then, create a file in the pyside-build dir named "shiboken-off", >>> right beneath >>> the subfolder "shiboken". >>> >>> Then start the same build command with yom. This time, setup.py will skip >>> the faulty shiboken part. >>> >>> 2. Link problem: >>> >>> This is a known problem that was also existent on Pyside 1.2.2/Qt4.8. >>> For some reason, the Pyside devs decided in 2010 to add the option >>> "/Zc:wchar_t-". On windows, that means that you have to build your own >>> Qt5, >>> which takes many hours. >>> >>> For the moment, you can switch to the branch "qt5-win-fix" and build >>> again. >>> >>> In any case, there are still some serious problems that are a showstopper >>> for any use, because internal protocols are not completely adjusted. >>> For instance, the implementation of dynamicmetaobject.cpp ist >>> completely broken, >>> and this crashes any instantiation of a widget. >>> >>> I am currently in the debugging phase and can use a lot of help. >>> >>> Cheers - Chris >>> >>> >>> On 03.09.15 19:52, Bob Hood wrote: >>>> On 9/2/2015 9:48 PM, E Smitty wrote: >>>>> Well, did you compile Python 2.7.9 yourself? Because it is >>>>> incompatible with extensions compiled with Visual Studio 2013. >>>> Well, that was certainly something that might have caused a problem, >>>> but it wasn't causing these specific issues. Using Python 2.7.10 >>>> built using VS2013, I still get the error about a "doc" target when >>>> using jom: >>>> >>>> ... >>>> [100%] Built target shibokenmodule >>>> Generating Shiboken documentation shiboken... >>>> Running process: E:\jom_1_0_16\jom.exe doc >>>> Error: Target doc doesn't exist. >>>> error: Error generating documentation shiboken >>>> >>>> and the link error when I switch back to "nmake": >>>> >>>> Linking CXX shared module ..\QtCore.pyd >>>> Creating library QtCore.lib and object QtCore.exp >>>> >>>> qtcore_module_wrapper.cpp.obj : error LNK2019: unresolved >>>> external symbol >>>> "__declspec(dllimport) public: int __cdecl QString::toWCharArray(unsigned >>>> short *)const " (__imp_?toWCharArray at QString@@QEBAHPEAG at Z) referenced in >>>> function "struct _object * __cdecl QStringRef_CppToPython_QStringRef(void >>>> const *)" (?QStringRef_CppToPython_QStringRef@@YAPEAU_object@@PEBX at Z) >>>> >>>> ..\QtCore.pyd : fatal error LNK1120: 1 unresolved externals >>>> >>>> Does anybody know what specific version of Qt PySide 2.0.0.dev0 is >>>> only developed against? This particular method >>>> (QString::toWCharArray) has exactly the same signature in both Qt >>>> 5.4.2 and 5.5.0, so there wasn't a change between those two versions. >>>> >>>> >>>> >>>> _______________________________________________ >>>> PySide mailing list >>>> PySide at qt-project.org >>>> http://lists.qt-project.org/mailman/listinfo/pyside >>> >>> -- >>> Christian Tismer :^) tismer at stackless.com >>> Software Consulting : http://www.stackless.com/ >>> Karl-Liebknecht-Str. 121 : https://github.com/PySide >>> 14482 Potsdam : GPG key -> 0xFB7BEE0E >>> phone +49 173 24 18 776 fax +49 (30) 700143-0023 >>> _______________________________________________ >>> PySide mailing list >>> PySide at qt-project.org >>> http://lists.qt-project.org/mailman/listinfo/pyside >> >> _______________________________________________ >> PySide mailing list >> PySide at qt-project.org >> http://lists.qt-project.org/mailman/listinfo/pyside >> > From nigel at cresset-group.com Wed Oct 28 17:17:22 2015 From: nigel at cresset-group.com (Nigel Palmer) Date: Wed, 28 Oct 2015 16:17:22 +0000 Subject: [PySide] shiboken error on function with return type QList Message-ID: Hi all I am trying to generate bindings using shiboken for a simple class but I am having the following error when shiboken parses a function which returns a QList. "Could not find a minimal constructor for type 'QByteArray'. This will result in a compilation error." Below is the header which is causing the error and type system file bytearraytest.h #ifndef BYTEARRAYTEST_H #define BYTEARRAYTEST_H #include #include class ByteArrayTest { public: ByteArrayTest(); QList byteArrayList(); }; #endif // BYTEARRAYTEST_H typesystem.xml

Any ideas? I am using PySide 1.2.2 with Python 2.7.10 and Qt 4.8.7 Many Thanks Nigel -------------- next part -------------- An HTML attachment was scrubbed... URL: From kenspicer at comcast.net Sat Oct 31 14:43:57 2015 From: kenspicer at comcast.net (Ken Spicer) Date: Sat, 31 Oct 2015 09:43:57 -0400 Subject: [PySide] missing pyside-config.cmake after building and installing pyside Message-ID: <5634C59D.9050405@comcast.net> Hi everybody, I have successfully built and installed PySide on an OpenSUSE13.1 system and am attempting to install 'FreeCAD' on the same system. The 'FreeCAD' installation fails because it cannot find a pyside-config.cmake. In reviewing previous pyside changes and bugs I found the following reference to a supposedly fixed pyside bug: 1052 PySideConfig.cmake contains an infinite loop due to missing default for SHIBOKEN_PYTHON_SUFFIX Is this something that could prevent the 'pyside-config.cmake' file from being generated? Anyway, could someone help me to get or find the missing file? Thanks for your help. Yours, Ken