Taiki Endo

> Do you think it's still worth adding it formally Yeah, it would still be worth it because the officially supported tools have somehhow better installation performance and robustness.

Thanks! > Key question atm is whether it is OK to add new fields `website` & `license_markdown` to both the base info and manifest structs. I'm okay with adding those...

> Is it ok to generate as `TOOLS.md` , and link to it from `README.md`? IMO the list is already getting long. I dont mind merging it into the README.md...

> IIUC, the CI loops over each tool, in which case putting the markdown generation in the `main.rs` will mean it does that step many times - once per tool,...

This action uses [cross](https://github.com/cross-rs/cross) to cross-compile by default, and the [cross wiki has a section on openssl](https://github.com/cross-rs/cross/wiki/FAQ#openssl-is-not-installed). Probably the easiest way is to enable the `vendored` feature of `openssl` crate.

Because of the [feature unification](https://doc.rust-lang.org/stable/cargo/reference/features.html#feature-unification), it will work even if you add `openssl` with `vendored` feature enabled as a dependency of your crate. Also, I think another way that might...

Hmm, is it possible to use the way that doesn't use openssl (i.e., use rustls)?.

> Adding vendored breaks the windows build actually. It is actually quite odd that it is failing though, since tarpaulin can build with this action and vendored feature enabled openssl...

@davincios Your issue sounds like a bug in your code, not an openssl-related problem. Please submit a new issue with complete information (e.g., link to the repository) on the actual...

> error: could not find `Cargo.toml` in `/home/runner/work/my-repo/my-repo` or any parent directory I believe you have to use `manifest-path` input option. (If you use this action outside of the cargo...