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@QString@@QEBAHPEAG@Z) referenced in
> function "struct _object * __cdecl QStringRef_CppToPython_QStringRef(void
> const *)" (?QStringRef_CppToPython_QStringRef@@YAPEAU_object@@PEBX@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@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
--
Christian Tismer :^) tis...@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
signature.asc
Description: OpenPGP digital signature
_______________________________________________ PySide mailing list PySide@qt-project.org http://lists.qt-project.org/mailman/listinfo/pyside
