Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Ninja for BoringSSL if available #837

Merged
merged 5 commits into from
May 30, 2021

Commits on May 29, 2021

  1. Detect Ninja in configure

    Look into the system if there is "ninja" binary available in PATH.
    If there is one, note it for future use.
    ilammy committed May 29, 2021
    Configuration menu
    Copy the full SHA
    6c45d72 View commit details
    Browse the repository at this point in the history
  2. Use Ninja for BoringSSL if available

    Ninja build tool significantly reduces compilation time for BoringSSL in
    default configuration. This is mostly due to the fact that it performs
    parallel builds by default but there are other gains (Makefiles that
    CMake generates are not that optimal). "make -j4" is also a viable
    option, but it often ends up brittle.
    ilammy committed May 29, 2021
    Configuration menu
    Copy the full SHA
    536d683 View commit details
    Browse the repository at this point in the history
  3. Install ninja for jobs that build BoringSSL

    Make sure it's actually installed where relevant.
    ilammy committed May 29, 2021
    Configuration menu
    Copy the full SHA
    03d1684 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    990181e View commit details
    Browse the repository at this point in the history

Commits on May 30, 2021

  1. Configuration menu
    Copy the full SHA
    65af000 View commit details
    Browse the repository at this point in the history