Support verbose output via --subcommands

[attilaolah]

trafficstars

It would be nice if the entire configure / make / cmake output would be passed to the standard output when the Bazel --subcommands flag is set, to make debugging easier.

Specifically, because sometimes what I'm trying to do is figure out what are the right flags or cache entries for the build to pick up my dependencies, which can be lots of trial-and-error. If it is an optional dependency, the build process would continue, building the entire library without my dependency, and I have to wait it out so that I could look at the build log.

If I could see the output early, I could cancel the build and retry with different flags.

---

If there is already some way to do this, maybe I just missed it, it would be nice then to document it somewhere more visible.

[xiedeacc]

+1

[jheaff1]

While not ideal, my method is to view the build log generated by rules_foreign_cc while it is building. You can find the log in the bowels of the Bazel build folders. Something like bazel-out/k8-fastbuild/…..

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days. Collaborators can add an assignee to keep this open indefinitely. Thanks for your contributions to rules_foreign_cc!

[stephane-caron]

Same need here. The trick works: a CMake.log file is produced afterwards, but only afterwards the build is over. Since it fails in my case, and the build takes 8-10 minute to complete, being able to track subcommands would help a bunch.

[jheaff1]

Same need here. The trick works: a CMake.log file is produced afterwards, but only afterwards the build is over. Since it fails in my case, and the build takes 8-10 minute to complete, being able to track subcommands would help a bunch.

A log file is generated during the build within the Linux/MacOS sandbox, which will be in ~/.cache/bazel of default Bazel settings are used. You could do a find -name CMake.log within that directory to find the log file during the build, then tail the file