Suppose I'm shipping a product that includes several executables. Each of them will bu

Shared runtime about bflat HOT 2 CLOSED

bflattened commented on September 3, 2024

Shared runtime

from bflat.

Comments (2)

MichalStrehovsky commented on September 3, 2024 3

That's a difficult feature to add. It also inhibits a lot of AOT optimizations since the compiler can no longer reason about the whole program.

Here's what I would do though:

Place all your logic into a shared library. Expose [UnmanagedCallersOnly] entrypoints for the individual Mains
Create shim programs that just p/invoke into the entrypoints

Sample:

Componen1.cs

class Component1
{
    [System.Runtime.InteropServices.UnmanagedCallersOnly(EntryPoint = "Component1_Main")]
    static void _Main() => System.Console.WriteLine("Hello from program1");
}

Componen2.cs

class Component2
{
    [System.Runtime.InteropServices.UnmanagedCallersOnly(EntryPoint = "Component2_Main")]
    static void _Main() => System.Console.WriteLine("Hello from program2");
}

Program1.cs

Component1_Main();

[System.Runtime.InteropServices.DllImport("SharedLib")]
static extern void Component1_Main();

Program2.cs

Component2_Main();

[System.Runtime.InteropServices.DllImport("SharedLib")]
static extern void Component2_Main();

Now build as:

bflat build Component1.cs Component2.cs -o:SharedLibrary.dll
bflat build --stdlib:zero Program1.cs -i:SharedLib --ldflags:SharedLibrary.lib
bflat build --stdlib:zero Program2.cs -i:SharedLib --ldflags:SharedLibrary.lib

The program itself only has a p/invoke and will be tiny (a couple kB). SharedLibrary.dll will have all the meat.

from bflat.