* ci: test if building with musl on Rust > 1.71 works again
* use cross instead?
* specify cross version to fix build issue
* Update build_releases.yml
* ci: add a build check for aarch64-linux-android
* appease clippy
* use 1.67.0 for Android due to NDK issue
* remove sparse since it is default now for 1.70 and causes issues with older versions anyway
Since I have a macOS M1 laptop to test on now, I think it's a good time
to bump it to be officially supported, especially since it's going
to be the main macOS platform for the foreseeable feature.
* ci: switch deb nightly builds back to the same string as normal
Easier to stay consistent, I guess.
* disable cache for cargo deb
* reenable cache
* nvm
This adds the build hash to the btm -V output for nightly builds, making it easier to troubleshoot when someone might have obtained a nightly build, and what commit it corresponds to.
This automatically triggers and grabs the build artifacts for systems that are only supported on Cirrus CI (as of now, FreeBSD and M1 macOS).
* ci: add cirrus build trigger script
* ci: modify build scripts to include cirrus build
* fix some stuff
* update docs
* more fixes
* ci: update rust-cache to 2.0.1
* ci: update dtolnay/rust-toolchain to ba37adf
* ci: update skip-duplicate-actions to v5.2.0
* ci: update ClementTsang/cargo-action to v0.0.3
* ci: update to macos-12
* ci: update ghaction-chocolatey to 2.1.0
* ci: update upload-artifact to v3.1.0
* ci: change from actions-rs to rustsec for audit-check
* ci: stop using actions-rs for builds
* ci: update cirrus to use tlsv1.2 when curling
* ci: disable macOS ARM workflows on GHA since its built on Cirrus
* ci: spring cleaning of completions autogen
This commit changes a few things/cleans up stuff:
- Completion and manpage generation now drops the files off in
`./target/tmp/bottom` rather than arbitrarily in the build directory.
This was originally done because I was lazy and just needed it to work
in CI, but it's kinda gross if you want to build the manpages in your
own directory.
- CI was updated to handle this.
- Only run if the `BTM_GENERATE` env var is actually non-empty.
* docs: update for manpage/completion gen
* ci: auto delete autogen comp/manpage dir
* ci: fix incorrect mv for autogen
The mv was too late, should be earlier in the workflow.
* ci: specify shell in autogen delete
* docs: more updates to manpage/comp docs
* ci: unify env vars
* ci: skip autogen on build-msi
action-rs' action seems to not be really maintained anymore and
throws some redundant warnings that kinda clog up outputs. As
such, I feel like moving to a more active action is probably worth it.
