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

fix qt4 conflict with boost #795

Open
wants to merge 1 commit into
base: production
Choose a base branch
from

Conversation

lianghongzhuo
Copy link
Contributor

This pull request contains two prats: some fix from @cielavenir and qt4 conflict with boost
For the qt4 and boost conflict, you can see here as a reference.
LARG/HFO#79 (comment)

@cielavenir
Copy link
Collaborator

cielavenir commented May 11, 2020

@cielavenir
Copy link
Collaborator

@lianghongzhuo force PythonInterp to 2 exists only for testing. It is not for mainstream.

@cielavenir
Copy link
Collaborator

@lianghongzhuo actually I recommend you to resubmit pull request only using qt4 guy (here 67aa72d)

@lianghongzhuo
Copy link
Contributor Author

lianghongzhuo commented May 11, 2020

@cielavenir Sorry, I didn't know you already submit your commits.

  1. I will modify this pull request that only leave qt4 commits.
  2. Keep all commits in this pull request and revise if needed.
    which one do you prefer?

@cielavenir
Copy link
Collaborator

cielavenir commented May 12, 2020

@lianghongzhuo sorry if I misunderstand what you mean, but please force-push 67aa72d on the branch-point of your branch, removing other commits

@lianghongzhuo
Copy link
Contributor Author

OK

@lianghongzhuo lianghongzhuo changed the title some fix from cielavenir and qt4 conflict with boost fix qt4 conflict with boost May 12, 2020
@lianghongzhuo
Copy link
Contributor Author

I think it looks better now. :)

@@ -28,7 +28,12 @@ if (QT_FOUND AND QT_QTCORE_FOUND AND QT_QTGUI_FOUND AND SOQT_LIBRARY_FOUND AND C
qt4_wrap_cpp(MOC_OUTPUT_FILES ${QTCOIN_MOCS})

check_include_file(X11/Xlib.h HAVE_X11_XLIB_H)

if (Boost_MINOR_VERSION LESS 65)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are you sure you don't have to test Boost MAJOR version here to be 1? For example, in the future Boost 2 might come out, then all this code will be invalid.
thanks

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

Successfully merging this pull request may close these issues.

3 participants