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

ENH: Include system runtime libraries #142

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

Conversation

jamesobutler
Copy link

This is part of addressing Slicer/Slicer#7847.

This avoids a termination fault when running the CLI executable when it was built with a newer MSVC relative to another computer with an older runtime. Including the runtime libraries will make sure compatibility is correct instead of falling back to the system version.

This avoids a termination fault when running the CLI executable when it was built with a newer MSVC relative to another computer with an older runtime. Including the runtime libraries will make sure compatibility is correct instead of falling back to the system version.
@jcfr
Copy link
Member

jcfr commented Jul 10, 2024

Slicer is already expected to package the needed runtime along the application.

I will look at the referenced issue to better understand and see how to fix the root cause.

@lassoan
Copy link
Contributor

lassoan commented Jul 10, 2024

It seems that the Slicer.exe launcher itself needs MSVC runtime DLLs, which is an issue, because it will not find them if they are in the bin subfolder. The best would be to link Slicer.exe statically so that it does not need any DLLs to run.

(ignore what I wrote before - since this only comes up when launching a CLI and not when launching Slicer itself, the launcher itself should be fine)

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

Successfully merging this pull request may close these issues.

3 participants