-
Notifications
You must be signed in to change notification settings - Fork 68
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
vtk has hard links that seem to prevent anaconda libraries relocation #1960
Comments
@doutriaux1 When conda compiles VTK, does it enable the module |
@sankhesh I passed it the exact same options as we do for our build. If I build with these options it seems to work, it's a relocation issue I think. Looks like some path are hard coded. |
@sankhesh I will try to manually turn this on anyway, thanks for the pointer. |
ok I see it in the log, we'll see if it picks it up
|
@sankhesh that was it! You're a genius! |
@sankhesh is there an option to turn on ALL modules? Thanks |
@doutriaux1 Awesome. There is an option to enable all modules : However, I would suggest not to use it. That would build a whole LOT MORE code than required. |
@sankhesh I'll give it a try, since it's for anaconda we only build it once in a long while so that might be worth it. |
@doutriaux1 please do not use / turn "VTK_BUILD_ALL_MODULES" it will increase the binary size unnecessarily. |
yes I noticed and it also needs mpi and all that we don't necessarily want on. |
using anaconda built vtk from our repo we cannot export svg any longer
results in:
The text was updated successfully, but these errors were encountered: