On 16/06/15 10:50, Haridasan, Sujith wrote:
Forgot to attach toasterconf.json file in previous mail. Hence
attaching in the mail.
*From:*[email protected]
[mailto:[email protected]] *On Behalf Of *Haridasan, Sujith
*Sent:* 16 June 2015 15:16
*To:* [email protected]
*Subject:* [Toaster] Query regarding toaster setup
Hi,
Hi
I am new to toaster. I am trying to configure toaster with the layers
already cloned. I created dir
mkdir –p $HOME/MEL/mytest
cd $HOME/MEL/mytest
git clone git://git.yoctoproject.org/poky.git
git clone git://github.com/meta-qt5/meta-qt5.git
git clone git://github.com/openembedded/meta-oe.git
I would recommend keeping the toasterconf.json un-modified and using the
Import Layer feature in toaster for custom/customised layers. (Under
project configuration on the project page select "Import layer")
Toaster will checkout/clone layers for you before building with the
provided layer git details. If you're using modified versions of
existing layers, maybe import them as local-meta-ruby so as not to
confuse them with the upstream versions.
The toasterconf is really just used to bootstrap toaster, to provide
some project defaults and current release information to toaster.
I have modified $HOME/MEL/mytest/poky/meta-yocto/conf/toasterconf.json
file with minor assumptions. I have attached toasterconf.json file
along with the mail.
I tried executing toaster as follows:
sujith@kdekid:~/MEL/mytest/poky$ ./bitbake/bin/toaster
Syncing...
Creating tables ...
Creating table auth_permission
Creating table auth_group_permissions
Creating table auth_group
Creating table auth_user_groups
Creating table auth_user_user_permissions
Creating table auth_user
Creating table django_content_type
Creating table django_session
Creating table django_admin_log
Creating table south_migrationhistory
You just installed Django's auth system, which means you don't have
any superusers defined.
Would you like to create one now? (yes/no): yes
Username (leave blank to use 'sujith'):
Email address:
Password:
Password (again):
Superuser created successfully.
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
Synced:
> django.contrib.auth
> django.contrib.contenttypes
> django.contrib.messages
> django.contrib.sessions
> django.contrib.admin
> django.contrib.staticfiles
> django.contrib.humanize
> south
Not synced (use migrations):
- orm
- bldcontrol
(use ./manage.py migrate to migrate these)
Running migrations for orm:
- Migrating forwards to
0021_auto__chg_field_build_project__chg_field_project_bitbake_version__chg_.
> orm:0001_initial
> orm:0002_auto__add_field_build_timespent
> orm:0003_timespent
- Migration 'orm:0003_timespent' is marked for no-dry-run.
> orm:0004_auto__add_field_package_installed_name
>
orm:0005_auto__add_target_image_file__add_target_file__add_field_variablehistor
>
orm:0006_auto__add_field_target_image_size__add_field_target_license_manifest_p
> orm:0007_auto__add_helptext
>
orm:0008_auto__chg_field_variablehistory_operation__chg_field_recipe_descriptio
>
orm:0009_auto__add_projectvariable__add_projectlayer__add_projecttarget__add_pr
>
orm:0010_auto__add_field_project_branch__add_field_project_short_description__a
> orm:0011_auto__add_field_projectlayer_dirpath
> orm:0012_auto__add_field_projectlayer_optional__add_field_projecttarget_task
>
orm:0013_auto__add_release__add_layerversiondependency__add_unique_layerversion
>
orm:0014_auto__chg_field_package_summary__chg_field_layer_summary__chg_field_re
>
orm:0015_auto__add_field_layer_vcs_web_url__add_field_layer_vcs_web_tree_base_u
>
orm:0016_auto__add_field_release_helptext__chg_field_release_branch__add_index_
>
orm:0017_auto__del_toastersettingdefaultlayer__add_releaselayersourcepriority__
> orm:0018_auto__add_field_layer_version_project
> orm:0019_auto__add_buildartifact
>
orm:0020_auto__add_field_layer_version_local_path__add_field_recipe_pathflags__
>
orm:0021_auto__chg_field_build_project__chg_field_project_bitbake_version__chg_
- Loading initial data for orm.
Installed 0 object(s) from 0 fixture(s)
Running migrations for bldcontrol:
- Migrating forwards to 0008_brarchive.
> bldcontrol:0001_initial
>
bldcontrol:0002_auto__add_field_buildenvironment_sourcedir__add_field_buildenvironment
> bldcontrol:0003_auto__add_field_brlayer_dirpath
> bldcontrol:0004_loadinitialdata
- Migration 'bldcontrol:0004_loadinitialdata' is marked for no-dry-run.
> bldcontrol:0005_auto__add_brerror
> bldcontrol:0006_auto__add_brbitbake
>
bldcontrol:0007_auto__add_field_buildrequest_environment__chg_field_buildrequest_build
> bldcontrol:0008_brarchive
- Migration 'bldcontrol:0008_brarchive' is marked for no-dry-run.
- Loading initial data for bldcontrol.
Installed 0 object(s) from 0 fixture(s)
Toaster needs to know in which directory it can download build log
files and other artifacts.
Toaster suggests "/home/sujith/MEL/mytest/poky/toaster_build_artifacts/".
Press Enter to select
"/home/sujith/MEL/mytest/poky/toaster_build_artifacts/" or type the
full path to a different directory:
Verifying the Build Environment. If the local Build Environment is not
properly configured, you will be asked to configure it.
-- Validation: The checkout directory must be set.
Toaster needs to know in which directory it should check out the
layers that will be needed for your builds.
Toaster suggests "/home/sujith/MEL/mytest". If you select this
directory, a layer like "meta-intel" will end up in
"/home/sujith/MEL/mytest/meta-intel".
Press Enter to select "/home/sujith/MEL/mytest" or type the full path
to a different directory (must be a parent of current checkout
directory):
Verifying the Build Environment. If the local Build Environment is not
properly configured, you will be asked to configure it.
-- Validation: The build directory must be set.
Toaster needs to know where is your build directory.
The build directory is where all the artifacts created by your builds
will be stored. Type the full path to the directory (for example: "
/home/sujith/build")/home/sujith/MEL/mytest/build
Build configuration saved
Verifying the Build Environment. If the local Build Environment is not
properly configured, you will be asked to configure it.
Toaster can use a SINGLE predefined configuration file to set up
default project settings and layer information sources.
Toaster will list now the configuration files that it found. Select
the number to use the desired configuration file.
[1] - /home/sujith/MEL/mytest/poky/meta-yocto/conf/toasterconf.json
[0] - Exit without importing any file
Enter your option: 1
Importing file:
/home/sujith/MEL/mytest/poky/meta-yocto/conf/toasterconf.json
Layer configuration imported. Updating information from the layer
sources, please wait.
You can re-update any time later by running
bitbake/lib/toaster/manage.py lsupdates
Fetching branches
Fetching layer information
Fetching machine information
Fetching target information
Starting webserver...
Webserver address: http://0.0.0.0:8000/ <http://0.0.0.0:8000/>
Starting browser...
Toaster is now running. You can stop it with Ctrl-C
May I know how can I get meta-qt5 and meta-ruby layer accessible using
toasterconf.json file? Any pointers would be helpful for me to proceed
ahead.
Thanks,
Sujith H
--
_______________________________________________
toaster mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/toaster
