| /OK3568_Linux_fs/kernel/scripts/package/ |
| H A D | buildtar | 20 tarball="${objtree}/linux-${KERNELRELEASE}-${ARCH}.tar" 32 tarball=${tarball}.gz 36 tarball=${tarball}.bz2 40 tarball=${tarball}.xz 152 tar cf $tarball -C $tmpdir $opts $dirs 154 echo "Tarball successfully created in $tarball"
|
| /OK3568_Linux_fs/buildroot/fs/tar/ |
| H A D | Config.in | 17 Do not compress the tarball. 22 Do compress the tarball with gzip. 27 Do compress the tarball with bzip2. 32 Do compress the tarball with lz4. 37 Do compress the tarball with lzma. 42 Do compress the tarball with lzop. 47 Do compress the tarball with xz.
|
| /OK3568_Linux_fs/yocto/poky/meta/lib/oeqa/sdk/ |
| H A D | case.py | 24 tarball = os.path.join(dl_dir, archive) 25 if os.path.exists(tarball): 26 return tarball 28 tarball = os.path.join(workdir, archive) 29 subprocess.check_output(["wget", "-O", tarball, url], stderr=subprocess.STDOUT) 30 return tarball
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-core/meta/ |
| H A D | testexport-tarball.bb | 1 DESCRIPTION = "SDK type target for standalone tarball containing packages defined by TEST_EXPORT_TO… 2 … tarball can be used to run missing programs on testing systems which don't have such tools.\ 3 This recipe is almost the same as buildtools-tarball" 4 SUMMARY = "Standalone tarball for test systems with missing software" 51 # However, testexport-tarball is inherently a tool set instead of a fully functional SDK, 65 # testexport-tarball doesn't need config site
|
| H A D | buildtools-docs-tarball.bb | 1 require recipes-core/meta/buildtools-tarball.bb 3 DESCRIPTION = "SDK type target for building a standalone tarball containing the tools needed to bui… 4 SUMMARY = "SDK type target for building a standalone tarball containing the tools needed to build t… 16 SDK_TITLE = "Docs Build tools tarball"
|
| H A D | buildtools-extended-tarball.bb | 1 require recipes-core/meta/buildtools-tarball.bb 3 DESCRIPTION = "SDK type target for building a standalone tarball containing build-essentials, pytho… 4 … make, git and tar. The tarball can be used to run bitbake builds on systems which don't meet the \ 6 SUMMARY = "Standalone tarball for running builds on systems with inadequate software and ancient co…
|
| H A D | buildtools-tarball.bb | 1 DESCRIPTION = "SDK type target for building a standalone tarball containing python3, chrpath, make,… 2 …tarball can be used to run bitbake builds on systems which don't meet the usual version requiremen… 3 SUMMARY = "Standalone tarball for running builds on systems with inadequate software" 102 # buildtools-tarball doesn't need config site
|
| /OK3568_Linux_fs/yocto/poky/meta/classes/ |
| H A D | npm.bbclass | 78 tarball = os.path.join(workdir, "%s-%s.tgz" % (base, j['version'])); 82 subprocess.run(['tar', 'czf', tarball, 90 return (tarball, j) 121 def _npm_cache_add(tarball, pkg): 122 """Add tarball to local registry and register it in the 124 registry.add_pkg(tarball, pkg) 126 def _npm_integrity(tarball): 127 """Return the npm integrity of a specified tarball""" 128 sha512 = bb.utils.sha512_file(tarball) 187 (tarball, pkg) = npm_pack(env, destdir, tmpdir) [all …]
|
| H A D | uninative.bbclass | 23 This event fires on the parent and will try to fetch the tarball if the 44 tarball = d.getVar("UNINATIVE_TARBALL") 46 tarballpath = os.path.join(tarballdir, tarball) 114 bb.warn("Disabling uninative as unable to fetch uninative tarball: %s" % str(exc)) 115 …bb.warn("To build your own uninative loader, please bitbake uninative-tarball and set UNINATIVE_TA… 117 bb.warn("Disabling uninative as unable to install uninative tarball: %s" % str(exc)) 118 …bb.warn("To build your own uninative loader, please bitbake uninative-tarball and set UNINATIVE_TA…
|
| /OK3568_Linux_fs/buildroot/docs/manual/ |
| H A D | using-buildroot-toolchain.txt | 17 +make sdk+. This generates a tarball of the content of the host directory 22 This tarball can then be distributed to application developers, when 26 Upon extracting the SDK tarball, the user must run the script 31 the tarball (e.g. because you will just be moving the +host+ directory, 32 or will be generating the tarball on your own), Buildroot also allows 34 generating a tarball.
|
| H A D | adding-packages-waf.txt | 31 On line 8 and 9, we declare the name of the tarball (xz-ed tarball 32 recommended) and the location of the tarball on the Web. Buildroot 33 will automatically download the tarball from this location. 66 the tree extracted by the tarball. If +HOST_LIBFOO_SUBDIR+ is not
|
| H A D | adding-packages-tips.txt | 183 - The tarball name generated by github matches the default one from 195 maintainer may have uploaded a release tarball, or the release may just point 196 to the automatically generated tarball from the git tag. If there is a 197 release tarball uploaded by the maintainer, we prefer to use that since it 201 You can see on the release page if it's an uploaded tarball or a git tag: 211 it's an automatically generated tarball and you should use the 229 By default, it will use a +.tar.gz+ tarball, but Gitlab also provides 231 +.tar.bz2+ tarball can be used: 240 If there is a specific tarball uploaded by the upstream developers in 242 rather use directly the link to the tarball.
|
| H A D | adding-packages-qmake.txt | 31 On line 8 and 9, we declare the name of the tarball (xz-ed tarball 32 recommended) and the location of the tarball on the Web. Buildroot 33 will automatically download the tarball from this location.
|
| H A D | adding-packages-rebar.txt | 30 On line 8 and 9, we declare the name of the tarball (xz-ed tarball 31 recommended) and the location of the tarball on the Web. Buildroot 32 will automatically download the tarball from this location.
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-extended/libwmf/ |
| H A D | libwmf_0.2.8.4.bb | 19 SRC_URI = "${SOURCEFORGE_MIRROR}/wvware/${BPN}/${PV}/${BPN}-${PV}.tar.gz;name=tarball \ 25 SRC_URI[tarball.md5sum] = "d1177739bf1ceb07f57421f0cee191e0" 26 SRC_URI[tarball.sha256sum] = "5b345c69220545d003ad52bfd035d5d6f4f075e65204114a9e875e84895a7cf8"
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-extended/blktool/ |
| H A D | blktool_4-7.1.bb | 12 …t.debian.org/archive/debian/20160728T043443Z/pool/main/b/${BPN}/${BPN}_4.orig.tar.gz;name=tarball \ 19 SRC_URI[tarball.md5sum] = "62edc09c9908107e69391c87f4f3fd40" 20 SRC_URI[tarball.sha256sum] = "b1e6d5912546d2a4b704ec65c2b9664aa3b4663e7d800e06803330335a2cb764"
|
| /OK3568_Linux_fs/yocto/poky/documentation/ref-manual/ |
| H A D | system-requirements.rst | 256 you can resolve this by installing a ``buildtools`` tarball that 257 contains these tools. You can get the tarball one of two ways: download 258 a pre-built tarball or use BitBake to build the tarball. 266 resolve this by installing a ``buildtools-extended`` tarball that 289 During execution, the buildtools tarball will be downloaded, the 300 in the ``buildtools-extended`` tarball, you can instead execute the 318 ``buildtools-extended`` tarball, additional working versions of tools 357 ``buildtools-extended`` tarball, additional working versions of tools 377 2. Run the BitBake command to build the tarball:: 379 $ bitbake buildtools-tarball [all …]
|
| /OK3568_Linux_fs/yocto/poky/meta/lib/oeqa/sdk/cases/ |
| H A D | buildlzip.py | 16 …tarball = self.fetch(testdir, self.td["DL_DIR"], "http://downloads.yoctoproject.org/mirror/sources… 23 subprocess.check_output(["tar", "xf", tarball, "-C", testdir], stderr=subprocess.STDOUT)
|
| H A D | buildcpio.py | 20 … tarball = self.fetch(testdir, self.td["DL_DIR"], "https://ftp.gnu.org/gnu/cpio/cpio-2.13.tar.gz") 27 subprocess.check_output(["tar", "xf", tarball, "-C", testdir], stderr=subprocess.STDOUT)
|
| H A D | buildepoxy.py | 24 …tarball = self.fetch(testdir, self.td["DL_DIR"], "https://github.com/anholt/libepoxy/releases/down… 31 subprocess.check_output(["tar", "xf", tarball, "-C", testdir], stderr=subprocess.STDOUT)
|
| H A D | assimp.py | 26 …tarball = self.fetch(testdir, self.td["DL_DIR"], "https://github.com/assimp/assimp/archive/v4.1.0.… 33 subprocess.check_output(["tar", "xf", tarball, "-C", testdir], stderr=subprocess.STDOUT)
|
| H A D | buildgalculator.py | 27 …tarball = self.fetch(testdir, self.td["DL_DIR"], "http://galculator.mnim.org/downloads/galculator-… 34 subprocess.check_output(["tar", "xf", tarball, "-C", testdir], stderr=subprocess.STDOUT)
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-extended/bash/ |
| H A D | bash_5.1.16.bb | 7 SRC_URI = "${GNU_MIRROR}/bash/${BP}.tar.gz;name=tarball \ 21 SRC_URI[tarball.sha256sum] = "5bac17218d3911834520dad13cd1f85ab944e1c09ae1aba55906be1f8192f558"
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-bsp/apmd/ |
| H A D | apmd_3.2.2-15.bb | 12 …bian.org/archive/debian/20160728T043443Z/pool/main/a/${BPN}/${BPN}_3.2.2.orig.tar.gz;name=tarball \ 24 SRC_URI[tarball.md5sum] = "b1e6309e8331e0f4e6efd311c2d97fa8" 25 SRC_URI[tarball.sha256sum] = "7f7d9f60b7766b852881d40b8ff91d8e39fccb0d1d913102a5c75a2dbb52332d"
|
| /OK3568_Linux_fs/buildroot/package/linux-headers/ |
| H A D | Config.in.host | 60 URL at kernel.org. Instead, select "Custom tarball" and 64 bool "Custom tarball" 67 source tarball. This URL can use any protocol recognized by 70 When pointing to a local tarball using file://, you may want 102 string "URL of custom kernel tarball"
|