This is not available in the currently released documentation. Perhaps, it is available in the next, but even then, we would need a more thorough documentation, preferably with a concrete example. See, what the Linaro guys wrote up for reference: http://arago-project.org/wiki/index.php/Setting_Up_Build_Environment
Currently, this is what we have in the docs on toolchain use. What I need is an assessment of where in particular it is lacking to satisfy this bug. http://www.yoctoproject.org/docs/1.5/ref-manual/ref-manual.html#var-TCMODE http://www.yoctoproject.org/docs/1.5/ref-manual/ref-manual.html#cross-development-toolchain-generation http://www.yoctoproject.org/docs/1.5/ref-manual/ref-manual.html#idp1628192 http://www.yoctoproject.org/docs/1.5/adt-manual/adt-manual.html#using-an-existing-toolchain-tarball Thanks, Scott
Can you show me a real world example, and not just plain documentation?
Yes - real-world examples are good and I can include one. Can you tell me though if the information that is currently there would allow a person to use an external toolchain? Knowing if that is true or not would help me better develop where to put an example.
See bug 4908 which has been blocking my full-time job since yesterday.
Setting target for 1.6.
Phew, I seem to have been frustrated here earlier. I sincerely apologize about that. I think the only issue that I see now is that the EXTERNAL_TOOLCHAIN variable is not documented in the "glossary". If that is added, that would satisfy me for now. Here is an example for the mentor graphics code sourcery toolchain: EXTERNAL_TOOLCHAIN = "/usr/local/arm-2009q1" It is basically setting the path to the toolchain root if I understand it correctly, but I may be wrong.
The tricky thing is the parts of this that matter (as in the parts that read EXTERNAL_TOOLCHAIN) are no longer in OE-Core. We could still document usage of meta-sourcery as an example of external toolchain usage, but it would need to be done in cooperation with the Mentor Graphics folks that maintain it and at this point in the release cycle it's 1.7 material.
That is fine, Paul.
Hi, Based on the comments, I am pushing this one to 1.7. Also changing to ACCEPTED so the filters don't catch the bug for NEEDINFO. Thanks, Scott
Paul, What can be done now with this bug? Is it appropriate to document meta-sourcery as an example of external toolchain usage as you suggested? Does Mentor need to be consulted/worked with? Thanks, Scott
Setting the milestone to M3. I still need some guidance on this so when Paul gets back I can hopefully get that. Scott
So, I'm marking this as ACCEPTED rather than NEEDINFO since it is now assigned to me rather than Scott.
I feel like I'm actually not very well set up to write about external toolchain setup. Chris, can I ask you to take care of this? Scott just needs some raw background material for the manual, if you could send him something that would be great.
Sorry for the delay on this. Scott, I think the readme over at https://github.com/MentorEmbedded/meta-sourcery should be current and covers the usage of the layer. I'll leave it to you as to whether to duplicate it or link to it. Essentially you add the layer to bblayers and set EXTERNAL_TOOLCHAIN = "/path/to/toolchain/install".
Hi, I have adjusted the documentation to address this situation. Please review the following areas: http://www.yoctoproject.org/docs/1.8/adt-manual/adt-manual.html#optionally-using-an-external-toolchain http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-TCMODE thanks, Scott
Thank you, Scott.
Looks good.
Hi, Looks like we have approvals for this fix. I am marking the issue RESOLVED and setting the documentation flag to "done." Thanks, Scott