pixi workspace platform add

Adds a platform(s) to the workspace file and updates the lock file

Usage

pixi workspace platform add [OPTIONS] [PLATFORM|NAME=PLATFORM|__NAME[=VERSION[=BUILD]]]...

Arguments

• <PLATFORM|NAME=PLATFORM|__NAME[=VERSION[=BUILD]]>

  Platforms to add, optionally followed by raw virtual-package specs
  May be provided more than once.

Options

• --auto-detect

  Detect this machine's platform (subdir and virtual packages) instead of naming a subdir. Optionally pass a single <name> to name it; any virtual-package flags override the detected values. The detected platform is placed at the top of the list
  aliases: auto-detected, current

• --cuda <VERSION>

  Declare a __cuda virtual package at the given version, e.g. 12.0. Valid on any subdir

• --cuda-arch <VERSION>

  Declare a __cuda_arch virtual package (GPU compute capability) at the given version, e.g. 8.6. Requires --cuda (or an existing __cuda), matching the conda CEP coupling. Serialized as cuda = { driver, arch }

• --archspec <ARCH>

  Declare a __archspec virtual package with the given microarchitecture string, e.g. x86_64_v3. Valid on any subdir

• --glibc <VERSION>

  Declare a __glibc virtual package at the given version, e.g. 2.28. Only valid on linux subdirs

• --linux <VERSION>

  Declare a __linux virtual package at the given kernel version, e.g. 5.10. Only valid on linux subdirs

• --macos <VERSION>

  Declare a __osx virtual package at the given macOS version, e.g. 14.0. Only valid on osx subdirs
  aliases: osx

• --windows <VERSION>

  Declare a __win virtual package at the given Windows version, e.g. 10. Only valid on win subdirs

• --no-install

  Don't update the environment, only add changed packages to the lock file
  env: PIXI_NO_INSTALL

• --feature (-f) <FEATURE>

  The name of the feature to add the platform to

• --environment (-e) <ENVIRONMENT>

  The environment to add the platform to. The platform is written to the platforms defined inline on the environment