%poky; ] > You can set up Toaster as a local instance or as a hosted service. Furthermore, you can use Toaster in Analysis Mode or Build Mode from both set ups.

This section describes how to use Toaster in Analysis Mode after setting Toaster up as a local instance or as a hosted service.

Follow these steps to set up a local instance of Toaster and then run in Analysis Mode: Prepare your Build System: Be sure your system has the Toaster requirements by following the steps in the "Establishing Toaster System Dependencies" section. Get Set Up to Use the Yocto Project: Get the requirements set up so that you can use the Yocto Project to build images. See the "What You Need and How You Get It" section in the Yocto Project Quick Start for information. Be Sure Ports are Free: Make sure that port 8000 and 8200 are free. In other words, make sure the ports do not have servers on them. Source your Build Environment Setup Script: From your Build Directory (e.g. poky/build), source the build environment setup script (i.e. &OE_INIT_FILE; or oe-init-build-env-memres). Start Toaster: From the Build Directory, start Toaster: $ source toaster start Start Your Build Using BitBake: Use the bitbake command to start your build. Here is an example that builds the core-image-minimal image: $ bitbake core-image-minimal For information on how to use Toaster, see the "Using the Toaster Interface" section.

A hosted service resides on a server and allows multiple users to take advantage of Toaster. In a production environment, you might want to have multiple local instances of Toaster, which run on various remote build machines, and have those local instances access and use a single hosted Toaster service. Starting Toaster with the toaster command (i.e. the script), causes three things to start: The BitBake server. The Toaster User Interface, which connects to the BitBake server on one side and to the SQL database on the other side. The web server, which reads the database and displays the web user interface. Rather than starting Toaster with the script, you can set up and start multiple instances of Toaster by manually starting as many or few of these three components across your environment. This is possible because it is not required that Toaster starts all three of its separate components in order to run. Minimally, a local instance of Toaster requires just one of the components. The concepts for setting up multiple local instances of Toaster that share a single hosted service revolve around maintaining a common SQL database and Web server that shows data from that common database as well as setting up separate local instances of BitBake servers and Toaster user interfaces for each of those separate BitBake build directories. The common SQL database and the Web server show data from all the various BitBake builds. Setting the SQL database outside of any Build Directory maintains a separation layer between the various local builds and the common database. The database is persistent because the logging database is set up external to the BitBake database server (e.g. MySQL). It is not even necessary to run the BitBake servers, the SQL server, and the Web server on the same machine. Each component can be run on its own machine. Follow these steps to set up and run a hosted service and run Toaster in Analysis Mode: Prepare your Build System: Be sure your system has the Toaster requirements by following the steps in the "Establishing Toaster System Dependencies" section. Get Set Up to Use the Yocto Project: Get the requirements set up so that you can use the Yocto Project to build images. See the "What You Need and How You Get It" section in the Yocto Project Quick Start for information. Be Sure Ports are Free: Make sure that port 8000 and 8200 are free. In other words, make sure the ports do not have servers on them. Set up the SQL Logging Server and the Web Server: You can use any SQL server out of the box (e.g. mysgl-server for an Ubuntu build system). If you are concerned about performance, you might want to hand-tune the server. You must set up proper username and password access on the shared server for everyone that will be using Toaster. You need administration rights for the mysql root account, which is not the same thing as root access on the machine. Clone a separate, local Git repository of the Toaster master branch to use for running the Web server. The Git repository for Toaster is part of the Yocto Project Source Directory. Consequently, you just need to set up a separate local clone of the Yocto Project Source Directory (e.g. poky): $ git clone git://git.yoctoproject.org/poky You do not perform builds on this tree. You need to create this local repository away from any build areas. In the separately cloned tree for the Web server, edit the bitbake/lib/toaster/toastermain/settings.py file so that the DATABASES value points to the previously created database server. Use the username and password established earlier. Run the database sync scripts to create the needed tables as follows: $ python bitbake/lib/toaster/manage.py syncdb $ python bitbake/lib/toaster/manage.py migrate orm You can start the Web server in the foreground or the background using these commands, respectively: $ python bitbake/lib/toaster/manage.py runserver $ nohup python bitbake/lib/toaster/manage.py runserver 2>toaster_web.log >toaster_web.log & Enable Build Logging to the Common SQL Server for Each Build Directory you are Using: For each build system that will be using Toaster and the shared SQL server, you need to edit the bitbake/lib/toaster/toastermain/settings.py file to alter the DATABASES value so that it points to the common SQL logging server. I don't see how to do this from the Wiki. I need more clarification. In the Build Directory, create the required conf/toaster.conf file as described in BitBake Extra Options. Briefly, for each Build Directory, you need to inherit the toaster class by setting the following in your local.conf configuration file: INHERIT += "toaster" INHERIT += "buildhistory" BUILDHISTORY_COMMIT = "1" Start the BitBake server using the following command: $ bitbake ‐‐postread conf/toaster.conf ‐‐server-only -t xmlrpc -B localhost:0 && export BBSERVER=localhost:-1 Start the logging user interface using the following command: $ nohup bitbake ‐‐observe-only -u toasterui >toaster_ui.log & No hard-coded ports are used as there is enough code to run autodiscovery for ports to prevent collisions. Source your Build Environment Setup Script: From your Build Directory on each of the build systems, (e.g. poky/build), source the build environment setup script (i.e. &OE_INIT_FILE; or oe-init-build-env-memres). Start Builds Using BitBake: Use the bitbake command to start a build on a build system. Here is an example that builds the core-image-minimal image: $ bitbake core-image-minimal When you are finished with a build in a given Build Directory, be sure to kill the BitBake server for that build area: $ bitbake -m For information on how to use Toaster, see the "Using the Toaster Interface" section.

This section describes how to use Toaster in Build Mode after setting Toaster up as a local instance or as a hosted service.

I need the information on how to do this.

Right now, the WIKI PAGE has some information on this but I don't understand it. I need more information.

The Toaster interface allows you to examine the following: Outcome of the build, errors and warnings thrown Packages included in an image Image directory structure Build configuration Recipes and packages built Full dependency chain for tasks, recipes and packages Tasks run by the build system Performance information such as time, CPU usage, and disk I/O per task For several useful videos that show how to effectively use the Toaster interface, see the Toaster Documentation on the Yocto Project website. We have agreed to get rid of the manual page on the website, contains the links to the GUI videos. We have agreed to host the videos on Vimeo and to embed the videos in this new Toaster manual.