[Question] Build Static Libraries

[deinok]

The README.md states the following:

It can also produce standalone dynamic or static libraries that can be consumed by applications written in other programming languages.

But I can't find information about how to do it. Can sombody give me more information?

[jkotas]

@deinok I have polished the WIP docs in #6645. Please take a look and give us feedback on the instructions worked for you.

[deinok]

@jkotas Really nice work. Probably I'm missing something, but why is NativeCallableAttribute attribute not included in source?

[deinok]

Also, does the generated files have some runtime dependencies other than the OS itself?

[jkotas]

Probably I'm missing something, but why is NativeCallableAttribute attribute not included in source?

CoreRT shares the public API definition with .NET Core. NativeCallableAttribute was not added as public .NET Core (yet), so this workaround it necessary for now.

Also, does the generated files have some runtime dependencies other than the OS itself?

The runtime dependencies are fully self-contained. The binary has same OS dependencies as .NET Core. (It only really matters on Linux - there is a list of OS packages that it needs.)

[deinok]

CoreRT shares the public API definition with .NET Core. NativeCallableAttribute was not added as public .NET Core (yet), so this workaround it necessary for now.

Thanks for the change on the docs.

The runtime dependencies are fully self-contained. The binary has same OS dependencies as .NET Core. (It only really matters on Linux - there is a list of OS packages that it needs.)

So, for what I understand a *.so generated via CoreRT will just require the same *.so that .NETCore
Runtime requires (the same a common publish -r will need), not the .NETCore Runtime itself

[jkotas]

Right

[deinok]

@jkotas Thanks for the info :)