eli-schwartz commented on issue #45853: URL: https://github.com/apache/arrow/issues/45853#issuecomment-2734956196
No, reconfiguring presumes that the build is stale and something should be changed (possibly forcing different compiler command lines to be produced). I would expect, if it says "directory already configured", that nothing should be recompiled unless the source modification timestamp has changed. > I do also see warnings about wraps being out of date, if those would contribute to the issue: This warning sounds odd, have the subprojects/*.wrap files actually been modified (and how)? The main reason you'd care about the warning is if you have manually edited a wrap file to change e.g. a wrap-git commit version, as without explicitly running `meson subprojects update --reset` meson may think the subproject is already available and not try running git commands to change the version in use. Also, if you've modified the wrap files to add diff_files, similar logic applies. It should in this case have no bearing on whether ninja is forcing existing (we hope unchanged) files to be recompiled erroneously. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
