ref-manual: Updated bitbake/ section to remove wrapper script
Robert P. J. Day noted that the bitbake command no longer uses a wrapper as the section indicated. I have removed this reference. Reported-by: Robert P. J. Day <rpjday@crashcourse.ca> (From yocto-docs rev: ccdcf3d80f2e684877265d2dde8606ddeed4dfd2) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
abf9789893
commit
5eeb8e08cf
|
@ -39,23 +39,27 @@
|
|||
|
||||
<para>
|
||||
This directory includes a copy of BitBake for ease of use.
|
||||
The copy usually matches the current stable BitBake release from the BitBake project.
|
||||
The copy usually matches the current stable BitBake release from
|
||||
the BitBake project.
|
||||
BitBake, a
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink>
|
||||
interpreter, reads the Yocto Project metadata and runs the tasks
|
||||
interpreter, reads the Yocto Project Metadata and runs the tasks
|
||||
defined by that data.
|
||||
Failures are usually from the metadata and not from BitBake itself.
|
||||
Failures are usually from the Metadata and not from BitBake itself.
|
||||
Consequently, most users do not need to worry about BitBake.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
When you run the <filename>bitbake</filename> command, the wrapper script in
|
||||
<filename>scripts/</filename> is executed to run the main BitBake executable,
|
||||
which resides in the <filename>bitbake/bin/</filename> directory.
|
||||
Sourcing the <link linkend="structure-core-script"><filename>&OE_INIT_FILE;</filename></link>
|
||||
script places the <filename>scripts</filename> and <filename>bitbake/bin</filename>
|
||||
directories (in that order) into the shell's <filename>PATH</filename> environment
|
||||
variable.
|
||||
When you run the <filename>bitbake</filename> command, the
|
||||
main BitBake executable, which resides in the
|
||||
<filename>bitbake/bin/</filename> directory, starts.
|
||||
Sourcing an environment setup script (e.g.
|
||||
<link linkend="structure-core-script"><filename>&OE_INIT_FILE;</filename></link>
|
||||
or
|
||||
<link linkend="structure-memres-core-script"><filename>oe-init-build-env-memres</filename></link>)
|
||||
places the <filename>scripts</filename> and
|
||||
<filename>bitbake/bin</filename> directories (in that order) into
|
||||
the shell's <filename>PATH</filename> environment variable.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
|
Loading…
Reference in New Issue