blob/9635228/vs2017/meta.yaml#L24 Noarch packages Noarch packages are packages that are not architecture specific and therefore only have to be built once. Noarch packages are either generic or Python each element is a string, as outlined in Package match specifications. arch string Optional. The architecture the package is built for. EXAMPLE: x86_64 Conda currently does not use this key. platform string an existing environment: conda install --name myenv --file spec-file.txt Conda does not check architecture or dependencies when installing from a spec file. To ensure that the pack- ages work correctly

blob/9635228/vs2017/meta.yaml#L24 Noarch packages Noarch packages are packages that are not architecture specific and therefore only have to be built once. Noarch packages are either generic or Python each element is a string, as outlined in Package match specifications. arch string Optional. The architecture the package is built for. EXAMPLE: x86_64 Conda currently does not use this key. platform string an existing environment: conda install --name myenv --file spec-file.txt Conda does not check architecture or dependencies when installing from a spec file. To ensure that the pack- ages work correctly

However, in some cases you might want to create an environment for a different target platform or architecture. To do so, use the --platform flag available in the conda create and conda env create commands an existing environment: conda install --name myenv --file spec-file.txt Conda does not check architecture or dependencies when installing from a spec file. To ensure that the pack- ages work correctly correctly, make sure that the file was created from a working environment, and use it on the same architecture, operating system, and platform, such as linux-64 or osx-64. Activating an environment Activating

However, in some cases you might want to create an environment for a different target platform or architecture. To do so, use the --platform flag available in the conda create and conda env create commands an existing environment: conda install --name myenv --file spec-file.txt Conda does not check architecture or dependencies when installing from a spec file. To ensure that the pack- ages work correctly correctly, make sure that the file was created from a working environment, and use it on the same architecture, operating system, and platform, such as linux-64 or osx-64. Activating an environment Activating

However, in some cases you might want to create an environment for a different target platform or architecture. To do so, use the --platform flag available in the conda create and conda env create commands an existing environment: conda install --name myenv --file spec-file.txt Conda does not check architecture or dependencies when installing from a spec file. To ensure that the pack- ages work correctly correctly, make sure that the file was created from a working environment, and use it on the same architecture, operating system, and platform, such as linux-64 or osx-64. Activating an environment Activating

blob/9635228/vs2017/meta.yaml#L24 Noarch packages Noarch packages are packages that are not architecture specific and therefore only have to be built once. Noarch packages are either generic or Python each element is a string, as outlined in Package match specifications. arch string Optional. The architecture the package is built for. EXAMPLE: x86_64 Conda currently does not use this key. platform string an existing environment: conda install --name myenv --file spec-file.txt Conda does not check architecture or dependencies when installing from a spec file. To ensure that the pack- ages work correctly

an existing environment: conda install --name myenv --file spec-file.txt Conda does not check architecture or dependencies when installing from a spec file. To ensure that the pack- ages work correctly correctly, make sure that the file was created from a working environment, and use it on the same architecture, operating system, and platform, such as linux-64 or osx-64. Activating an environment Activating blob/9635228/vs2017/meta.yaml#L24 Noarch packages Noarch packages are packages that are not architecture specific and therefore only have to be built once. Noarch packages are either generic or Python

an existing environment: conda install --name myenv --file spec-file.txt Conda does not check architecture or dependencies when installing from a spec file. To ensure that the pack- ages work correctly correctly, make sure that the file was created from a working environment, and use it on the same architecture, operating system, and platform, such as linux-64 or osx-64. Activating an environment Activating blob/9635228/vs2017/meta.yaml#L24 Noarch packages Noarch packages are packages that are not architecture specific and therefore only have to be built once. Noarch packages are either generic or Python

blob/9635228/vs2017/meta.yaml#L24 Noarch packages Noarch packages are packages that are not architecture specific and therefore only have to be built once. Noarch packages are either generic or Python each element is a string, as outlined in Package match specifications. arch string Optional. The architecture the package is built for. EXAMPLE: x86_64 Conda currently does not use this key. platform string an existing environment: conda install --name myenv --file spec-file.txt Conda does not check architecture or dependencies when installing from a spec file. To ensure that the pack- ages work correctly

Documentation, Release 4.6.0 conda install --name myenv --file spec-file.txt Conda does not check architecture or dependencies when installing from a spec file. To ensure that the packages work correctly, make sure that the file was created from a working environment, and use it on the same architecture, operating system and platform, such as linux-64 or osx-64. Activating an environment To activate virtualenvwrapper 5.177 2013-11-27 2.2.2: • remove ARCH environment variable for being able to change architecture • add PKG_NAME, PKG_VERSION to environment when running build.sh, .-post-link.sh and .-