documentation: Fixed links for yocto-1.1
After greping through the documentation directory, I addressed all the <ulink> statements that used to have yocto-1.0 in the URL. They are now yocto-1.1. (From yocto-docs rev: 97d160263c5905fdeaf4ec285bc5359918790581) 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
bc885cd8d3
commit
51b3d9dd53
|
@ -56,7 +56,7 @@
|
||||||
<para>
|
<para>
|
||||||
The ADT Installer is contained in the ADT Installer tarball.
|
The ADT Installer is contained in the ADT Installer tarball.
|
||||||
You can download the tarball into any directory from
|
You can download the tarball into any directory from
|
||||||
<ulink url='http://autobuilder.yoctoproject.org/downloads/yocto-1.1/adt-installer/'></ulink>.
|
<ulink url='http://www.yoctoproject.org/downloads/yocto-1.1/adt-installer/'></ulink>.
|
||||||
Or, you can use BitBake to generate the tarball inside the existing Yocto Project
|
Or, you can use BitBake to generate the tarball inside the existing Yocto Project
|
||||||
build tree.
|
build tree.
|
||||||
</para>
|
</para>
|
||||||
|
|
|
@ -553,12 +553,12 @@ WRITER NOTE: The areas to get the kernel and root filesystem are located in the
|
||||||
(QEMU or real hardware), the area you get the image from differs.
|
(QEMU or real hardware), the area you get the image from differs.
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem><para>Download the image from
|
<listitem><para>Download the image from
|
||||||
<ulink url='http://autobuilder.yoctoproject.org/downloads/yocto-1.0/machines/'>
|
<ulink url='http://www.yoctoproject.org/downloads/yocto-1.1/machines/'>
|
||||||
<filename>machines</filename></ulink> if your target architecture is supported
|
<filename>machines</filename></ulink> if your target architecture is supported
|
||||||
and you are going to develop and test your application on actual hardware.
|
and you are going to develop and test your application on actual hardware.
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
<listitem><para>Download the image from the
|
<listitem><para>Download the image from the
|
||||||
<ulink url='http://autobuilder.yoctoproject.org/downloads/yocto-1.0/machines/qemu/'>
|
<ulink url='http://www.yoctoproject.org/downloads/yocto-1.1/machines/qemu/'>
|
||||||
<filename>machines/qemu</filename></ulink> if your target architecture is supported
|
<filename>machines/qemu</filename></ulink> if your target architecture is supported
|
||||||
and you are going to develop and test your application using the QEMU
|
and you are going to develop and test your application using the QEMU
|
||||||
emulator.</para></listitem>
|
emulator.</para></listitem>
|
||||||
|
@ -637,7 +637,7 @@ WRITER NOTE: The areas to get the kernel and root filesystem are located in the
|
||||||
several target architectures and has many pre-built kernel images and root filesystem
|
several target architectures and has many pre-built kernel images and root filesystem
|
||||||
images.</para>
|
images.</para>
|
||||||
<para>If you are going to develop your application on hardware, go to the
|
<para>If you are going to develop your application on hardware, go to the
|
||||||
<ulink url='http://autobuilder.yoctoproject.org/downloads/yocto-1.0/machines/'>
|
<ulink url='http://www.yoctoproject.org/downloads/yocto-1.1/machines/'>
|
||||||
<filename>machines</filename></ulink> download area and choose a target machine area
|
<filename>machines</filename></ulink> download area and choose a target machine area
|
||||||
from which to download the kernel image and root filesystem.
|
from which to download the kernel image and root filesystem.
|
||||||
This download area could have several files in it that support development using
|
This download area could have several files in it that support development using
|
||||||
|
@ -647,7 +647,7 @@ WRITER NOTE: The areas to get the kernel and root filesystem are located in the
|
||||||
Be sure to get the files you need for your particular development process.</para>
|
Be sure to get the files you need for your particular development process.</para>
|
||||||
<para>If you are going to develop your application and then run and test it using the QEMU
|
<para>If you are going to develop your application and then run and test it using the QEMU
|
||||||
emulator, go to the
|
emulator, go to the
|
||||||
<ulink url='http://autobuilder.yoctoproject.org/downloads/yocto-1.0/machines/qemu/'>
|
<ulink url='http://www.yoctoproject.org/downloads/yocto-1.1/machines/qemu/'>
|
||||||
<filename>machines/qemu</filename></ulink> download area.
|
<filename>machines/qemu</filename></ulink> download area.
|
||||||
From this area, go down into the directory for your target architecture
|
From this area, go down into the directory for your target architecture
|
||||||
(e.g. <filename>qemux86_64</filename> for an
|
(e.g. <filename>qemux86_64</filename> for an
|
||||||
|
|
|
@ -101,7 +101,7 @@
|
||||||
<para>
|
<para>
|
||||||
<imagedata fileref="figures/source-repos.png" align="center" width="6in" depth="4in" />
|
<imagedata fileref="figures/source-repos.png" align="center" width="6in" depth="4in" />
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
<listitem><para><anchor id='index-downloads' /><emphasis><ulink url='http://autobuilder.yoctoproject.org/downloads/'>Index of /downloads:</ulink></emphasis>
|
<listitem><para><anchor id='index-downloads' /><emphasis><ulink url='http://www.yoctoproject.org/downloads/'>Index of /downloads:</ulink></emphasis>
|
||||||
This area contains an index of downloads such as
|
This area contains an index of downloads such as
|
||||||
the <trademark class='trade'>Eclipse</trademark>
|
the <trademark class='trade'>Eclipse</trademark>
|
||||||
Yocto Plug-in, miscellaneous support, Poky, pseudo, cross-development toolchains,
|
Yocto Plug-in, miscellaneous support, Poky, pseudo, cross-development toolchains,
|
||||||
|
@ -116,7 +116,7 @@
|
||||||
This page on the Yocto Project website allows you to download any Yocto Project
|
This page on the Yocto Project website allows you to download any Yocto Project
|
||||||
release or Board Support Package (BSP) in tarball form.
|
release or Board Support Package (BSP) in tarball form.
|
||||||
The tarballs are similar to those found in the
|
The tarballs are similar to those found in the
|
||||||
<ulink url='http://autobuilder.yoctoproject.org/downloads/'>Index of /downloads:</ulink> area.</para>
|
<ulink url='http://www.yoctoproject.org/downloads/'>Index of /downloads:</ulink> area.</para>
|
||||||
<para>
|
<para>
|
||||||
<imagedata fileref="figures/yp-download.png" align="center" width="6in" depth="4in" />
|
<imagedata fileref="figures/yp-download.png" align="center" width="6in" depth="4in" />
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
|
|
|
@ -914,7 +914,7 @@
|
||||||
Experience shows that buildbot is a good fit for this role.
|
Experience shows that buildbot is a good fit for this role.
|
||||||
What works well is to configure buildbot to make two types of builds:
|
What works well is to configure buildbot to make two types of builds:
|
||||||
incremental and full (from scratch).
|
incremental and full (from scratch).
|
||||||
See <ulink url='http://autobuilder.yoctoproject.org:8010'>the buildbot for the
|
See <ulink url='http://www.yoctoproject.org:8010'>the buildbot for the
|
||||||
Yocto Project</ulink> for an example implementation that uses buildbot.
|
Yocto Project</ulink> for an example implementation that uses buildbot.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
|
|
@ -33,8 +33,8 @@
|
||||||
You can use a stand-alone tarball to provide Python 2.6.
|
You can use a stand-alone tarball to provide Python 2.6.
|
||||||
You can find pre-built 32 and 64-bit versions of Python 2.6 at the following locations:
|
You can find pre-built 32 and 64-bit versions of Python 2.6 at the following locations:
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem><para><ulink url='http://autobuilder.yoctoproject.org/downloads/miscsupport/yocto-1.0-python-nativesdk/python-nativesdk-standalone-i686.tar.bz2'>32-bit tarball</ulink></para></listitem>
|
<listitem><para><ulink url='http://www.yoctoproject.org/downloads/miscsupport/yocto-1.1-python-nativesdk/python-nativesdk-standalone-i686.tar.bz2'>32-bit tarball</ulink></para></listitem>
|
||||||
<listitem><para><ulink url='http://autobuilder.yoctoproject.org/downloads/miscsupport/yocto-1.0-python-nativesdk/python-nativesdk-standalone-x86_64.tar.bz2'>64-bit tarball</ulink></para></listitem>
|
<listitem><para><ulink url='http://www.yoctoproject.org/downloads/miscsupport/yocto-1.1-python-nativesdk/python-nativesdk-standalone-x86_64.tar.bz2'>64-bit tarball</ulink></para></listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
|
@ -237,7 +237,7 @@
|
||||||
<question>
|
<question>
|
||||||
<para>
|
<para>
|
||||||
I see lots of 404 responses for files on
|
I see lots of 404 responses for files on
|
||||||
<filename>http://autobuilder.yoctoproject.org/sources/*</filename>. Is something wrong?
|
<filename>http://www.yoctoproject.org/sources/*</filename>. Is something wrong?
|
||||||
</para>
|
</para>
|
||||||
</question>
|
</question>
|
||||||
<answer>
|
<answer>
|
||||||
|
@ -520,10 +520,10 @@
|
||||||
configuration file:
|
configuration file:
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
PREMIRRORS_prepend = "\
|
PREMIRRORS_prepend = "\
|
||||||
git://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
|
git://.*/.* http://www.yoctoproject.org/sources/ \n \
|
||||||
ftp://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
|
ftp://.*/.* http://www.yoctoproject.org/sources/ \n \
|
||||||
http://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
|
http://.*/.* http://www.yoctoproject.org/sources/ \n \
|
||||||
https://.*/.* http://autobuilder.yoctoproject.org/sources/ \n"
|
https://.*/.* http://www.yoctoproject.org/sources/ \n"
|
||||||
</literallayout>
|
</literallayout>
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
|
@ -564,9 +564,9 @@
|
||||||
configuration file as long as the PREMIRROR server is up to date:
|
configuration file as long as the PREMIRROR server is up to date:
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
PREMIRRORS_prepend = "\
|
PREMIRRORS_prepend = "\
|
||||||
ftp://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
|
ftp://.*/.* http://www.yoctoproject.org/sources/ \n \
|
||||||
http://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
|
http://.*/.* http://www.yoctoproject.org/sources/ \n \
|
||||||
https://.*/.* http://autobuilder.yoctoproject.org/sources/ \n"
|
https://.*/.* http://www.yoctoproject.org/sources/ \n"
|
||||||
BB_FETCH_PREMIRRORONLY = "1"
|
BB_FETCH_PREMIRRORONLY = "1"
|
||||||
</literallayout>
|
</literallayout>
|
||||||
These changes would cause Poky to successfully fetch source over HTTP and
|
These changes would cause Poky to successfully fetch source over HTTP and
|
||||||
|
|
|
@ -106,7 +106,7 @@
|
||||||
<listitem><para><emphasis>Releases:</emphasis> Stable, tested releases are available through
|
<listitem><para><emphasis>Releases:</emphasis> Stable, tested releases are available through
|
||||||
<ulink url='http://yoctoproject.org/downloads/poky/'/>.</para></listitem>
|
<ulink url='http://yoctoproject.org/downloads/poky/'/>.</para></listitem>
|
||||||
<listitem><para><emphasis>Nightly Builds:</emphasis> These releases are available at
|
<listitem><para><emphasis>Nightly Builds:</emphasis> These releases are available at
|
||||||
<ulink url='http://autobuilder.yoctoproject.org/'/>.
|
<ulink url='http://autobuilder.yoctoproject.org/nightly'/>.
|
||||||
These builds include Yocto Project releases, meta-toolchain tarballs, and
|
These builds include Yocto Project releases, meta-toolchain tarballs, and
|
||||||
experimental builds.</para></listitem>
|
experimental builds.</para></listitem>
|
||||||
<listitem><para><emphasis>Yocto Project Website:</emphasis> You can find releases
|
<listitem><para><emphasis>Yocto Project Website:</emphasis> You can find releases
|
||||||
|
|
Loading…
Reference in New Issue