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

Revisiting library initialization #682

Open
magnatelee opened this issue Apr 12, 2023 · 0 comments
Open

Revisiting library initialization #682

magnatelee opened this issue Apr 12, 2023 · 0 comments

Comments

@magnatelee
Copy link
Contributor

The current procedure for library initialization requires that the library registration callback be exposed and bound to Python via CFFI. This shouldn't be a hard requirement, as long as the library makes sure that its registration callback is invoked somehow. Plus, while working on #675, @trxcllnt and I uncovered that the dlopen during library registration can cause trouble when mixed with Cython extension libraries that are misconfigured, such as shared libs of the same legate library from different locations being loaded simultaneously.

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

1 participant