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

when i run the example #67

Open
Yanthirteen13 opened this issue Feb 27, 2024 · 4 comments
Open

when i run the example #67

Yanthirteen13 opened this issue Feb 27, 2024 · 4 comments
Assignees

Comments

@Yanthirteen13
Copy link

he@he-virtual-machine:~/ViennaPS/build/ViennaPS/examples/holeEtching$ python3 holeEtching.py config.txt
Running 2D simulation.
Traceback (most recent call last):
File "/home/he/ViennaPS/build/ViennaPS/examples/holeEtching/holeEtching.py", line 12, in
import viennaps2d as vps
File "/home/he/.local/lib/python3.10/site-packages/viennaps2d/init.py", line 11, in
from ._viennaps2d import *
ImportError: libvtkIOXMLParser.so.1: cannot open shared object file: No such file or directory

can u help me?i dont know what's the problem,thanks a lot

@tobre1
Copy link
Member

tobre1 commented Feb 27, 2024

It appears there might be a linking issue with your VTK build. Could you please clarify whether you are using your own custom-built VTK, or if you're relying on the VTK build through buildDependencies while setting up ViennaPS?

@Yanthirteen13
Copy link
Author

Yanthirteen13 commented Feb 27, 2024

i am relying on the VTK build through buildDependencies while setting up ViennaPS.when i rebuild ,it shows"Built target buildDependencies"

@tobre1
Copy link
Member

tobre1 commented Feb 28, 2024

I am not able to reproduce this problem. Could you please provide additional information on your build system and building steps.

I've successfully reproduced this issue with a fresh build and utilizing a custom VTK build. It appears that the problem stems from the VTK libraries not being correctly included in the runtime path.

Unfortunately, I don't have an immediate solution for this at the moment. However, it's worth noting that we're currently in the process of a major overhaul of the CMake setup, which we anticipate will likely address this problem.

In the meantime, if you're able to utilize a system-wide installation of VTK, such as through a package manager like sudo apt install vtk9 on a Linux-based system, you should be able to run the Python bindings within the current setup.

@Curve Curve self-assigned this Mar 4, 2024
@Curve
Copy link
Member

Curve commented Mar 23, 2024

With the latest CMake overhaul this should now work.

Could you please update and test again?

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

No branches or pull requests

3 participants