Open MihaMarkic opened 7 years ago
The generated libraries need a CLR runtime, either linked statically or dynamically in the final application. Right now we only support Mono, but maybe .NET Core support can be be added after we have the missing features on the roadmap implemented.
So no really standalone libraries, right.
They can be "standalone" in the sense that you can get a DLL with Mono statically linked. So you'd just distribute two files, the .dll
/.so
and .h
include file for end users.
The statically linked approach is not implemented but should be easy, we'll add these features depending on the feedback we get from users, so let us know if you need something like this.
I'd be certainly interested in this scenario. Right now I have a scenario where a friend uses python and would call into an external library where some calculation are done. So, I'd send him a couple of files instead of instructions on how to install mono, etc. Then there are console applications and other candidates that would benefit.
IDK, if I find time and digged enough into this I could take care of this. But don't expect too much, simply notice that I'm looking into it ;)
Does end user libraries require .net installed or are they standalone (single file, no references)? I'd certainly prefer an option to have the later but I think currently they are the former (required .net to be installed).