can I build tinygo project as a static link file and link it to another C project?

[jifanchn]

As described above.

I'm wondering if we can just create a very tiny bootstrap C project and link it to a tinyGO program?

And in that case, tinygo output will be "xxx.h" and "xxx.so" and finally link to a basic C project which prepare working environments for tinygo core.

So that maybe we can use most currently useful C platform code and handle data with tinygo.

Nor don't we need to write platform hardware related code in tinygo and tinygo itself can run as a VM(runtime).

[aykevl]

You can compile to an object file by giving it an .o extension. But it will likely lack some symbols you need.
Alternatively, you can use Go and include external C files using CGo.

Can you give a bit more detail what you're trying to accomplish? What hardware are you compiling for, and with what environment?

[xudongzheng]

I've been looking into this and I would like to embed a TinyGo application within Zephyr. The idea is to have most of the logic in Go but to rely on Zephyr for Bluetooth and low level hardware stuff. Even though TinyGo does support nRF52 for Bluetooth, using Zephyr gives a lot of options such as using a separate chip for radio and having the two communicate via HCI.

[aykevl]

This is not really a supported configuration. TinyGo is its own RTOS, it does not currently support linking with an existing RTOS.
This might get added in the future, but we currently have no plans for this.