Comments (7)
I am using Apple Silicon every day :) But I understand that it's an issue for bioconda
folks. We're working on it!
from pixi.
I think the user needs to manually install rosetta, but Apple makes it pretty easy.
We actually have a similar problem for emscripten-wasm32
and wasi-wasm32
- for those architectures we would also always want to install the defined platform instead of the native one.
But I agree with Bas that we might find a straightforward solution for the osx-arm64
-> osx-64
case and could allow automatic cross-platform installation of the environments.
@ruben-arts I think the bioconda
project has not yet started to build packages for osx-arm64
.
from pixi.
This is indeed something we're not supporting yet. We've had a similar request on in this issue
Although its not super trivial, as we want a project to be completely reproducible and I believe to make your request work you need Rosetta on your machine and we can't check if that is installed yet.
On the short therm, in most cases it's not hard to build the conda package for osx-arm64
which packages do you need this for?
from pixi.
I would want this to be supported out of the box without the user having to specify additional flags.
@ruben-arts Perhaps we should extend our logic in some places to use osx-64
as the "current" platform if the project is not configured for osx-arm64
? With a small warning perhaps?
@corneliusroemer Do macOS x86 applications always work on macOS arm64? Or do you need to enable this somehow?
from pixi.
I guess with a virtual package we could easily define and document the logic right? This probably also goes for the wasm platforms, not sure what you would need for those.
from pixi.
Do macOS x86 applications always work on macOS arm64? Or do you need to enable this somehow?
Yes, one needs to install rosetta, but most devs have done so already and it's easy if not. It's literally a one-liner:
/usr/sbin/softwareupdate --install-rosetta --agree-to-license
It's also not too hard to test if rosetta is installed and warn the user, see how nextstrain-cli
does that here for inspiration:
- https://github.com/nextstrain/cli/blob/4fa53169059047454fb10b55a584395239b61a1a/nextstrain/cli/util.py#L606-L644
- https://github.com/nextstrain/cli/blob/4fa53169059047454fb10b55a584395239b61a1a/bin/standalone-installer-unix#L117-L137
I can't use any bioconda packages with pixi yet, indeed, as there are no arm versions. Also by far not all conda-forge osx packages have been migrated to arm yet.
I highly recommend one of you get an ARM mac to dogfood pixi on that platform, it's quite widespread and is fairly important for pixi to fly, I think - I wouldn't recommend it to anyone until it works decently on arm.
from pixi.
Here is a workaround:
curl -L https://github.com/prefix-dev/pixi/releases/download/v0.18.0/pixi-x86_64-apple-darwin -o ~/.pixi/bin/pixi-64
chmod u+x ~/.pixi/bin/pixi-64
Now you can use pixi-64
on osx-arm64 to install "cross-platform" packages. Of course, the downside is that you have 2x pixi installations, but this works for the time being. We'll implement some more clever cross-platform ideas: #1020
from pixi.
Related Issues (20)
- Provide feedback when local install editable fails HOT 4
- `pixi add` with comment HOT 1
- ros2-nav2 example is broken HOT 6
- pixi should help user with missing project channel HOT 2
- Invalidate lock file when mapping changes.
- pixi config option to exhaustively list all configuration options (like `conda config --describe`) HOT 1
- Unable to install `faster-whisper` with pixi, but works with pip (Python 3.12) HOT 3
- Can't modify PATH in env activation table HOT 1
- Incorrectly rebuilding editable pypi dependency, and not installing it HOT 10
- --frozen helpstring is missing from 0.23.0 HOT 1
- thread panic in rattler solve HOT 7
- Patch conda-pypi mapping with a specific name HOT 3
- `pixi.lock` always outdated when using local folder with `editable` as `PyPI` dependency HOT 1
- Pixi does not freeze version number for PyPI package installs HOT 2
- `pixi install` fails when using `detached-environments = true` and `.pixi` doesn't exist yet
- `pixi run` warning about project manifest should only show up if `PIXI_PROJECT_MANIFEST` and local `pixi.toml` are different HOT 4
- `[activation.env]` variables are not expanded HOT 1
- `pixi install` / `pixi run` doesn't handle multiple concurrent invocations very well HOT 1
- CUDA virtual package is not detected when using brew version of pixi HOT 2
- Pixi successfull install message missing a newline
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pixi.