Searched refs:build (Results 1 – 25 of 601) sorted by relevance
12345678910>>...25
| /Linux-v5.4/tools/build/Documentation/ |
| D | Build.txt | 4 The perf build framework was adopted from the kernel build system, hence the
8 directories to nest for specific target to be build.
10 Unlike the kernel we don't have a single build object 'obj-y' list that where
12 carry a sources list for multiple build objects.
18 The build framework consists of 2 Makefiles:
21 Makefile.build
24 'Makefile.build' file is the makefile used from the outside. It's
27 $ make -f tools/build/Makefile.build srctree=$(KSRC) dir=$(DIR) obj=$(OBJECT)
33 OBJECT - is the name of the build object
47 the build to nested directories.
[all …]
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | Build.txt | 2 1) perf build
4 The perf build process consists of several separated building blocks,
11 Several makefiles govern the perf build:
18 main makefile that triggers build of all perf objects including
21 - tools/build/Makefile.build
22 main makefile of the build framework
24 - tools/build/Build.include
25 build framework generic definitions
28 makefiles that defines build objects
30 Please refer to tools/build/Documentation/Build.txt for more
[all …]
|
| /Linux-v5.4/drivers/block/paride/ |
| D | Kconfig | 17 connected through a parallel port. If you chose to build PARIDE
18 support into your kernel, you may answer Y here to build in the
19 parallel port IDE driver, otherwise you should answer M to build
33 connected through a parallel port. If you chose to build PARIDE
34 support into your kernel, you may answer Y here to build in the
36 build it as a loadable module. The module will be called pcd. You
49 connected through a parallel port. If you chose to build PARIDE
50 support into your kernel, you may answer Y here to build in the
52 to build it as a loadable module. The module will be called pf.
63 connected through a parallel port. If you chose to build PARIDE
[all …]
|
| /Linux-v5.4/drivers/staging/speakup/ |
| D | Kconfig | 49 synthesizer. You can say y to build it into the kernel,
50 or m to build it as a module. See the configuration
58 synthesizer. You can say y to build it into the kernel,
59 or m to build it as a module. See the configuration
66 synthesizer. You can say y to build it into the kernel,
67 or m to build it as a module. See the configuration
74 You can say y to build it into the kernel, or m to
75 build it as a module. See the configuration help on the
82 synthesizer. You can say y to build it into the kernel,
83 or m to build it as a module. See the configuration
[all …]
|
| /Linux-v5.4/tools/build/ |
| D | Makefile.include | 2 build := -f $(srctree)/tools/build/Makefile.build dir=. obj
5 $(Q)$(MAKE) -C $(srctree)/tools/build CFLAGS= LDFLAGS= $(OUTPUT)fixdep
8 $(Q)$(MAKE) -C $(srctree)/tools/build clean
|
| D | Makefile.build | 27 build-dir := $(srctree)/tools/build
31 fixdep := $(build-dir)/fixdep
37 include $(build-dir)/Build.include
51 build-file := $(dir)/Build
52 -include $(build-file)
139 $(Q)$(MAKE) -f $(build-dir)/Makefile.build dir=$(dir)/$@ obj=$(obj)
|
| D | Makefile | 33 build := -f $(srctree)/tools/build/Makefile.build dir=. obj macro
43 $(Q)$(MAKE) $(build)=fixdep
|
| /Linux-v5.4/samples/bpf/ |
| D | README.rst | 26 This will creates a local "usr/include" directory in the git/build top
48 By default llvm will build all non-experimental backends including bpf.
54 (build dependencies are cmake and gcc-c++)::
59 $ cd ..; mkdir build; cd build
66 make samples/bpf/ LLC=~/git/llvm/build/bin/llc CLANG=~/git/llvm/build/bin/clang
71 environment variables before calling make. This will direct make to build
76 make samples/bpf/ LLC=~/git/llvm/build/bin/llc CLANG=~/git/llvm/build/bin/clang
|
| /Linux-v5.4/tools/build/tests/ex/ |
| D | Makefile | 9 include $(srctree)/tools/build/Makefile.include
15 make -f $(srctree)/tools/build/Makefile.build dir=. $@
18 make $(build)=ex
21 make $(build)=libex
|
| /Linux-v5.4/tools/perf/ |
| D | Makefile.perf | 212 include $(srctree)/tools/build/Makefile.include
594 build := -f $(srctree)/tools/build/Makefile.build dir=. obj
597 $(Q)$(MAKE) $(build)=perf
600 $(Q)$(MAKE) -f $(srctree)/tools/build/Makefile.build dir=pmu-events obj=jevents
606 $(Q)$(MAKE) -f $(srctree)/tools/build/Makefile.build dir=pmu-events obj=pmu-events
613 $(Q)$(MAKE) $(build)=gtk
659 build-dir = $(if $(__build-dir),$(__build-dir),.)
686 $(Q)$(MAKE) -f $(srctree)/tools/build/Makefile.build dir=$(build-dir) $@
689 $(Q)$(MAKE) -f $(srctree)/tools/build/Makefile.build dir=$(build-dir) $@
692 $(Q)$(MAKE) -f $(srctree)/tools/build/Makefile.build dir=$(build-dir) $@
[all …]
|
| /Linux-v5.4/tools/testing/selftests/rcutorture/bin/ |
| D | parse-build.sh | 18 T=${TMPDIR-/tmp}/parse-build.sh.$$
28 print_bug $title no build
34 print_bug $title build errors:
45 print_warning $title build errors:
|
| /Linux-v5.4/Documentation/dev-tools/ |
| D | gdb-kernel-debugging.rst | 39 this mode. In this case, you should build the kernel with
51 - cd /path/to/linux-build
58 add-auto-load-safe-path /path/to/linux-build
74 scanning for modules in /home/user/linux/build
75 loading @0xffffffffa0020000: /home/user/linux/build/net/netfilter/xt_tcpudp.ko
76 loading @0xffffffffa0016000: /home/user/linux/build/net/netfilter/xt_pkttype.ko
77 loading @0xffffffffa0002000: /home/user/linux/build/net/netfilter/xt_limit.ko
78 loading @0xffffffffa00ca000: /home/user/linux/build/net/packet/af_packet.ko
79 loading @0xffffffffa003c000: /home/user/linux/build/fs/fuse/fuse.ko
81 loading @0xffffffffa0000000: /home/user/linux/build/drivers/ata/ata_generic.ko
[all …]
|
| /Linux-v5.4/drivers/iio/dac/ |
| D | Kconfig | 13 Say yes here to build support for Analog Devices AD5024, AD5025, AD5044,
27 Say yes here to build support for Analog Devices AD5360, AD5361,
40 Say yes here to build support for Analog Devices AD5380, AD5381,
51 Say yes here to build support for Analog Devices AD5421 loop-powered
61 Say yes here to build support for Analog Devices AD5300, AD5301, AD5310,
74 Say yes here to build support for Analog Devices AD5415, AD5426, AD5429,
89 Say yes here to build support for Analog Devices AD5592R
101 Say yes here to build support for Analog Devices AD5593R
111 Say yes here to build support for Analog Devices AD5504, AD5501,
121 Say yes here to build support for Analog Devices AD5624R, AD5644R and
[all …]
|
| /Linux-v5.4/drivers/iio/potentiometer/ |
| D | Kconfig | 13 Say yes here to build support for the Analog Devices AD5272 and AD5274
23 Say yes here to build support for the Maxim Integrated DS1803
33 Say yes here to build support for the Maxim
44 Say yes here to build support for the Maxim
55 Say yes here to build support for the Maxim
66 Say yes here to build support for the Microchip
77 Say yes here to build support for the Microchip
95 Say yes here to build support for the Microchip
109 Say yes here to build support for the Microchip
122 Say yes here to build support for the Texas Instruments
|
| /Linux-v5.4/drivers/staging/isdn/gigaset/ |
| D | Kconfig | 14 This will build a module called "gigaset".
15 Note: If you build your ISDN subsystem (ISDN_CAPI or ISDN_I4L)
16 as a module, you have to build this driver as a module too,
30 Say N to build the old native ISDN4Linux variant.
39 This will build a module called "bas_gigaset".
47 This will build a module called "usb_gigaset".
54 This will build a module called "ser_gigaset".
|
| /Linux-v5.4/drivers/iio/accel/ |
| D | Kconfig | 15 Say Y here to build support for Analog Devices adis16201 dual-axis
27 Say Y here to build support for Analog Devices adis16209 dual-axis digital inclinometer
43 Say Y here if you want to build support for the Analog Devices
57 Say Y here if you want to build support for the Analog Devices
97 Say Y here if you want to build a driver for the Bosch BMA180 or
123 Say yes here to build support for the following Bosch accelerometers:
142 Say yes here to build support for the MiraMEMS DA280 3-axis 14-bit
152 Say yes here to build support for the MiraMEMS DA311 3-axis 12-bit
163 Say yes here to build support for the Domintech low-g tri-axial
176 Choosing M will build the driver as a module. If so, the module
[all …]
|
| /Linux-v5.4/tools/testing/ktest/ |
| D | config-bisect.pl | 66 my $build;
582 doprint "READY TO TEST .config IN $build\n";
646 $build = $val;
670 $build = $tree if (!defined($build));
673 $build = expand_path $build;
679 if ( ! -d $build ) {
680 die "$build not a directory\n";
704 if ($build ne $tree) {
705 $make = "make O=$build"
708 $output_config = "$build/.config";
|
| /Linux-v5.4/Documentation/kbuild/ |
| D | reproducible-builds.rst | 7 exactly the same. This makes it possible to verify that the build
57 to an absolute filename in an out-of-tree build. Kbuild automatically
67 The build processes for some programs under the ``tools/``
69 cause a later source package build using e.g. ``make rpm-pkg`` to
78 generate a different temporary key for each build, resulting in the
82 One approach to this is to divide up the build process so that the
96 4. Perform a second build that attaches the module signatures. It
113 Once you set all the necessary variables for a reproducible build, a
122 .. _KBUILD_BUILD_TIMESTAMP: kbuild.html#kbuild-build-timestamp
123 .. _KBUILD_BUILD_USER and KBUILD_BUILD_HOST: kbuild.html#kbuild-build-user-kbuild-build-host
[all …]
|
| /Linux-v5.4/drivers/iio/chemical/ |
| D | Kconfig | 16 Say Y here to build I2C interface support for the following
32 Say yes here to build support for Bosch Sensortec BME680 sensor with
54 Say Y here to build I2C interface support for the AMS
61 Say Y here to build I2C interface support for the AMS
70 Say Y here to build support for the Plantower PMS7003 particulate
81 Say Y here to build I2C interface support for the following
94 Say Y here to build support for the Sensirion SPS30 particulate
104 Say Y here to build I2C interface support for the SGX
|
| /Linux-v5.4/drivers/iio/pressure/ |
| D | Kconfig | 13 Say yes here to build support for the Honeywell ABP pressure
26 Say yes here to build support for Bosch Sensortec BMP180 and BMP280
50 Say yes here to build support for the Barometer sensor when
75 Say yes here to build support for the HID SENSOR
86 Say yes here to build support for Hope RF HP03 pressure and
100 Say yes here to build support for the Freescale MPL115A2
111 Say yes here to build support for the Freescale MPL115A1
123 Say yes here to build support for the Freescale MPL3115A2
134 Say Y here to build support for the Measurement Specialties
144 Say Y here to build I2C bus support for MS5611.
[all …]
|
| /Linux-v5.4/arch/s390/ |
| D | Makefile | 150 $(Q)$(MAKE) $(build)=$(boot) $@
153 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
156 $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
159 $(Q)$(MAKE) $(build)=arch/$(ARCH)/kernel/vdso64 $@
160 $(Q)$(MAKE) $(build)=arch/$(ARCH)/kernel/vdso32 $@
167 $(Q)$(MAKE) $(build)=$(syscalls) uapi
170 $(Q)$(MAKE) $(build)=$(syscalls) kapi
171 $(Q)$(MAKE) $(build)=$(tools) kapi
|
| /Linux-v5.4/ |
| D | Makefile | 262 config-build :=
263 mixed-build :=
266 single-build :=
286 config-build := 1
288 mixed-build := 1
295 single-build := 1
297 mixed-build := 1
304 mixed-build := 1
311 mixed-build := 1
315 ifdef mixed-build
[all …]
|
| /Linux-v5.4/drivers/iio/proximity/ |
| D | Kconfig | 14 Say Y here to build SPI interface support for the Austrian
31 Say Y here if you want to build a driver for the Intersil ISL29501
43 Say Y to build a driver for PulsedLight LIDAR range finding
53 Say Y to build a driver for the ultrasonic sensors I2CXL of
65 Say Y to build a driver for the RFD77402 Time-of-Flight (distance)
75 Say Y here to build a driver for GPIO bitbanged ultrasonic
96 Say Y here to build a driver for Semtech's SX9500 capacitive
108 Say Y here to build a driver for Devantech SRF02/SRF08/SRF10
119 Say Y here to build a driver for STMicroelectronics VL53L0X
|
| /Linux-v5.4/tools/gpio/ |
| D | Makefile | 27 include $(srctree)/tools/build/Makefile.include
40 $(Q)$(MAKE) $(build)=gpio-utils
47 $(Q)$(MAKE) $(build)=lsgpio
56 $(Q)$(MAKE) $(build)=gpio-hammer
65 $(Q)$(MAKE) $(build)=gpio-event-mon
|
| /Linux-v5.4/drivers/net/wireless/realtek/rtlwifi/ |
| D | Kconfig | 24 If you choose to build it as a module, it will be called rtl8192ce
35 If you choose to build it as a module, it will be called rtl8192se
46 If you choose to build it as a module, it will be called rtl8192de
59 If you choose to build it as a module, it will be called rtl8723ae
72 If you choose to build it as a module, it will be called rtl8723be
83 If you choose to build it as a module, it will be called rtl8188ee
95 If you choose to build it as a module, it will be called rtl8192ee
107 If you choose to build it as a module, it will be called rtl8821ae
119 If you choose to build it as a module, it will be called rtl8192cu
|
12345678910>>...25
