I use vs2013 x64 build
and added DEFINES += PYTHONQT_USE_RELEASE_PYTHON_FALLBACK
the release build successed, but debug build has lnk error
PythonQt.obj:-1: error: LNK2019: unresolved external symbol impinvalid_parameter_noinfo_noreturn referenced in function "public: int const & __cdecl std::_Vector_const_iterator<class std::_Vector_val<struct="" std::_Simple_types<int=""> > >::operator*(void)const " (??D?$_Vector_const_iterator@V?$_Vector_val@U?$_Simple_types@H@std@@@std@@@std@@QEBAAEBHXZ)
by the way, I have successful built both debug and release in r371, but failed in later code
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Got the same issues.
Reason for the use of the python release build for me is that i want to use a python dll from a binary distribution (e.g. Anaconda) and the modules compiled for it instead of providing debug variants of all those modules.
I solved the issues this way:
1) in Anaconda pyconfig.h i had to use the PYTHONQT_USE_RELEASE_PYTHON_FALLBACK define also to link agaings python35.lib instead of python35_d.lib
2) i had to link against msvcrt (microsoft release runtime instead of debug) due to the release python
3) in PythonQt::setupSharedLibrarySuffixes() my application crashed.
So i hardcoded this function to get the extension (pyd)
found no proper solution yet. But my applications runs so far....
Error seems to come from the using different vs versions for the release python dll and my current local version...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I use vs2013 x64 build
and added DEFINES += PYTHONQT_USE_RELEASE_PYTHON_FALLBACK
the release build successed, but debug build has lnk error
PythonQt.obj:-1: error: LNK2019: unresolved external symbol impinvalid_parameter_noinfo_noreturn referenced in function "public: int const & __cdecl std::_Vector_const_iterator<class std::_Vector_val<struct="" std::_Simple_types<int=""> > >::operator*(void)const " (??D?$_Vector_const_iterator@V?$_Vector_val@U?$_Simple_types@H@std@@@std@@@std@@QEBAAEBHXZ)
by the way, I have successful built both debug and release in r371, but failed in later code
I had exactly the same when I tried a Python which was built with VS2013. This worked fine with a Python built with 2010.
I finally resorted to building a debug version of Python itself (3.4.1) and linking against that in debug mode. :-(
Mixing a debug Python and release PythonQt is always tricky on Windows.
If you google for it, you might find useful links on stackoverflow.
I think building a debug Python is the better solution in the long run.
Last edit: Florian Link 2015-02-11
Hi!
Got the same issues.
Reason for the use of the python release build for me is that i want to use a python dll from a binary distribution (e.g. Anaconda) and the modules compiled for it instead of providing debug variants of all those modules.
I solved the issues this way:
1) in Anaconda pyconfig.h i had to use the PYTHONQT_USE_RELEASE_PYTHON_FALLBACK define also to link agaings python35.lib instead of python35_d.lib
2) i had to link against msvcrt (microsoft release runtime instead of debug) due to the release python
3) in PythonQt::setupSharedLibrarySuffixes() my application crashed.
So i hardcoded this function to get the extension (pyd)
found no proper solution yet. But my applications runs so far....
Error seems to come from the using different vs versions for the release python dll and my current local version...