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

Fixed or-tools install script #643

Merged
merged 7 commits into from
Feb 22, 2024
Merged

Fixed or-tools install script #643

merged 7 commits into from
Feb 22, 2024

Conversation

SeppiaBrilla
Copy link
Contributor

Hi, I have noticed that, in some Linux systems, the script to install or-tools wasn't working properly: the compilation was successful but at, execution time, the Or-tools solver would throw an exception because it could not locate a shared library it needed. The library was present but it was located in the binary directory and not in the shared library directory. To fix this issue, I have added an if statement that checks if the shared binary folder is present and if it is, the libraries will be copied there. I have also added a message to inform the user on how to act in case the solver doesn't work.

@ozgurakgun
Copy link
Collaborator

ozgurakgun commented Feb 18, 2024

I think this is the right diagnosis, but I am not sure if the solution is ok.

AFAIK: DYLD_LIBRARY_PATH is a colon separated list of directories that contain libraries. So not necessarily a single value.

We have BIN_DIR controlling where the binaries should end up in, with ~/.local/bin as it's default value.

Maybe we need a LIB_DIR env var as well controlling where the shared libs should end up in? Does anybody know what the done thing is here I wonder? Maybe @ott2?

PS: DYLD_LIBRARY_PATH on macos LD_LIBRARY_PATH on linux.

@ozgurakgun ozgurakgun merged commit 2b9618f into conjure-cp:main Feb 22, 2024
12 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