title: Setting CGO_CFLAGS persistently in a Go package?
body: <p>My Go package includes a .c file that uses a library which needs certain CFLAGS set.  On the command line to "go install" I can specify <code>CGO_CFLAGS</code> with the needed flags, and everything works.  However, I would like to make it so that someone can "go get" my package and build it without passing any extra command line arguments.</p>
  
  <p>Does the Go packaging system provide a place where I could put some config like this, to specify some arguments that are always needed when <code>go install</code>ing a package?</p>
  
  <p>(I'm aware of doing <code>#cgo CFLAGS:</code> directives in Go source files, but recall that in my package I have a .c source file so need the CGO_CFLAGS setting to the overall build process)</p>