-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
ARROW-17632: [Python][C++] Add details of where libarrow is being found during build #14059
ARROW-17632: [Python][C++] Add details of where libarrow is being found during build #14059
Conversation
cpp/src/arrow/ArrowConfig.cmake.in
Outdated
message(STATUS "Found the Arrow core shared library: ${ARROW_SHARED_LIB}") | ||
message(STATUS "Found the Arrow core import library: ${ARROW_IMPORT_LIB}") | ||
message(STATUS "Found the Arrow core static library: ${ARROW_STATIC_LIB}") | ||
endif() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you define a function arrow_show_details(package_name)
or something that shows these status messages and use it in all *Config.cmake.in
?
cpp/src/arrow/ArrowConfig.cmake.in
Outdated
if(NOT ${PACKAGE_NAME}_FIND_QUIETLY) | ||
string(TOUPPER ${PACKAGE_NAME} package_name_upper) | ||
message(STATUS "${PACKAGE_NAME} version: ${${package_name_upper}_VERSION}") | ||
message(STATUS "Found the ${PACKAGE_NAME} shared library: ${${package_name_upper}_SHARED_LIB}") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this work with ArrowDataset
?
It seems that we need to pass 2 arguments to this function: arrow_show_details(package_name variable_prefix)
(e.g.: arrow_show_details(ArrowDataset ARROW_DATASET)
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The signature now is macro(arrow_show_details package_name variable_prefix)
, but does it make sense to use target_base_name
instead of variable_prefix
as in arrow_keep_backward_compatibility
, and do something like:
macro(arrow_show_details package_name target_base_name)
string(TOUPPER ${target_base_name} target_base_name_upper)
.
.
.
endmacro()
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
Benchmark runs are scheduled for baseline = f42f3df and contender = 3aee08b. 3aee08b is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
…nd during build (apache#14059) This PR aims to add back `message(STATUS ...)` statements that printed some details about Arrow being found, its version, and the paths. These were refactored away as part of apache#13892. Authored-by: Dhruv Vats <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
…nd during build (apache#14059) This PR aims to add back `message(STATUS ...)` statements that printed some details about Arrow being found, its version, and the paths. These were refactored away as part of apache#13892. Authored-by: Dhruv Vats <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
This PR aims to add back
message(STATUS ...)
statements that printed some details about Arrow being found, its version, and the paths. These were refactored away as part of #13892.