Go to file
Jeff Carr c847491037 trigger new version due to pkg vs sum error
somehow this happened somewhere in early 2025:

	root@b:~# go install go.wit.com/apps/forge@v0.22.110
	go: downloading go.wit.com/lib/fhelp v0.0.9
	go/pkg/mod/go.wit.com/apps/forge@v0.22.110/windowHowto.go:11:2: go.wit.com/lib/fhelp@v0.0.9: verifying module: checksum mismatch
	        downloaded: h1:Az6H6IFpel5Cm5Ok8LxfPErM0PnIGOc1tBN9yaCjUeA=
	        sum.golang.org: h1:4705J6yZ1g7YbOtNqBjVILzrR/oWIS0bfOWpG0WNGpI=

	SECURITY ERROR
	This download does NOT match the one reported by the checksum server.
	The bits may have been replaced on the origin server, or an attacker may
	have intercepted the download attempt.
2025-05-23 10:31:52 -05:00
.gitignore forgot .gitignore go.* 2025-01-13 09:20:48 -06:00
LICENSE trigger new version due to pkg vs sum error 2025-05-23 10:31:52 -05:00
Makefile make install 2025-01-13 06:03:49 -06:00
README.md trigger new version due to pkg vs sum error 2025-05-23 10:31:52 -05:00
goModClean.go add help for 'go-mod-clean' 2025-01-17 05:13:25 -06:00
goSrcFind.go code to determine the go src directory 2025-01-13 08:55:48 -06:00
goWork.go code to determine the go src directory 2025-01-13 08:55:48 -06:00
human.go expose func 2025-02-22 06:53:10 -06:00
linux.go first attempt to install protoc on linux 2025-02-12 15:10:50 -06:00
protoc.go parse out the uuid and version 2025-01-17 02:51:16 -06:00

README.md

forge help

This is some code to help new users compile the GO GUI plugins which can be rather difficult to figure out how to do.

Design Goals

  • automate the recovery and build process for GO plugins
  • handle input from STDIN when there is no GUI yet

Notes

Try to make things easy.