Update manpage with information about alternative compilers#4398
Update manpage with information about alternative compilers#4398MikeMcQuaid merged 10 commits intoHomebrew:masterfrom
Conversation
* Update the manpage source file with additional information
* document the `HOMEBREW_CC` variable with usage information
* update usage information for `--cc`, specifying how to use llvm's clang
|
I'm not sure what the proper way is to go about updating the documentation, it says that travis failed because the man pages changed. |
|
You'll need to run |
|
Ah gotcha, thank you! |
Use brew man to generate manpages, and then copy them to the repo.
|
@afnanenayet my apologies for not being clearer. The manpages are automatically generated from documentation embedded in the Homebrew source files. So you need to update the documentation comments in the relevant files, and then run For the changes that you want, you'll need to update |
|
Haha yeah I was very confused. Thanks for the pointer, maybe we should add this to the documentation as well. |
Properly update man pages using the local brew executable (from the repo), and copy the man pages to the repo.
|
@jonchang is there anything we can do about the code coverage? Edit: JK, I thought that the codecov regression was blocking the merge |
| #: <compiler> should be the name of the compiler's executable, for instance | ||
| #: `gcc-4.2` for Apple's GCC 4.2, or `gcc-4.9` for a Homebrew-provided GCC | ||
| #: 4.9. | ||
| #: 4.9. In order to use LLVM's clang, use `llvm_clang`. To specify the |
There was a problem hiding this comment.
Might be good to reference current versions e.g. gcc, gcc-6 or gcc-4.9? Could you also add Please do not file issues if you encounter errors when using this flag.
There was a problem hiding this comment.
Yes for sure, I used those examples because that's what was documented previously, and I wasn't sure if I should change them
|
|
||
| *Default:* `~/Library/Caches/Homebrew`. | ||
|
|
||
| * `HOMEBREW_CC`: |
There was a problem hiding this comment.
I'd probably rather we left this undocumented as it's very likely to break things if you set it in your environment.
| * Homebrew provides a `gcc` formula for use with Xcode 4.2+ or when needing | ||
| C++11 support on earlier versions. | ||
| C++11 support on earlier versions. | ||
| * Homebrew provides older GCC formulae, e.g. `gcc@4.8` and `gcc@6`. |
Yep, can just ignore code coverage on this PR 👍 |
* update references in `--cc` flag, using modern gcc examples * note that issues should not be filed if `--cc` flag is used * remove reference to `HOMEBREW_CC` as it should not be exposed to users * generate manpages using `brew man` with these changes
This fixes the rubocop offences, which was blocking Travis
Generate new man pages so that the docs and manpages match up
MikeMcQuaid
left a comment
There was a problem hiding this comment.
Couple more tiny tweaks then good to 🚢! Thanks again.
| #: Homebrew-provided GCC 4.9. In order to use LLVM's clang, use | ||
| #: `llvm_clang`. To specify the Apple-provided clang, use `clang`. This | ||
| #: parameter will only accept compilers that are provided by Homebrew or | ||
| #: bundled with MacOS. Please do not file issues if you encounter errors |
There was a problem hiding this comment.
I've been spelling it wrong all this time...O.o
|
Thanks so much for your first contribution! Without people like you submitting PRs we couldn't run this project. You rock, @afnanenayet! |
|
@MikeMcQuaid @jonchang I really appreciate how you guys helped me out despite me not knowing anything about how homebrew is structured and literally taking 10 commits to update some doc -- really appreciate the encouragement :) |
This change references #4387. While I understand alternative compilers aren't officially supported, it is worth documenting Homebrew's behavior with the options that do allow users to compile with something besides Apple's bundled clang.
--ccparam, stating how to use the Homebrew provided clang, also noting that issues should not be filed if this flag is usedNote: I did not write any additional tests, because I did not change any functionality.
brew stylewith your changes locally?brew testswith your changes locally?