Skip to content

Conversation

@merlimat
Copy link
Contributor

Motivation

Ensure the CMake preparation fails when the correct Boost-Python library is not found. With the current behavior, the build goes through even when not found, and then the resulting _pulsar.so will not be linked with boost-python and will fail to load at runtime.

@merlimat merlimat added the type/bug The PR fixed a bug or issue reported a bug label Sep 19, 2018
@merlimat merlimat added this to the 2.2.0-incubating milestone Sep 19, 2018
@merlimat merlimat self-assigned this Sep 19, 2018
@merlimat
Copy link
Contributor Author

run cpp tests

@merlimat merlimat merged commit d536d66 into apache:master Sep 20, 2018
@merlimat merlimat deleted the py-build-fix branch September 20, 2018 00:03
Comment on lines +51 to +54
if (APPLE)
set(PYTHON_WRAPPER_LIBS ${PYTHON_WRAPPER_LIBS}
${Boost_PYTHON27-MT_LIBRARY_RELEASE} ${Boost_PYTHON37-MT_LIBRARY_RELEASE})
endif()
Copy link
Contributor

Choose a reason for hiding this comment

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

Recently I found some build issues like #11747. It's caused by Boost_<component>-MT_LIBRARY_RELEASE is set with Boost_<component>-MT_LIBRARY_RELEASE-NOTFOUND and added to PYTHON_WRAPPER_LIBS.

Could you explain why this line is needed for macOS? @merlimat

Copy link
Contributor

Choose a reason for hiding this comment

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

BTW, here is a fix: #13193. But IMO these code could be removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type/bug The PR fixed a bug or issue reported a bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants