Skip to content

Review hard-coding tools version in build #4298

@jamie-osec

Description

@jamie-osec

#4295

Related: Hardcoding build tools version (#4098) is far from ideal because:

  • The user will get an error after passing -- --tools-version to the underlying command, which we support.
  • Solana's build tools also control the Rust version used, meaning it may be even necessary to change this to make builds work by default (e.g. in the case of MSRV bumps, which the Rust community doesn't consider breaking)

The idea of adding this is to move away from relying on the user having a new-enough platform-tools installed (following the general pattern of moving solana cli functionality into anchor to avoid depending on that unknown environment). This was mostly to resolve a lot of issues caused by people with the 1.85 build tools, which were causing frequent error reports.

Really, we want a way to ensure that the user has build tools for at least our MSRV.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions