[Toaster] Understanding Toaster

[Reyna, David]

Hi Rizwan,

> 1. Since the user is required to edit local.conf file if he wants to change the machine, why does Toaster again asks the user to configure the machine via GUI in "Local Yocto Project" type?
When you did this step, what you are doing is setting up a shell and environment to start and stop Toaster. This has nothing to do with projects, since you create and define projects from within Toaster directly.
> 2. If the user selects different machines in local.conf and Toaster GUI, which one is selected for building?
The local.conf in the Toaster’s “build” directory is never used. Toaster creates a unique build directory for each “project”, so that they are all kept clean from each other. When you set the project configuration in Toaster for a project, Toaster will update the respective conf information (via a “conf/toaster.conf” file actually) to reflect your selections.

> 3. I also just want to know, what are your future plans with Toaster. As in, is it going to stay for a long period? hopefully?
Yes, I am in it for the log period :-)

- David


From: Rizwan Md [mailto:mdrizwan827 at gmail.com]
Sent: Tuesday, November 29, 2016 9:04 PM
To: Reyna, David
Subject: RE: [Toaster] Understanding Toaster


Hi David,

Thank you so much for the reply, now I have better understanding on Toaster.
Sorry for bothering you again, but there is one more scenario which has kept me thinking.
I did the following:
1. Cloned the latest poky from Yocto repository.
2. I sourced the oe-init-build-env script.
3. I edited my local.conf file and changed the MACHINE variable from qemux86 to qemuarm.
4. I started Toaster in Port 8000.
5. In Toaster, I again selected machine as "qemumips"and started building core-image-minimal image.
I have following queries:
1. Since the user is required to edit local.conf file if he wants to change the machine, why does Toaster again asks the user to configure the machine via GUI in "Local Yocto Project" type?
2. If the user selects different machines in local.conf and Toaster GUI, which one is selected for building?
3. I also just want to know, what are your future plans with Toaster. As in, is it going to stay for a long period? hopefully?
Thanks,
Rizwan.
On Nov 23, 2016 10:23 AM, "Reyna, David" <david.reyna at windriver.com<mailto:david.reyna at windriver.com>> wrote:

Hi Rizwan,

Thank you for your questions!

1. What is the exact difference between Toaster with Local yocto project and Toaster with any other release such as krogoth or Morty.
The “local” option uses whatever version and source of Yocto Project that you had installed and started Toaster with. The advantage is speed since it local and control since you set up your clone.
The “release” options use the public release git repositories, and not the local content (beyond starting Toaster). The advantage is full access to a tested release, with all their layers and packages, so you do not need to worry about making sure your local installation is complete.
2. In the Local yocto project in Toaster, will the user be able to add published  OE layers to his project?
No, unless you add them yourself.
3. If by using krogoth or Morty branch for development, the user will be able to access all the layers/recipes published, why would he use Local development with Toaster?
See above. It comes down to control and speed. If you know what you want and can manage the installation, then go for it. If you are exploring, then use the official repos.
4. What is exact difference between setting up Toaster locally and as a hosted Toaster?
If you only want to access the Toaster server on the machine you are hosting it on, then go simple and start Toaster with the webport=<port>.

If you (and others!) would like to access the Toaster server across the network from any other host, then start Toaster with webport=<IP>:<port>.

5. Will you be providing Toaster GUI along with Eclipse IDE? Which I now see is not available.

Toaster is its own GUI leveraging HTTP and web browsers and is focused on building and analyzing working projects, so there is no need for integration or connection with Eclipse.

The Yocto Project support for Eclipse is more related around developing and debugging applications, something Toaster will not be doing.

- David



From: toaster-bounces at yoctoproject.org<mailto:toaster-bounces at yoctoproject.org> [mailto:toaster-bounces at yoctoproject.org<mailto:toaster-bounces at yoctoproject.org>] On Behalf Of Rizwan Md
Sent: Tuesday, November 22, 2016 8:29 PM
To: toaster at yoctoproject.org<mailto:toaster at yoctoproject.org>
Subject: [Toaster] Understanding Toaster

Hello,
I am new to Yocto project, I have been learning about it. I thought of using Toaster for the same. I find Toaster to be appealing. But, I have some doubts regarding toaster. I have listed them below.
1. What is the exact difference between Toaster with Local yocto project and Toaster with any other release such as krogoth or Morty.
2. In the Local yocto project in Toaster, will the user be able to add published  OE layers to his project?
3. If by using krogoth or Morty branch for development, the user will be able to access all the layers/recipes published, why would he use Local development with Toaster?
4. What is exact difference between setting up Toaster locally and as a hosted Toaster?
5. Will you be providing Toaster GUI along with Eclipse IDE? Which I now see is not available.
Please help me understand it better.
Thanks in advance.
Rizwan.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/toaster/attachments/20161130/8f625363/attachment-0001.html>