Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

compilation stops with [Parse error at "BOOST_JOIN"] with QT4.8 and Boost 1.53 #93

Closed
mark-orion opened this issue Jul 30, 2013 · 4 comments
Labels
Milestone

Comments

@mark-orion
Copy link

GQRX does not compile on "pre QT5" systems with Boost versions higher than 1.47. The reason is a known QT bug QTBUG-22829 where moc has trouble with certain boost headers. The workaround is to make the critical headers invisible to MOC:
Example:

ifndef Q_MOC_RUN

include <boost/python.hpp>

endif

Details of the bug can be found here: https://bugreports.qt-project.org/browse/QTBUG-22829
I would like to request this fix as the latest Pybombs based gnuradio build system is based on Boost 1.53 and provides a build recipe for GQRX that sadly does not work due to this bug.

@csete
Copy link
Collaborator

csete commented Jul 30, 2013

Thanks for the analysis. I encountered this very same issue yesterday but I thought it was because of conflicting boost installations. I will try to fix this ASAP.

@ghost ghost assigned csete Jul 30, 2013
csete added a commit that referenced this issue Jul 30, 2013
@csete
Copy link
Collaborator

csete commented Jul 30, 2013

So, I made a fix as per your suggestion and it works for me now using Qt 4.8.1. Can you confirm that it works for you too?

@mark-orion
Copy link
Author

I can confirm that it builds and works fine now. I tested it on two
machines, both work. Thanks for the quick fix and this great program in
general.

On 31/07/13 00:07, Alexandru Csete wrote:

So, I made a fix as per your suggestion and it works for me now using
Qt 4.8.1. Can you confirm that it works for you too?


Reply to this email directly or view it on GitHub
#93 (comment).

@csete
Copy link
Collaborator

csete commented Jul 31, 2013

Thanks for the feedback. I'm glad we could fix it now as I am about to package version 2.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants