From 6dd04bee2f051a5b3a7e8df91b1ae46bf367bcaa Mon Sep 17 00:00:00 2001 From: Jonathan Chang Date: Tue, 8 Sep 2020 23:39:16 +1000 Subject: [PATCH] docs: talk about custom Requirements --- docs/Building-Against-Non-Homebrew-Dependencies.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Building-Against-Non-Homebrew-Dependencies.md b/docs/Building-Against-Non-Homebrew-Dependencies.md index 4f84f103d7..eb9fa56105 100644 --- a/docs/Building-Against-Non-Homebrew-Dependencies.md +++ b/docs/Building-Against-Non-Homebrew-Dependencies.md @@ -8,4 +8,4 @@ As Homebrew became primarily a binary package manager, most users were fulfillin ## Today -If you wish to build against custom non-Homebrew dependencies that are provided by Homebrew (e.g. a non-Homebrew, non-macOS `ruby`) then you must [create and maintain your own tap](How-to-Create-and-Maintain-a-Tap.md) as these formulae will not be accepted in Homebrew/homebrew-core. Once you have done that you can specify `env :std` in the formula which will allow e.g. `which ruby` to access your existing `PATH` variable and allow compilation to link against this Ruby. +If you wish to build against custom non-Homebrew dependencies that are provided by Homebrew (e.g. a non-Homebrew, non-macOS `ruby`) then you must [create and maintain your own tap](How-to-Create-and-Maintain-a-Tap.md) as these formulae will not be accepted in Homebrew/homebrew-core. Once you have done that you can specify `env :std` in the formula which will allow e.g. `which ruby` to access your existing `PATH` variable and allow compilation to link against this Ruby. You can also [include a custom Requirement](https://github.com/Homebrew/brew/tree/HEAD/Library/Homebrew/requirements) in your formula that more accurately describes the non-Homebrew software you build against.