I suppose that there are some environments where make isn’t available by default, so if the crate author wants to target those environments and the crate needs make then they have to make it a dependency.
Typically, if a crate needs make it’s to do some setting up (e.g. in a post-fetch action).
Nothing to do with your PATH, alire doesn’t check to see whether make is already present before trying the download.
Thank you. That makes sense. I was just curious if it was potentially a problem.
RBE
Are you saying I need to add make as a dependency?
You already do! … here:
[[actions]]
type = "pre-build"
command = ["make", "-C", "./build/gnat", "tools"]
[[depends-on]]
libsdl2 = "^2.0.0"
make = "*" # Required for post-fetch actions
It’s just possible we could stop Alire even thinking about downloading a tool if (some version of) it’s already present on the PATH …
macOS has Make 3.81 on the path already.
Homebrew offers Make but installs it as gmake (because the SDK already has a version, I guess): 4.4.1.
==> Caveats
GNU "make" has been installed as "gmake".
If you need to use it as "make", you can add a "gnubin" directory
to your PATH from your bashrc like:
PATH="/opt/homebrew/opt/make/libexec/gnubin:$PATH"
Ah, I wasn’t sure. That’s ok then.