Vicente Eduardo Ferrer Garcia

@SMillerDev One more thing about the bootstrap files (the non standard files installed in the lib directory). Some runtimes are really hard to embed, basically they do not provide embedding...

> Why would it be difficult for package managers? It should just be part of the cmake configuration where this is installed. @SMillerDev Are you talking about the env vars?...

This is still happening on `ubuntu:jammy`, with versions ```sh root@b764c64be8c7:/usr/local/metacall/build# node -e 'console.log(process.versions.openssl)' 1.1.1m root@b764c64be8c7:/usr/local/metacall/build# python3 -c 'import ssl; print(ssl.OPENSSL_VERSION.split()[1])' 3.0.2 ``` I am reopening this for now, I have...

Also it seems to be related with rust, when using a similar version (3.0.4 and 3.0.6) if we disable calls in node to rs when python is also loaded in...

Here's the issue of Rust: https://github.com/metacall/core/commit/ad9e7cf7c9a5d04e214f2c0bc1fdaabfa8d1a911 It is unrelated apparently.

This may be interesting to be implemented with GitHub actions.

Also it will be interesting to be implemented in any package, also find a standard way to link the libraries. This should be reviewed with this: https://github.com/metacall/core/issues/231 It depends on...

Additional problems: https://github.com/metacall/core/issues/378 https://github.com/metacall/core/issues/377

@Samyak2 you are right, it is completely unneeded. In my opinion it would be interesting to see what are the real dependencies of the Core itself or.. another option is...

First step towards the resolution of this issue is done: https://github.com/metacall/core/commit/5ea99d7dc3a0c5a5eacdf056bfff4ebb548a14fc Next step is to standardize the compiler detection (and its features) from headers, and include architecture and OS detection....