Use toolchain resolution instead of extension

[fionera]

Currently the doxygen tool is manually defined. A better approach would be to use a toolchain

[TendTo]

Hi, thank you for the suggestion. To be bluntly honest, I chose this solution because it seemed quite simple while still satisfying all my needs, especially since the execution mainly uses only one tool, doxygen, hardly a chain.

This said, I am interested to hear in what context you think toolchains would be better. Are there features they support we are missing out on? Is the added complexity justified? Or does the architecture become even simpler?

I'm not opposed to this kind of changes in principle, but I would like to have a good understanding of the reason to do so.

[fionera]

With toolchain resolution, its way simpler to provide a custom doxygen. I quickly wrote my own implementation of these rules, as currently I cannot provide a doxygen that is built by bazel itself

[TendTo]

Wouldn't the examples/executable approach work in your case?

Regardless, if you are willing to share your implementation, either via link or pr, I'm more than interested in having a look. It may be far more elegant than the current one, and better to integrate with future features. Maybe my reticence is just due to my inexperience with bazel toolchains, which I often find over complex