For more about specifying packages, see 'go help packages'.
For more about where packages and binaries are installed,
-see 'go help gopath'.
+run 'go help gopath'. For more about calling between Go and C/C++,
+run 'go help c'.
See also: go install, go get, go clean.
`,
Additional help topics:
+ c calling between Go and C/C++
gopath GOPATH environment variable
packages description of package lists
remote remote import path syntax
For more about specifying packages, see 'go help packages'.
For more about where packages and binaries are installed,
-see 'go help gopath'.
+run 'go help gopath'. For more about calling between Go and C/C++,
+run 'go help c'.
See also: go install, go get, go clean.
See also: go fmt, go fix.
+Calling between Go and C
+
+There are two different ways to call between Go and C/C++ code.
+
+The first is the cgo tool, which is part of the Go distribution. For
+information on how to use it see the cgo documentation (godoc cmd/cgo).
+
+The second is the SWIG program, which is a general tool for
+interfacing between languages. For information on SWIG see
+http://swig.org/. When running go build, any file with a .swig
+extension will be passed to SWIG. Any file with a .swigcxx extension
+will be passed to SWIG with the -c++ option.
+
+When either cgo or SWIG is used, go build will pass any .c, .s, or .S
+files to the C compiler, and any .cc, .cpp, .cxx files to the C++
+compiler. The CC or CXX environment variables may be set to determine
+the C or C++ compiler, respectively, to use.
+
+
GOPATH environment variable
The Go path is used to resolve import statements.
package main
+var helpC = &Command{
+ UsageLine: "c",
+ Short: "calling between Go and C/C++",
+ Long: `
+There are two different ways to call between Go and C/C++ code.
+
+The first is the cgo tool, which is part of the Go distribution. For
+information on how to use it see the cgo documentation (godoc cmd/cgo).
+
+The second is the SWIG program, which is a general tool for
+interfacing between languages. For information on SWIG see
+http://swig.org/. When running go build, any file with a .swig
+extension will be passed to SWIG. Any file with a .swigcxx extension
+will be passed to SWIG with the -c++ option.
+
+When either cgo or SWIG is used, go build will pass any .c, .s, or .S
+files to the C compiler, and any .cc, .cpp, .cxx files to the C++
+compiler. The CC or CXX environment variables may be set to determine
+the C or C++ compiler, respectively, to use.
+ `,
+}
+
var helpPackages = &Command{
UsageLine: "packages",
Short: "description of package lists",