On 23/11/16 04:53, Reyna, David 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>.
And just in case you were also meaning "production setup" as we used
"hosted" often to described this in the past (it's confusing I know).
The production setup is a way to setup Toaster as a service for multiple
people to use on a proper build server (for example one that is hosted
in a data centre). For this setup we recommend proven/hardened
technologies to run Toaster with such as Apache webserver and MySQL
(e.g. rather than Toaster's internal webserver and sqlite).
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:*[email protected]
[mailto:[email protected]] *On Behalf Of *Rizwan Md
*Sent:* Tuesday, November 22, 2016 8:29 PM
*To:* [email protected]
*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.
--
_______________________________________________
toaster mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/toaster
