Search results

From Yocto Project
Jump to navigationJump to search
  • <includeonly>{{Category|Top level}}
    0 members (0 subcategories, 0 files) - 22:18, 12 July 2012
  • ...irectory to contain binary images. Enough to get a board to boot with some level of functionality, keeping in mind that the larger the image, the longer it The top level directory of the meta-intel repo contains multiple BSPs, and classes, commo
    3 KB (529 words) - 16:37, 4 December 2013
  • ...ster information into the build controller process. This page is a '''high level''' look at the database design and how it is used. == Top level models ==
    8 KB (1,400 words) - 17:52, 10 February 2016
  • ...irectory to contain binary images. Enough to get a board to boot with some level of functionality, keeping in mind that the larger the image, the longer it The top level directory of the meta-intel repo contains multiple BSPs, and classes, commo
    4 KB (727 words) - 22:42, 1 July 2014
  • {{PD Help Page}} ...e, this page belongs to "[[:Category:Help]]". If you open the "[[:Category:Help]]" page, you will see a link to this page there.
    8 KB (1,339 words) - 22:18, 12 July 2012
  • [[File:0.0.Top_Header.jpg|600px|thumb|center|Top Header]] === High-level design feedback ===
    8 KB (1,151 words) - 14:50, 30 November 2015
  • constructing a particular target at process level. This article focus more on profiling than optimization, the former being to either plot the top N recipes-task stat values
    2 KB (265 words) - 21:12, 28 February 2017
  • 'git bisect' in it's most basic form can be used to help you identify which commit is broken by keeping track of known good and know ...For this we need to cd into build (as git bisect needs to run at the top level) and bitbake foo. If the build is successful then the script exits with su
    2 KB (416 words) - 15:40, 14 July 2016
  • ...s structured as a set of sub-commands under a 'top-level' command. The top-level command (yocto-bsp or yocto-kernel) itself does nothing but invoke or provide help on the sub-commands
    13 KB (2,115 words) - 19:32, 31 March 2012
  • * Tools to help manage the ongoing influx of CVEs (around 1000 per month) so that expert ti Here is a picture of the high level SRTool record structure:
    7 KB (1,145 words) - 23:41, 24 January 2019
  • !Support Level |-valign="top"
    13 KB (1,419 words) - 16:16, 10 May 2024
  • {{PD Help Page}} ...ng the “{{lcfirst:{{int:talk}}}}” [[Help:Navigation#Page tabs|tab]] at the top of the page. Simply edit the page as normal to add your comment.
    7 KB (1,170 words) - 22:18, 12 July 2012
  • ...the Security Response Tool (SRTool) development process. We hope this will help you start contributing to the project. The SRTool is based on the Yocto Pro Click on the "Login" button in the top bar, select "Request Account", fill in the information, Click "Sign Up", an
    14 KB (2,063 words) - 05:59, 30 November 2023
  • ...that there's a top-level command which essentially invokes multiple lower-level subcommands. To display help for a top-level command, simply invoke the command without any parameters:
    18 KB (2,603 words) - 13:54, 9 August 2012
  • ...that there's a top-level command which essentially invokes multiple lower-level subcommands. To display help for a top-level command, simply invoke the command without any parameters:
    21 KB (2,893 words) - 15:57, 9 August 2012
  • ...d run <code>make install-ptest</code> if there is such a target in the top-level <code>Makefile</code>. For packages where this is enough, you don't need to
    6 KB (967 words) - 14:36, 25 December 2023
  • ** python release.py --help will display your options. ...on. In this example, the staging directory will be created in the same top level dir as the candidate, and be called "yocto-2.3." i.e. https://autobuilder.
    6 KB (1,076 words) - 07:44, 3 May 2017
  • ...that had nowhere else to land. As a result the size of the manual and top level topics became overwhelming to the new developer who had just graduated from c) How to help them choose the right kernel
    11 KB (1,894 words) - 04:31, 14 July 2017
  • {{PD Help Page}} ...spaces'''", which differentiate between the purpose of the pages at a high level. Pages in certain namespaces can also have special properties or behave di
    12 KB (1,808 words) - 22:18, 12 July 2012
  • ...'<code><nowiki>{{FOO}}</nowiki></code>'''. As such, they look a lot like [[Help:Templates|templates]]. ...or '''<code><nowiki>{{#foo:...}}</nowiki></code>'''. See also {{mediawiki|Help:Extension:ParserFunctions}}.
    43 KB (5,612 words) - 22:18, 12 July 2012
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)