2012/05/06 21:41:36 go-app-builder: Failed parsing input (1 error) 2012/05/06 21:41:36 /path/to/myapp/code.google.com/p/freetype-go/example/round/main.go:36:28: composite struct literal image.Uniform with untagged fieldsWhich is weird for a few reasons:0. I'm not including main.go, nor is any of my dependencies.1. main.go is in package main and I would think app engine would have no reason to compile anything in package main, heck _my_ program isn't even in a package main2. It's not actually a compilation error on the commandline:3. It seems a problem if I run 'go vet' although it's not the same error message I get from the SDK:$ go vet main.gomain.go:36:28: image.Uniform struct literal uses untagged fieldsmain.go:44:8: code.google.com/p/freetype-go/freetype/raster.Point struct literal uses untagged fieldsmain.go:48:8: code.google.com/p/freetype-go/freetype/raster.Point struct literal uses untagged fieldsmain.go:52:16: code.google.com/p/freetype-go/freetype/raster.Point struct literal uses untagged fieldsmain.go:53:16: code.google.com/p/freetype-go/freetype/raster.Point struct literal uses untagged fieldsmain.go:53:43: code.google.com/p/freetype-go/freetype/raster.Point struct literal uses untagged fieldsmain.go:54:16: code.google.com/p/freetype-go/freetype/raster.Point struct literal uses untagged fieldsmain.go:54:43: code.google.com/p/freetype-go/freetype/raster.Point struct literal uses untagged fieldsmain.go:58:22: code.google.com/p/freetype-go/freetype/raster.Point struct literal uses untagged fieldsmain.go:60:16: code.google.com/p/freetype-go/freetype/raster.Point struct literal uses untagged fieldsOne last data point, not sure if it matters:$ go versiongo version go1.0.1Should I file a bug about this somewhere? or am I trying to put a round peg in a square hole?Bill
=I think this would mask the problem: if there is an unimported package (even if it's not main) that registers an HTTP handler in an init(), then that will become a part of your app. I would carefully include only the packages you import to avoid this sort of debugging headache.