Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
1.2k views
in Technique[技术] by (71.8m points)

cmake - Is setting LD_LIBRARY_PATH best way to ensure shared libraries of python package are loaded?

I've a python wheel which contains shared libraries *.so alongwith the python module. Those shared libraries are created using setuptools.command.build_ext [via cmake].

Upon installing the wheel

pip install <name>.whl

All the python packages are installed in /opt/conda/lib/python3.6/site-packages/<package>/ while the shared libraries are installed in /opt/conda/lib/python3.6/site-packages

However, by default LD_LIBRARY_PATH doesn't search for /opt/conda/lib/python3.6

Is it considered a best practice to force users to update LD_LIBRARY_PATH to point to the directory that contains shared libraries as part of python package installation? or is there a better way of handling it at compile-time so that the shared libraries are accessible for the users [who don't compile it but just install the python package] without updating the LD_LIBRARY_PATH?

question from:https://stackoverflow.com/questions/65648315/is-setting-ld-library-path-best-way-to-ensure-shared-libraries-of-python-package

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Answer

0 votes
by (71.8m points)
Waitting for answers

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

2.1m questions

2.1m answers

60 comments

57.0k users

...