tinygo/cgo
Ayke van Laethem 3e109fca5f builder: use build ID as cache key
Instead of storing an increasing version number in relevant packages
(compiler.Version, interp.Version, cgo.Version, ...), read the build ID
from the currently running executable. This has several benefits:

  * All changes relevant to the compiled packages are caught.
  * No need to bump the version for each change to these packages.
    This avoids merge conflicts.
  * During development, `go install` is enough. No need to run
    `tinygo clean` all the time.

Of course, the drawback is that it might be updated a bit more often
than necessary but I think the overall benefit is big.

Regular release users shouldn't see any difference. Because the tinygo
binary stays the same, the cache works well.
2021-12-28 18:29:05 -05:00
..
testdata cgo: add support for C.CString and related functions 2021-11-24 21:09:29 +01:00
cgo.go builder: use build ID as cache key 2021-12-28 18:29:05 -05:00
cgo_test.go cgo: add //go: pragmas to generated functions and globals 2021-11-24 21:09:29 +01:00
const.go cgo: implement prefix parsing 2021-05-21 17:54:13 +02:00
const_test.go cgo: implement prefix parsing 2021-05-21 17:54:13 +02:00
libclang.go cgo: run CGo parser for all CGo fragments in a file 2021-11-04 22:26:33 +01:00
libclang_config.go all: add LLVM 12 support 2021-11-30 21:53:16 +01:00
libclang_config_llvm12.go all: add LLVM 12 support 2021-11-30 21:53:16 +01:00
libclang_stubs.c all: drop support for LLVM 10 2021-10-31 10:44:17 +01:00
security.go cgo: implement #cgo CFLAGS 2019-11-25 09:32:03 +01:00
security_test.go cgo: implement #cgo CFLAGS 2019-11-25 09:32:03 +01:00
sync.go cgo: refactor; support multiple cgo files in a single package 2019-05-12 10:49:15 +02:00