Using libgccjit as an AOT compiler backend forcross-compilation (second attempt)

[me@rochus-keller.ch]

Thanks for your respones.

@David:

> I can imagine something that implements the libgccjit API and then

> proxies the calls to different underlying target support libraries, but

> that doesn't exist yet, and wouldn't you save any space on disk or

> build times, alas.

I will load the library via dlopen/dlsym to avoid static dependencies anyway
and I assume by this very mechanism I would also be able to deal with different
versions of the library without implementing a proxy.


> Not without a huge amount of work, as noted above.

I understand, but at least building libgccjit so that the gcc specific dependencies 
like libgmp, libmpfr, libmpc can be avoided. Does build with -static work for 
libgccjit? Ideally I would the users offer a simple tar.gz download for each architecture
and host system which they would reference by path from the IDE.
What do you think?


@Basile

Please not that I will use it for AOT, not for jit.

> RefPerSys tries to. See source in github below

I assume you refer to my requirement "that only one shared library has to be deployed"?


best regards
Rochus