Skip to content
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

solvers: avoid specifying solver paths in define-runtime-path #278

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

sorawee
Copy link
Collaborator

@sorawee sorawee commented Mar 5, 2024

On commands like raco distribute, paths under define-runtime-path will be copied over for distribution, which mandates their existence. Therefore, we should only use define-runtime-path with paths that we know for sure that they exist.

On commands like `raco distribute`, paths under `define-runtime-path`
will be copied over for distribution, which mandates their existence.
Therefore, we should only use `define-runtime-path` with paths
that we know for sure that they exist.
@gussmith23
Copy link
Contributor

FWIW, putting the solver binaries into Rosette did turn out to be the cleanest way to package up my project. It eliminated the need for extra logic telling Rosette where the packaged solvers are. I wouldn't have discovered this feature without Rosette forcing the binaries to be present. I do think that making the binaries optional is definitely the right idea, though perhaps there should be some specific documentation on packaging up projects that use Rosette, specifically suggesting that copying the binaries into Rosette is an easy route to packaging up the binaries.

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