You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a documentation gap; there is no specific category for that so filing as a "bug".
As detailed in #514 (comment) and many others, ninja is probably the most popular tool for building C/C++. It's also used outside C/C++ Unsurprisingly, including ninja in the default image has been requested many times over the years:
provide sample install code that works for each supported operating system + the ${{ conditionals }} to make it portable. Or, much better:
endorse some official, GitHub-approved action that installs ninja on all operating systems so not every user has to perform a duplicate security audit effort. In other words, officially endorse one of these:
As of now, installing ninja requires searching closed issues for scattered, conflicting and out of date advice. Random tips to install ninja on Windows vary (either vcpkg that comes and goes, unreliable choco, other?), mac recommendations are very slow (brew) and Linux samples miss the important and non-obvious "apt-get update" pre-requirement #2924
Description
This is a documentation gap; there is no specific category for that so filing as a "bug".
As detailed in #514 (comment) and many others, ninja is probably the most popular tool for building C/C++. It's also used outside C/C++ Unsurprisingly, including
ninja
in the default image has been requested many times over the years:This has been rejected every time. One of the answers given practically every time: "it's easy to install at run time".
Because
ninja
is the top C/C++ build tool, how to install it should be in the official documentation.https://docs.github.com/en/search?query=ninja
The official documentation should either:
As of now, installing ninja requires searching closed issues for scattered, conflicting and out of date advice. Random tips to install ninja on Windows vary (either vcpkg that comes and goes, unreliable choco, other?), mac recommendations are very slow (brew) and Linux samples miss the important and non-obvious "apt-get update" pre-requirement #2924
From #8348 (comment)
I don't think it is "extremely" easy, see above. But if it truly is, then documenting this will be too.
cc: @erik-bershel, @Darleev, @alepauly, @miketimeofeev, @maxim-lobanov, @dibir-magomedsaygitov
Platforms affected
Runner images affected
Image version and build link
This is a documentation gap; there was no category for that.
Is it regression?
No
Expected behavior
https://docs.github.com/en/search?query=ninja shows something
Actual behavior
https://docs.github.com/en/search?query=ninja shows nothing
Repro steps
https://docs.github.com/en/search?query=ninja
The text was updated successfully, but these errors were encountered: