Lines Matching full:architecture

41 	=== 7 Architecture Makefiles
42 	   --- 7.1 Set variables to tweak the build to the architecture
46 	   --- 7.5 Architecture-specific boot images
86 architecture-specific information to the top Makefile.
113 *Arch developers* are people who work on an entire architecture, such
431 	Another example are the architecture-specific Makefiles which
579 	This functionality is useful for architecture Makefiles that try
783 for the target architecture (i.e. the same architecture as you are building
793 	built for the target architecture.
912 but in the architecture makefiles where the kbuild infrastructure
943 7 Architecture Makefiles
950 for said architecture.
967 6) Finally, the architecture-specific part does any required post processing
973 7.1 Set variables to tweak the build to the architecture
1026 	Append or modify as required per architecture.
1037 	Append or modify as required per architecture.
1127 	architecture itself.
1154 	machinery is all architecture-independent.
1172 	    and arch/$(ARCH)/Makefile only adds architecture-specific
1183 7.5 Architecture-specific boot images
1212 	There are no rules for naming architecture-specific targets,
1226 	An architecture shall always, per default, build a bootable image.
1357 	architecture Makefiles do no need to explicitly write out that rule.
1425 	architecture-specific files.
1444 	This pass runs after kallsyms generation. If the architecture
1482 	If an architecture uses a verbatim copy of a header from
1497 	When a header is exported where the architecture uses
1512 	If an architecture generates other header files alongside generic-y
1557 	This variable defines the target architecture, such as "i386",
1562 	host system architecture.  For a cross build, a user may
1571 	Use this for architecture-specific install targets.