[TRACKER] Binding native app library to embedded scripts

[KaruroChori]

A native application distributed as a dynamic library with main entry-point can be linked against by a vs app by passing the path of the library and the c headers.
For example:

<app link-with.lib="this://native-app/libapp.so" link-with.header="this://native-app/app.h">

The symbols exposed by it should be available (possibly namespaced) to our custom scripts in vs. Most targets will need some translation layer based on libffi, but for tcc-cnative it should be much easier.

Should. Because it requires to:

• Build and distribute libtcc1.a
• Link libc which I really don't want
• Have knowledge of where such library is placed in the host system.

This approach, while feasible, is does not fit well considering the rest of the design objectives, and it does not play well with what will be needed when implementing the same feature in other pipelines.

The suggested approach is to load the dynamic library in memory as a cached asset, and parse its list of symbol to expose explicitly when building the embedded script.