Home | History | Annotate | Download | only in go

Lines Matching refs:cgo

558         // Cgo directives
559 CgoCFLAGS []string // cgo: flags for C compiler
560 CgoCPPFLAGS []string // cgo: flags for C preprocessor
561 CgoCXXFLAGS []string // cgo: flags for C++ compiler
562 CgoLDFLAGS []string // cgo: flags for linker
563 CgoPkgConfig []string // cgo: pkg-config names
589 CgoEnabled bool // whether cgo can be used
756 The first is the cgo tool, which is part of the Go distribution. For
757 information on how to use it see the cgo documentation (go doc cmd/cgo).
765 When either cgo or SWIG is used, go build will pass any .c, .m, .s,
784 functions exported using a cgo //export comment. Requires
790 be those functions exported using a cgo //export comment.
818 If the package uses cgo or SWIG, these will be compiled with the
822 C++ source files. Only useful with cgo or SWIG, and always
825 Objective-C source files. Only useful with cgo, and always
829 If the package uses cgo or SWIG, these will be assembled with the
1017 Environment variables for use with cgo:
1022 Whether the cgo command is supported. Either 0 or 1.
1024 Flags that cgo will pass to the compiler when compiling
1027 Flags that cgo will pass to the compiler when compiling
1030 Flags that cgo will pass to the compiler when compiling
1033 Flags that cgo will pass to the compiler when linking.
1057 when using -linkmode=auto with code that uses cgo.