Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Ensure PYTHONQT_USE_RELEASE_PYTHON_FALLBACK works as expected. #4

Open
jcfr opened this issue Mar 27, 2012 · 1 comment
Open

Ensure PYTHONQT_USE_RELEASE_PYTHON_FALLBACK works as expected. #4

jcfr opened this issue Mar 27, 2012 · 1 comment
Assignees
@jcfr

Comments

@jcfr
Copy link
Member

jcfr commented Mar 27, 2012

See #3
@ghost ghost assigned jcfr Mar 27, 2012
@jcfr
Copy link
Member Author

jcfr commented Jul 10, 2012

From @jeinarsson

I compiled Python 2.7.2 + Qt 4.8 PythonQt from this repo with msvc2008. To get Debug mode
 working (that is, not mixing runtimes and crashing), I had to remove the hack in dPython.h 
completely, and link to python27_d.lib manually. I guess this is what 
PYTHONQT_USE_RELEASE_PYTHON_FALLBACK will fix in the future.

I don't understand all of the dependencies.. I got Release mode working via the QtCreator 
project, but the Debug project keeps complaining about the python library thus far..
EDIT: Using Qt Creator for the extension actually worked out now.. However, naming the 
debug lib PythonQt_d.lib and putting it all into CMake would be nice. If I manage I'll ping 
you again...

@patmarion patmarion mentioned this issue Sep 4, 2015
Closed
@espakm espakm mentioned this issue Feb 18, 2016
Open
jmirabel added a commit to jmirabel/PythonQt that referenced this issue Nov 15, 2019
@jmirabel
Merge pull request commontk#4 from jmirabel/qt5
452b8cf 
Remove matplotlib backend.
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@jcfr jcfr

Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jcfr