if you compile and run .go file successfully on ppc32 then it will do the same in larger projects, but first you should know about project structure in go and for complex projects there is a lot to speak but for golang specific this is what I can share.

1. create your project root folder at set a project name to it, then run go mod init {git-repository-address like github.com/usr/project or your desired name}
2. create your project structure folders
3. each folder which needs a binary output better to have a cmd folder inside and you can only have a single cmd folder for whole project depends on size of project
4. after adding some .go files {and their corresponding _test files} in project we should run go mod tidy to download dependencies and you can do go mod vendor to save dependencies locally at a folder in project root named vendor
5. no you can run specific main function using go run {project-name}/path-to-go-file
6. to run tests you can do go test ./... don’t forget to apply linters to your project, for example golangci-lint and you better do it as a git hook before commit
7. for creating output you can do go buid {project-name}/path-to-go-file -o {output} in which you can also cross-compile and use env GOOS=linux GOARCH=amd64 CGO_ENABLED=1 go build {project-name}/path-to-go-file -o {output}