On Mon, Oct 14, 2024 at 9:16 PM 'Brian Candler' via golang-nuts
wrote:
> Or it could be like https://pkg.go.dev/modernc.org/sqlite, which took the
> Sqlite C source code and transpiled it into pure Go.
It's both, depending on target. The targets supported by
ebitengine/purego[0] link dynamicall
Or it could be like https://pkg.go.dev/modernc.org/sqlite, which took the
Sqlite C source code and transpiled it into pure Go.
Refs:
https://twitter.com/bradfitz/status/855271867162083329?lang=en
https://groups.google.com/g/golang-nuts/c/QDEczMhlQBU/m/4lCn2kP0AwAJ
On Monday 14 October 2024 at 18
wow, impressive. but how does this work without C? don't you have to link
to some standard OS rendering frameworks which are most likely in C? or do
you communicate through syscalls?
On Wednesday, October 2, 2024 at 9:25:24 PM UTC+8 Mandolyte wrote:
> Worked! Thanks
>
> On Wednesday, October 2
Worked! Thanks
On Wednesday, October 2, 2024 at 9:18:41 AM UTC-4 Jan Mercl wrote:
> On Wed, Oct 2, 2024 at 3:07 PM Mandolyte wrote:
>
> > What did I do wrong?
>
> Copying the go.mod file effectively declares the code in hello.go to be in
> package modernc.org/tk9.0.
> That's the package hello.g
On Wed, Oct 2, 2024 at 3:07 PM Mandolyte wrote:
> What did I do wrong?
Copying the go.mod file effectively declares the code in hello.go to be in
package modernc.org/tk9.0.
That's the package hello.go imports, hence the import cycle. This works
here:
jnml@t3610:~/tmp$ mkdir tk
jnml@t3610:~/tmp$
It has been a long time since I have done any Go work, so probably my
ignorance... but I did the following:
- in an empty folder
- copied the hello.go from the examples folder
- copied the go.mod file from repo root folder
- ran `CGO_ENABLED=0 go run hello.go`
- with this result:
```
$ CGO_ENABLED
