From: Sven Ebenfeld <sven.ebenfeld@gmail.com>
To: ss infod <ssinfod@gmail.com>,
"meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>
Subject: Re: Angstrom for i.mx 6
Date: Thu, 05 Mar 2015 19:05:30 +0100 [thread overview]
Message-ID: <54F89AEA.90706@gmail.com> (raw)
In-Reply-To: <CAHUo2cyzHcbkqZ8DpZD5hG7jRJ_jwfXrm=fXkKY5L2ZVU14OGQ@mail.gmail.com>
Am 05.03.2015 um 18:56 schrieb ss infod:
> Yes, I noticed that these machine configuration are there.
>
> However, I don't know what are the steps to use these machines
> configuration to build the angstrom distro ?
>
> Do I simply perform a git checkout of the Angstrom distro.
> git clone git://github.com/Angstrom-distribution/setup-scripts.git
>
> Then another checkout of the meta-fsl-arm-extra
>
> git://git.yoctoproject.org/meta-fsl-arm-extra
>
>
No, as stated in the manual you referred to, you need to run the
./oebb.sh script in setup-scripts. Before that, you should probably
checkout the angstrom-v2014.12-yocto1.7 branch (git checkout
angstrom-v2014.12-yocto1.7 in setup-scripts)
This script is creating config files for you and cloning the other layers.
Afterwards, you can find a script called something like
"environment-...". This script needs to be sourced (running: ".
./environment-...") every time you open a new console to run the OE build.
After you got the environment running, you can just choose the machine,
by putting it in front of the bitbake command.
>
> Then, do you think I would be able to build the distro with the MACHINE=
> 'imx6qsabrelite' ?
After you have followed the manual, yes.
>
> Is that correct ?
>
> Thanks for any input.
> ssinfod.
>
Cheers,
Sven
next prev parent reply other threads:[~2015-03-05 18:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 4:14 Angstrom for i.mx 6 ss infod
2015-03-05 7:38 ` Sven Ebenfeld
2015-03-05 17:56 ` ss infod
2015-03-05 18:05 ` Sven Ebenfeld [this message]
2015-03-05 18:05 ` Sven Ebenfeld
2015-03-08 5:26 ` ss infod
2015-03-09 17:35 ` Sven Ebenfeld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54F89AEA.90706@gmail.com \
--to=sven.ebenfeld@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=ssinfod@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.