Skip to content

Fix/use correct compiler pixi/conda #914

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

Merged

Conversation

tony-p
Copy link
Contributor

@tony-p tony-p commented Jan 28, 2025

Use the correct compiler in the pixi.toml which removes the need for some conda specific things I put in originally, will also automatically select correct compiler for the OS.

Also bring version more in line with conan requirements, and update pixi versions in pipeline.

… for the platform, and setup the required environment for it to work as expected
@facontidavide
Copy link
Collaborator

Just a question for a person unfamiliar with pixi. Should the lock file be there?

@tony-p
Copy link
Contributor Author

tony-p commented Jan 31, 2025

Typically yes, it ensures reproducibility, especially when you are trying to go back in time to an old version.

So the toml file describes the constraints, and then solver finds a valid set and fixes them in the lock file.

the lock file will be updated if you change the constraints, and if you want to try bumping all the versions, you can remove the lock file and let it regenerate.

The default parameters of the setup-pixi action will actually ensure that the committed lock file is up to date with the constraints.

@facontidavide facontidavide merged commit b4bbef6 into BehaviorTree:master Jan 31, 2025
9 checks passed
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.

2 participants