Lines Matching refs:objects
228 compile the objects listed in $(isdn-y) and then run
231 Due to kbuild recognizing $(<module_name>-y) for composite objects,
248 Note: Of course, when you are building objects into the kernel,
258 There is also the possibility to list objects that will
260 All objects listed with lib-y are combined in a single
265 For consistency, objects listed in lib-m will be included in lib.a.
287 A Makefile is only responsible for building objects in its own
307 the directory, but also to decide whether or not to link objects from
310 When Kbuild descends into the directory with 'y', all built-in objects
316 that directory specifies obj-y, those objects will be left orphan.
321 do not contain kernel-space objects at all. A typical usage is to let
346 1) head objects
348 Some objects must be placed at the head of vmlinux. They are
352 arch/$(SRCARCH)/Makefile should specify such objects as head-y.
796 Host programs can be made up based on composite objects.
797 The syntax used to define composite objects for host programs is
798 similar to the syntax used for kernel objects.
799 $(<executable>-objs) lists all objects used to link the final
939 Userspace programs can be made up based on composite objects.
940 The syntax used to define composite objects for userspace programs is
941 similar to the syntax used for kernel objects.
942 $(<executable>-objs) lists all objects used to link the final
1098 The very first objects linked are listed in head-y, assigned by
1291 $(head-y) lists objects to be linked first in vmlinux.
1481 will be invoked for post-link objects (vmlinux and modules.ko)