-
|
I'm a little confused as to why you distribute an entire go toolchain with the standard libary. Even if you need to do this because you do some compiler magic etc. providing precompiled libaries under |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Thanks for asking. Encore's request semantics as well as automatic tracing require integration into the runtime. The changes are all open source and constitute a very small amount of code, mostly involving adding some hooks. You are more than welcome to build the toolchain yourself. To my knowledge the packaging process is the same as for the regular Go releases, and the precompiled libraries are present because not all environments have the tools installed to compile the standard library and cgo. |
Beta Was this translation helpful? Give feedback.
-
|
Does this present issue with using the custom golang tool chain to do other things like compiling golang to wasm etc |
Beta Was this translation helpful? Give feedback.
Thanks for asking. Encore's request semantics as well as automatic tracing require integration into the runtime. The changes are all open source and constitute a very small amount of code, mostly involving adding some hooks. You are more than welcome to build the toolchain yourself.
To my knowledge the packaging process is the same as for the regular Go releases, and the precompiled libraries are present because not all environments have the tools installed to compile the standard library and cgo.