You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When scikit-build assembles dpctl, it runs cmake with "_skbuild/*/cmake-build" being
its build directory, "_skbuild/*/cmake-install" being its install directory. It then
runs setuptools.setup to execute build_py steps using "_skbuild/*/setuptools" as its
build_base. Since sycl interface library is registered in package-data, it is copied
from cmake-install (where is has symbolic links) to setuptools (where unpatched
setuptools.command.build_py command follows them turning them into hard files).
Then, when running install_lib step, files from _"skbuild/*/setuptools/lib/dpctl" are
copied into site-packages/dpctl using copy_tree, which also follows symbolic links,
hence turning them into hard links).
This PR transfers logic from pre-scikit-build setup.py to fix hard links as post
setuptools.command.install.run() step).
A test is added to tests/test_service.py to verify that on Linux some of library files
are symbolic links.
0 commit comments