Is your feature request related to a problem? Please describe.
Whenever there is an issue with the native build, there is an additional hurdle of understanding this repo's build flow to the rapidsai/cudf developers.
It is complex enough and on top of that it is obscured in multiple Maven antrun plugin executions that are hard to read especially for users unfamiliar with Maven.
Describe the solution you'd like
Either consolidate all the cmake invocations in a single shell script and the script logs all its parameters so it is easy to run without Maven in the build container
or have some dry-run option that generates the build script.
Describe alternatives you've considered
We can document in more detail how to extract the steps from Maven debug output and reproduce each step in the build container without Maven. But I expect it to be harder than generating a bash script to run by a rapidsai engineer
Is your feature request related to a problem? Please describe. Whenever there is an issue with the native build, there is an additional hurdle of understanding this repo's build flow to the rapidsai/cudf developers. It is complex enough and on top of that it is obscured in multiple Maven antrun plugin executions that are hard to read especially for users unfamiliar with Maven.
Describe the solution you'd like Either consolidate all the cmake invocations in a single shell script and the script logs all its parameters so it is easy to run without Maven in the build container or have some dry-run option that generates the build script.
Describe alternatives you've considered We can document in more detail how to extract the steps from Maven debug output and reproduce each step in the build container without Maven. But I expect it to be harder than generating a bash script to run by a rapidsai engineer
Additional context Breaking changes in libcudf
cc @vyasr