Documentation

Lake.Config.PackageConfig

@[inline]

The default buildArchive configuration for a package with name.

Equations
Instances For

    A Package's declarative configuration.

    • bootstrap : Bool

      For internal use. Whether this package is Lean itself.

    • manifestFile : Option System.FilePath

      This field is deprecated.

      The path of a package's manifest file, which stores the exact versions of its resolved dependencies.

      Defaults to defaultManifestFile (i.e., lake-manifest.json).

    • extraDepTargets : Array Lean.Name

      An Array of target names to build whenever the package is used.

    • precompileModules : Bool

      Whether to compile each of the package's module into a native shared library that is loaded whenever the module is imported. This speeds up evaluation of metaprograms and enables the interpreter to run functions marked @[extern].

      Defaults to false.

    • moreGlobalServerArgs : Array String

      Additional arguments to pass to the Lean language server (i.e., lean --server) launched by lake serve, both for this package and also for any packages browsed from this one in the same session.

    • The directory containing the package's Lean source files. Defaults to the package's directory.

      (This will be passed to lean as the -R option.)

    • buildDir : System.FilePath

      The directory to which Lake should output the package's build results. Defaults to defaultBuildDir (i.e., .lake/build).

    • leanLibDir : System.FilePath

      The build subdirectory to which Lake should output the package's binary Lean libraries (e.g., .olean, .ilean files). Defaults to defaultLeanLibDir (i.e., lib).

    • nativeLibDir : System.FilePath

      The build subdirectory to which Lake should output the package's native libraries (e.g., .a, .so, .dll files). Defaults to defaultNativeLibDir (i.e., lib).

    • The build subdirectory to which Lake should output the package's binary executable. Defaults to defaultBinDir (i.e., bin).

    • The build subdirectory to which Lake should output the package's intermediary results (e.g., .c and .o files). Defaults to defaultIrDir (i.e., ir).

    • releaseRepo : Option String

      The URL of the GitHub repository to upload and download releases of this package. If none (the default), for downloads, Lake uses the URL the package was download from (if it is a dependency) and for uploads, uses gh's default.

    • buildArchive : Option String

      A custom name for the build archive for the GitHub cloud release. If none (the default), Lake defaults to {(pkg-)name}-{System.Platform.target}.tar.gz.

    • preferReleaseBuild : Bool

      Whether to prefer downloading a prebuilt release (from GitHub) rather than building this package from the source when this package is used as a dependency.

    • testDriver : String

      The name of the script, executable, or library by lake test when this package is the workspace root. To point to a definition in another package, use the syntax <pkg>/<def>.

      A script driver will be run by lake test with the arguments configured in testDriverArgs followed by any specified on the CLI (e.g., via lake lint -- <args>...). An executable driver will be built and then run like a script. A library will just be built.

    • testDriverArgs : Array String

      Arguments to pass to the package's test driver. These arguments will come before those passed on the command line via lake test -- <args>....

    • lintDriver : String

      The name of the script or executable used by lake lint when this package is the workspace root. To point to a definition in another package, use the syntax <pkg>/<def>.

      A script driver will be run by lake lint with the arguments configured in lintDriverArgs followed by any specified on the CLI (e.g., via lake lint -- <args>...). An executable driver will be built and then run like a script.

    • lintDriverArgs : Array String

      Arguments to pass to the package's linter. These arguments will come before those passed on the command line via lake lint -- <args>....

    • version : StdVer

      The package version. Versions have the form:

      v!"<major>.<minor>.<patch>[-<specialDescr>]"
      

      A version with a - suffix is considered a "prerelease".

      Lake suggest the following guidelines for incrementing versions:

      • Major version increment (e.g., v1.3.0 → v2.0.0) Indicates significant breaking changes in the package. Package users are not expected to update to the new version without manual intervention.

      • Minor version increment (e.g., v1.3.0 → v1.4.0) Denotes notable changes that are expected to be generally backwards compatible. Package users are expected to update to this version automatically and should be able to fix any breakages and/or warnings easily.

      • Patch version increment (e.g., v1.3.0 → v1.3.1) Reserved for bug fixes and small touchups. Package users are expected to update automatically and should not expect significant breakage, except in the edge case of users relying on the behavior of patched bugs.

      Note that backwards-incompatible changes may occur at any version increment. The is because the current nature of Lean (e.g., transitive imports, rich metaprogramming, reducibility in proofs), makes it infeasible to define a completely stable interface for a package. Instead, the different version levels indicate a change's intended significance and how difficult migration is expected to be.

      Versions of form the 0.x.x are considered development versions prior to first official release. Like prerelease, they are not expected to closely follow the above guidelines.

      Packages without a defined version default to 0.0.0.

    • versionTags : StrPat

      Git tags of this package's repository that should be treated as versions. Package indices (e.g., Reservoir) can make use of this information to determine the Git revisions corresponding to released versions.

      Defaults to tags that are "version-like". That is, start with a v followed by a digit.

    • description : String

      A short description for the package (e.g., for Reservoir).

    • keywords : Array String

      Custom keywords associated with the package. Reservoir can make use of a package's keywords to group related packages together and make it easier for users to discover them.

      Good keywords include the domain (e.g., math, software-verification, devtool), specific subtopics (e.g., topology, cryptology), and significant implementation details (e.g., dsl, ffi, cli). For instance, Lake's keywords could be devtool, cli, dsl, package-manager, and build-system.

    • homepage : String

      A URL to information about the package.

      Reservoir will already include a link to the package's GitHub repository (if the package is sourced from there). Thus, users are advised to specify something else for this (if anything).

    • license : String

      The package's license (if one). Should be a valid SPDX License Expression.

      Reservoir requires that packages uses an OSI-approved license to be included in its index, and currently only supports single identifier SPDX expressions. For, a list of OSI-approved SPDX license identifiers, see the SPDX LIcense List.

    • licenseFiles : Array System.FilePath

      Files containing licensing information for the package.

      These should be the license files that users are expected to include when distributing package sources, which may be more then one file for some licenses. For example, the Apache 2.0 license requires the reproduction of a NOTICE file along with the license (if such a file exists).

      Defaults to #["LICENSE"].

    • readmeFile : System.FilePath

      The path to the package's README.

      A README should be a Markdown file containing an overview of the package. Reservoir displays the rendered HTML of this file on a package's page. A nonstandard location can be used to provide a different README for Reservoir and GitHub.

      Defaults to README.md.

    • reservoir : Bool

      Whether Reservoir should include the package in its index. When set to false, Reservoir will not add the package to its index and will remove it if it was already there (when Reservoir is next updated).

    • enableArtifactCache? : Option Bool

      Whether to enables Lake's local, offline artifact cache for the package.

      Artifacts (i.e., build products) of packages will be shared across local copies by storing them in a cache associated with the Lean toolchain. This can significantly reduce initial build times and disk space usage when working with multiple copies of large projects or large dependencies.

      As a caveat, build targets which support the artifact cache will not be stored in their usual location within the build directory. Thus, projects with custom build scripts that rely on specific location of artifacts may wish to disable this feature.

      If none (the default), the cache will be disabled by default unless the LAKE_ARTIFACT_CACHE environment variable is set to true.

    • libPrefixOnWindows : Bool

      Whether native libraries (of this package) should be prefixed with lib on Windows.

      Unlike Unix, Windows does not require native libraries to start with lib and, by convention, they usually do not. However, for consistent naming across all platforms, users may wish to enable this.

      Defaults to false.

    Instances For
      Equations
      • One or more equations did not get rendered due to their size.
      Instances For
        @[reducible, inline]

        The package's name.

        Equations
        Instances For

          A package declaration from a configuration written in Lean.

          Instances For