Lines Matching refs:Linking
538 Linking
583 In essence, the _cgo_import.o file includes the extra linking
616 Internal and External Linking
618 The text above describes "internal" linking, in which cmd/link parses and
624 using internal linking, cmd/link can generate Go binaries by itself.
626 In order to allow linking arbitrary object files without requiring
627 dynamic libraries, cgo supports an "external" linking mode too. In
628 external linking mode, cmd/link does not process any host object files.
632 final executable. External linking avoids the dynamic library
649 must support both internal and external linking, depending on the
651 linking is probably fine, but if other packages are involved, so that there
652 are dependencies on libraries beyond libc, external linking is likely
654 information to support both linking modes, leaving the decision
655 to be made when linking the final binary.
657 Linking Directives
659 In either linking mode, package-specific directives must be passed
668 In internal linking mode, allow an unresolved reference to
694 In internal linking mode, use "<path>" as the dynamic linker
704 In internal linking mode, put the Go symbol
715 In external linking mode, allow unresolved references to
725 In external linking mode, put the Go symbol
733 In external linking mode, invoke the host linker (usually gcc)
742 internal and external linking; the linker will select the appropriate
743 subset for the chosen linking mode.
783 The linking directives are used according to the kind of final link
818 linker in external linking mode.
820 By default, cmd/link will decide the linking mode as follows: if the only
822 packages (net, os/user, runtime/cgo), cmd/link will use internal linking
824 will use external linking mode. The first rule means that a build of
842 These defaults mean that Go-aware build systems can ignore the linking
844 they can also control the linking details if desired.
