Skip to content

Add pixi configuration for local dev #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

luizirber
Copy link

@luizirber luizirber commented Nov 25, 2024

While working on conda-forge/staged-recipes#28343 I created a pixi configuration for local dev, submitting here as a PR.

This might help with #45 too, we use in some parts of sourmash CI and it is very convenient because it uses the same deps from local dev.

I tested this in

  • linux x86_64
  • macOS arm64
  • macOS x86_64
  • macOS x86_64 on arm64 via rosetta2, pixi does all the setup as long as you have rosetta2 installed (I did it with /usr/sbin/softwareupdate --install-rosetta --agree-to-license)
  • tried out linux aarch64 and almost fried my poor raspberry pi 4, but compilation failed for GGCAT, so ended up removing it

the github actions workflow uses this pixi configuration to do a build and run the generated binary, but I can't test it properly because I don't have permissions to run GH actions in your repo

@luizirber luizirber force-pushed the lirber/pixi branch 4 times, most recently from 29a2f48 to 7fb31c5 Compare November 26, 2024 19:07
@luizirber luizirber marked this pull request as ready for review November 26, 2024 19:10
@luizirber
Copy link
Author

luizirber commented Nov 26, 2024

Still pending: how to document use of pixi? Add to README?

What I do is usually either

  • pixi shell for a shell with all deps installed and ready
  • pixi run build to generate ./build/fulgor for use
  • pixi run debug to generate a debug build in ./debug_build/fulgor

but not sure how to fit it best in README without making it confusing with current instructions

@Alessio-Campa
Copy link
Collaborator

but not sure how to fit it best in README without making it confusing with current instructions

This could fit very well inside the wiki. Do you have the documentation already prepared? You can send it to me or @jermp, or write it as a comment here, and we will add it right away.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants