| /OK3568_Linux_fs/kernel/tools/scripts/ |
| H A D | utilities.mak | 139 # Usage: absolute-executable-path-or-empty = $(call lookup,path)
147 # is-executable
149 # Usage: bool-value = $(call is-executable,path)
154 is-executable = $(call _is-executable-helper,$(shell-sq))
155 _is-executable-helper = $(shell sh -c $(_is-executable-sh))
156 _is-executable-sh = $(call shell-sq,test -f $(1) -a -x $(1) && echo y)
158 # get-executable
160 # Usage: absolute-executable-path-or-empty = $(call get-executable,path)
162 # The goal is to get an absolute path for an executable;
168 get-executable = $(if $(1),$(if $(is-absolute),$(_ge-abspath),$(lookup)))
[all …]
|
| /OK3568_Linux_fs/external/xserver/hw/xquartz/mach-startup/ |
| H A D | bundle_trampoline.c | 40 * versions of macOS require that the main executable of an app be Mach-O for full system
44 * 1) bash is seen as the responsible executable for Security & Privacy, and the user doesn't
47 * the subsequent spawn of the real executable under Rosetta rather than natively.
68 char *executable = NULL; in main() local
70 asprintf(&executable, "%s/X11.sh", executable_directory); in main()
71 if (access(executable, X_OK) == -1) { in main()
72 free(executable); in main()
73 asprintf(&executable, "%s/X11", executable_directory); in main()
75 assert(access(executable, X_OK) == 0); in main()
77 argv[0] = executable; in main()
[all …]
|
| /OK3568_Linux_fs/buildroot/package/python-setuptools/ |
| H A D | 0001-add-executable.patch | 4 Subject: [PATCH] add executable
9 Add a new --executable option to distribute so that we can
31 + ('executable=', 'e', "specify final destination interpreter path"),
39 + self.executable = None
51 + self.executable = None
56 + ('executable','executable')
64 exec_param = getattr(bs_cmd, 'executable', None)
65 + if self.executable is not None:
66 + exec_param = self.executable
|
| /OK3568_Linux_fs/yocto/poky/meta/files/common-licenses/ |
| H A D | CPOL-1.02 | 5 …his License is intended to allow developers to use the Source Code and Executable Files provided a…
8 - Source Code and Executable Files can be used in commercial applications;
9 - Source Code and Executable Files can be redistributed; and
24 …all articles written by Author which describes how the Source Code and Executable Files for the Wo…
30 …d. "Executable Files" refer to the executables, binary files, configuration and any required data …
34 …efers to the collection of source code and configuration files used to create the Executable Files.
38 …tion of files distributed by the Publisher, including the Source Code, Executable Files, binaries,…
46 …a. You may use the standard version of the Source Code or Executable Files in Your own application…
52 …d. You may distribute the standard version of the Executable Files and Source Code or Derivative W…
54 …nt. The author retains copyright to any such Articles. You may use the Executable Files and Source…
[all …]
|
| H A D | BitTorrent-1.1 | 16 2. Both Source Code and executable versions of the Licensed Product, including Modifications made b…
22 …executable versions of a Licensed Product, without paying a royalty or other fee to the Licensor o…
42 …ted by a Contributor or portions thereof, in both Source Code or as an executable program, either …
47 … by such Contributor or portions thereof, in both Source Code or as an executable program, either …
55 …bute. You agree not to offer or impose any terms on any Source Code or executable version of the L…
57 …executable or other form of the Licensed Product, or via a mechanism generally accepted in the sof…
67 …Executable Versions. You may distribute Licensed Product as an executable program under a license …
71 …Executable Versions of Licensed Products, Modifications or Derivative Works. Notwithstanding any p…
124 …tion files, scripts used to control compilation and installation of an executable program, or a li…
133 … License). You may not copy or use this file, in either source code or executable form, except in …
|
| H A D | APL-1.0 | 24 1.5. "EXECUTABLE" means the Licensed Work in any form other than Source Code.
46 …erface definition files, and scripts used to control compilation and installation of an executable.
74 in Source Code and Executable form, either with other Modifications, on an unmodified basis, or as …
82 in Source Code and Executable form, either with other Modifications, on an unmodified basis, or as …
107 … the beginning of all Source Code files, and viewable to a user in any executable such that the Li…
109 3.2. EXECUTABLE DISTRIBUTIONS OF THE LICENSED WORK.
111 …eof, in Executable form (an "EXECUTABLE DISTRIBUTION") to any third party, under the terms of Sect…
113 …Executable Distribution must be accompanied by the Source Code for the Licensed Work making up the…
115 …Executable Distribution must be accompanied with a written offer, valid for at least thirty six (3…
117 …any Licensed Work or portion thereof distributed to any third party in Executable form, whether su…
[all …]
|
| H A D | ErlPL-1.1 | 22 1.5. ``Executable`` means Covered Code in any form other than Source
53 compilation and installation of an Executable, or a list of source
121 an Executable version or via an accepted Electronic Distribution
122 Mechanism to anyone to whom you made an Executable version available;
138 Executable version or related documentation in which You describe the
183 3.6. Distribution of Executable Versions.
184 You may distribute Covered Code in Executable form only if the
190 in any notice in an Executable version, related documentation or
192 Covered Code. You may distribute the Executable version of Covered
195 of this License and that the license for the Executable version does
[all …]
|
| /OK3568_Linux_fs/kernel/scripts/kconfig/tests/ |
| H A D | conftest.py | 41 """Run text-based Kconfig executable and save the result.
49 returncode: exit status of the Kconfig executable
121 returncode: exit status of the Kconfig executable
131 returncode: exit status of the Kconfig executable
140 returncode: exit status of the Kconfig executable
148 returncode: exit status of the Kconfig executable
166 returncode: exit status of the Kconfig executable
174 returncode: exit status of the Kconfig executable
182 returncode: exit status of the Kconfig executable
190 returncode: exit status of the Kconfig executable
[all …]
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-networking/recipes-connectivity/ufw/ufw/ |
| H A D | 0003-only-make-one-reference-to-env.patch | 6 If sys.executable happens to be '/usr/bin/env python' or something
9 quick sanity check on sys.executable before doing the substitution.
25 condition is removed so the shebang line is substituted with the sys.executable
27 of sys.executable and replaces it with "#! /usr/bin/env python3".
64 + # Distutils searches for the string of sys.executable and replaces it
66 print("Updating staging/ufw to use %s" % (sys.executable))
69 - "1s%^#.*python.*%#! /usr/bin/env " + sys.executable + "%g",
70 + "1s%/.*python.*%" + sys.executable + "%g",
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/python/python3-installer/ |
| H A D | interpreter.patch | 21 + default=sys.executable,
22 + help=f"interpreter (defaults to {sys.executable})",
31 - interpreter=sys.executable,
40 @@ -59,20 +59,7 @@ def _build_shebang(executable: str, forlauncher: bool) -> bytes:
43 executable_bytes = executable.encode("utf-8")
49 - # Shebang support for an executable with a space in it is under-specified
55 - quoted = shlex.quote(executable).encode("utf-8")
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/lib/gcc/arm-none-linux-gnueabihf/10.3.1/plugin/include/ |
| H A D | domwalk.h | 36 blocks reachable by executable edges. */
44 are not executable.
49 edges it can determine are not executable.
53 determined to be not executable. */
58 non-executable edges to be merged in from an earlier analysis (and
59 potentially for additional edges to be marked as non-executable). */
81 outgoing edges should still be considered executable. A return value
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/lib/gcc/aarch64-none-linux-gnu/10.3.1/plugin/include/ |
| H A D | domwalk.h | 36 blocks reachable by executable edges. */
44 are not executable.
49 edges it can determine are not executable.
53 determined to be not executable. */
58 non-executable edges to be merged in from an earlier analysis (and
59 potentially for additional edges to be marked as non-executable). */
81 outgoing edges should still be considered executable. A return value
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/gdb/ |
| H A D | Separate-Debug-Files.html | 81 file separate from the executable itself, in a way that allows
84 than the executable code itself—some systems distribute debugging
92 <li> The executable contains a <em>debug link</em> that specifies the name of
94 usually <samp><var>executable</var>.debug</samp>, where <var>executable</var> is the
95 name of the corresponding executable file without leading directories
99 the executable and the debug file came from the same build.
101 </li><li> <a name="build-ID"></a>The executable contains a <em>build ID</em>, a unique bit string t…
116 the directory of the executable file, then in a subdirectory of that
119 the leading directories of the executable’s absolute file name. (On
120 MS-Windows/MS-DOS, the drive letter of the executable’s leading
[all …]
|
| H A D | qXfer-executable-filename-read.html | 18 <title>Debugging with GDB: qXfer executable filename read</title>
20 <meta name="description" content="Debugging with GDB: qXfer executable filename read">
21 <meta name="keywords" content="Debugging with GDB: qXfer executable filename read">
55 <meta http-equiv="Refresh" content="0; url=General-Query-Packets.html#qXfer-executable-filename-rea…
61 …ng for is at <a href="General-Query-Packets.html#qXfer-executable-filename-read">qXfer executable …
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/gdb/ |
| H A D | Separate-Debug-Files.html | 81 file separate from the executable itself, in a way that allows
84 than the executable code itself—some systems distribute debugging
92 <li> The executable contains a <em>debug link</em> that specifies the name of
94 usually <samp><var>executable</var>.debug</samp>, where <var>executable</var> is the
95 name of the corresponding executable file without leading directories
99 the executable and the debug file came from the same build.
101 </li><li> <a name="build-ID"></a>The executable contains a <em>build ID</em>, a unique bit string t…
116 the directory of the executable file, then in a subdirectory of that
119 the leading directories of the executable’s absolute file name. (On
120 MS-Windows/MS-DOS, the drive letter of the executable’s leading
[all …]
|
| H A D | qXfer-executable-filename-read.html | 18 <title>Debugging with GDB: qXfer executable filename read</title>
20 <meta name="description" content="Debugging with GDB: qXfer executable filename read">
21 <meta name="keywords" content="Debugging with GDB: qXfer executable filename read">
55 <meta http-equiv="Refresh" content="0; url=General-Query-Packets.html#qXfer-executable-filename-rea…
61 …ng for is at <a href="General-Query-Packets.html#qXfer-executable-filename-read">qXfer executable …
|
| /OK3568_Linux_fs/u-boot/scripts/ |
| H A D | Makefile.host | 10 # Will compile bin2hex.c and create an executable named bin2hex
14 # Will compile lxdialog.c and checklist.c, and then link the executable
21 # They are linked as C++ code to the executable qconf
93 # Create executable from a single .c file
94 # host-csingle -> Executable
101 # Link an executable based on list of .o files, all plain c
102 # host-cmulti -> executable
118 # Link an executable based on list of .o files, a mixture of .c and .cc
119 # host-cxxmulti -> executable
|
| /OK3568_Linux_fs/device/rockchip/common/linux-kbuild/armhf/linux-kbuild-4.4/scripts/ |
| H A D | Makefile.host | 10 # Will compile bin2hex.c and create an executable named bin2hex
14 # Will compile lxdialog.c and checklist.c, and then link the executable
21 # They are linked as C++ code to the executable qconf
85 # Create executable from a single .c file
86 # host-csingle -> Executable
93 # Link an executable based on list of .o files, all plain c
94 # host-cmulti -> executable
110 # Link an executable based on list of .o files, a mixture of .c and .cc
111 # host-cxxmulti -> executable
|
| /OK3568_Linux_fs/device/rockchip/common/linux-kbuild/aarch64/linux-kbuild-4.4/scripts/ |
| H A D | Makefile.host | 10 # Will compile bin2hex.c and create an executable named bin2hex
14 # Will compile lxdialog.c and checklist.c, and then link the executable
21 # They are linked as C++ code to the executable qconf
85 # Create executable from a single .c file
86 # host-csingle -> Executable
93 # Link an executable based on list of .o files, all plain c
94 # host-cmulti -> executable
110 # Link an executable based on list of .o files, a mixture of .c and .cc
111 # host-cxxmulti -> executable
|
| /OK3568_Linux_fs/kernel/scripts/ |
| H A D | Makefile.host | 28 # Will compile bin2hex.c and create an executable named bin2hex
32 # Will compile lxdialog.c and checklist.c, and then link the executable
39 # They are linked as C++ code to the executable qconf
89 # Create executable from a single .c file
90 # host-csingle -> Executable
97 # Link an executable based on list of .o files, all plain c
98 # host-cmulti -> executable
114 # Link an executable based on list of .o files, a mixture of .c and .cc
115 # host-cxxmulti -> executable
|
| /OK3568_Linux_fs/device/rockchip/common/linux-kbuild/armhf/linux-kbuild-5.10/scripts/ |
| H A D | Makefile.host | 28 # Will compile bin2hex.c and create an executable named bin2hex
32 # Will compile lxdialog.c and checklist.c, and then link the executable
39 # They are linked as C++ code to the executable qconf
89 # Create executable from a single .c file
90 # host-csingle -> Executable
97 # Link an executable based on list of .o files, all plain c
98 # host-cmulti -> executable
114 # Link an executable based on list of .o files, a mixture of .c and .cc
115 # host-cxxmulti -> executable
|
| /OK3568_Linux_fs/device/rockchip/common/linux-kbuild/aarch64/linux-kbuild-5.10/scripts/ |
| H A D | Makefile.host | 28 # Will compile bin2hex.c and create an executable named bin2hex
32 # Will compile lxdialog.c and checklist.c, and then link the executable
39 # They are linked as C++ code to the executable qconf
89 # Create executable from a single .c file
90 # host-csingle -> Executable
97 # Link an executable based on list of .o files, all plain c
98 # host-cmulti -> executable
114 # Link an executable based on list of .o files, a mixture of .c and .cc
115 # host-cxxmulti -> executable
|
| /OK3568_Linux_fs/buildroot/support/scripts/ |
| H A D | check-host-rpath | 43 # This function tells whether a given ELF executable (first argument)
46 # executable is available in the host library directory. This function
51 # function will check if the libraries needed by the executable are
52 # located (or not). In practice, the ELF executable RPATH may point to
54 # if such an executable is within the current package per-package host
73 # ELF executable (first argument) properly points to the host library
81 # directory will make sure the ELF executable will find at runtime the
|
| /OK3568_Linux_fs/external/rkwifibt/ |
| H A D | meson.build | 8 executable(
14 executable(
20 executable(
26 executable(
|
| /OK3568_Linux_fs/kernel/samples/bpf/ |
| H A D | Makefile.target | 10 # Will compile xsk_example.c and create an executable named xsk_example
14 # Will compile xdpsock_1.c and xdpsock_2.c, and then link the executable
52 # Create executable from a single .c file
53 # tprog-csingle -> Executable
60 # Link an executable based on list of .o files, all plain c
61 # tprog-cmulti -> executable
|