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

Feature request: Include P4est.jl as dependency #25

Open
jmark opened this issue Jun 12, 2023 · 0 comments
Open

Feature request: Include P4est.jl as dependency #25

jmark opened this issue Jun 12, 2023 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@jmark
Copy link
Contributor

jmark commented Jun 12, 2023

T8code.jl respectively t8code_jll.jl come with their own shared libraries of p4est and libsc. In order to avoid
namespace collisions the bindings for these libraries are not exported to the global namespace as is done for the
t8code bindings. This means, fully qualified names are necessary in order to use p4est_* and sc_* routines.

However, it would be more elegant to use the same routines from P4est.jl instead. But, with the current configuration
the shared libraries from different packages do not properly "see each other" and do not communicate in therms of
adress spaces which is vital for memory management.

This should be investigated.

The questions is: How does the mechanism of loading shared libraries from different packages into the same adress space work? Especially, on different platforms such as Linux, MacOS and Windows.

@jmark jmark added enhancement New feature or request help wanted Extra attention is needed labels Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant