| /OK3568_Linux_fs/yocto/poky/bitbake/lib/toaster/tests/browser/ |
| H A D | test_builddashboard_page_artifacts.py | 20 """ Tests for artifacts on the build dashboard /build/X """
39 Check whether the "Build artifacts" heading is visible (True if it
42 return self.element_exists('[data-heading="build-artifacts"]')
53 If a build produced no artifacts, the artifacts heading and images
65 # check build artifacts heading
66 msg = 'Build artifacts heading should not be displayed for non-image' \
76 If a build produced SDK artifacts, they should be shown, but the section
99 # check build artifacts heading
100 msg = 'Build artifacts heading should be displayed for SDK ' \
101 'builds which generate artifacts'
[all …]
|
| /OK3568_Linux_fs/yocto/poky/bitbake/lib/toaster/toastergui/templates/ |
| H A D | builddashboard.html | 80 <h2 data-heading="build-artifacts">Build artifacts</h2>
83 …<div class="well well-transparent dashboard-section" data-artifacts-for-target="{{target.target.pk…
129 <ul class="list-unstyled" data-links="image-artifacts">
141 Kernel artifacts
144 <ul class="list-unstyled" data-links="kernel-artifacts">
158 SDK artifacts
161 <ul class="list-unstyled" data-links="sdk-artifacts">
181 <!-- other artifacts -->
183 <h2>Other artifacts</h2>
188 …<span class="glyphicon glyphicon-question-sign get-help" title="Build artifacts discovered in <i>t…
[all …]
|
| /OK3568_Linux_fs/buildroot/support/misc/ |
| H A D | gitlab-ci.yml.in | 23 artifacts:
53 artifacts:
75 artifacts:
96 artifacts:
|
| /OK3568_Linux_fs/yocto/poky/scripts/lib/wic/ |
| H A D | help.py | 150 various build artifacts required to build the image.
154 the corresponding artifacts are typically found in a normal
163 artifacts from e.g. core-image-sato.
169 the boot artifacts (e.g. /EFI or /syslinux dirs) to use as the
193 When 'wic -e' is used, the locations for the build artifacts
619 OpenEmbedded build artifacts. Image generation is driven by
624 artifacts, the result is an image or set of images that can be
650 artifacts that will be used in creating the image: 'raw' and
653 If used in 'raw' mode, artifacts are explicitly specified via
658 artifacts used to create the image.
[all …]
|
| /OK3568_Linux_fs/buildroot/package/mender-artifact/ |
| H A D | Config.in.host | 6 Mender artifacts library.
9 Mender artifacts can contain binaries, metadata, checksums,
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-core/images/ |
| H A D | core-image-tiny-initramfs.bb | 5 actually generate an image but rather generates boot and rootfs artifacts \
21 # don't actually generate an image, just the artifacts needed for one
|
| /OK3568_Linux_fs/buildroot/package/mender/ |
| H A D | readme.txt | 8 such as 'mender-artifact' which is used to create Mender Artifacts
107 Creating Mender Artifacts
110 To create Mender Artifacts based on Buildroot build output you must
|
| /OK3568_Linux_fs/yocto/poky/scripts/ |
| H A D | wic | 123 raise WicError("The following build artifacts are not specified: %s" %
208 logger.info("Build artifacts not found, exiting.")
209 logger.info(" (Please check that the build artifacts for the machine")
211 logger.info(" are the correct artifacts for the image (.wks file)).\n")
321 help="name of the image to use the artifacts from "
327 help="path to the dir containing the boot artifacts "
|
| /OK3568_Linux_fs/yocto/poky/bitbake/lib/bb/ui/ |
| H A D | buildinfohelper.py | 703 Save SDK artifacts to the database, associating them with a
1560 # request archival of the project artifacts
1670 task_artifacts = task_vars['artifacts']
1725 Scan for built image artifacts in DEPLOY_DIR_IMAGE and associate them
1743 # any image artifacts, so we can return immediately
1850 # copy image files and build artifacts from the
1860 logger.info('image artifacts for target %s cloned from ' \
1867 Return targets which could generate SDK artifacts, i.e.
1889 # targets which might have created SDK artifacts
1892 # location of SDK artifacts
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/sound/soc/ |
| H A D | pops-clicks.rst | 5 Pops and clicks are unwanted audio artifacts caused by the powering up and down
37 Capture artifacts are somewhat easier to get rid as we can delay activating the
|
| /OK3568_Linux_fs/yocto/poky/meta/classes/ |
| H A D | toaster.bbclass | 340 # get list of artifacts from sstate manifest
359 artifacts = [fname.strip() for fname in fmanifest]
360 data = {"task": e.taskid, "artifacts": artifacts}
|
| H A D | kernel-artifact-names.bbclass | 4 # artifacts, but aren't kernel recipes themselves
|
| /OK3568_Linux_fs/external/xserver/hw/dmx/doc/ |
| H A D | scaled.xml | 168 rounding is incorrect and can cause artifacts.
175 errors do not create artifacts. This method is probably
216 eliminate artifacts caused by this problem,
235 wire, additional artifacts are introduced (because
252 Many of these artifacts could be eliminated if
255 properly aligned areas of damage. The remaining artifacts
690 this extension without introducing artifacts. This
|
| /OK3568_Linux_fs/external/rknpu2/examples/3rdparty/opencv/opencv-linux-aarch64/include/opencv2/stitching/detail/ |
| H A D | exposure_compensate.hpp | 99 /** @brief Exposure compensator which tries to remove exposure related artifacts by adjusting image
114 /** @brief Exposure compensator which tries to remove exposure related artifacts by adjusting image…
|
| /OK3568_Linux_fs/yocto/poky/bitbake/lib/toaster/tests/builds/ |
| H A D | README | 13 - TOASTER_DIR (where toaster keeps it's artifacts)
|
| /OK3568_Linux_fs/yocto/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-execution.rst | 607 The setscene process enables BitBake to handle "pre-built" artifacts.
608 The ability to handle and reuse these artifacts allows BitBake the
610 Instead, BitBake can use, when possible, existing build artifacts.
631 which it believes in can obtain artifacts.
638 executes and provides the necessary artifacts returning either success
|
| /OK3568_Linux_fs/yocto/poky/documentation/migration-guides/ |
| H A D | migration-1.8.rst | 72 shared work area and to place build artifacts separately in the source
76 ``${B}`` (build artifacts) are used correctly in functions such as
|
| /OK3568_Linux_fs/buildroot/ |
| H A D | .gitlab-ci.yml | 13 artifacts:
|
| /OK3568_Linux_fs/u-boot/board/phytec/pfla02/ |
| H A D | README | 18 This generates the artifacts SPL and u-boot.img.
|
| /OK3568_Linux_fs/yocto/poky/scripts/lib/wic/plugins/imager/ |
| H A D | direct.py | 164 For 'wic', we already have our build artifacts - we just create
165 filesystems from the artifacts directly and combine them into
225 Print the image(s) and artifacts used, for the user.
236 msg += 'The following build artifacts were used to create the image(s):\n'
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/mfd/ |
| H A D | twl4030-audio.txt | 14 - ti,digimic_delay: Delay need after enabling the digimic to reduce artifacts
|
| /OK3568_Linux_fs/u-boot/board/phytec/pcm058/ |
| H A D | README | 22 This generates the artifacts SPL and u-boot.img.
|
| /OK3568_Linux_fs/kernel/kernel/ |
| H A D | kheaders.c | 66 MODULE_DESCRIPTION("Echo the kernel header artifacts used to build the kernel");
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-connectivity/zeromq/files/ |
| H A D | 0001-CMakeLists-txt-Avoid-host-specific-path-to-libsodium.patch | 13 This change mitigates an issue stemming from reuse of build artifacts
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-core/initrdscripts/files/ |
| H A D | init-install-efi.sh | 287 # Copy kernel artifacts. To add more artifacts just add to types
|