-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME
86 lines (61 loc) · 3.1 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
History
===============================================================================
The oe-layersetup repository was created by Texas Instruments back in 2012
as both a tool for configuring OpenEmbedded builds and the place to house
the configuration files for rebuilding all of the releases of our software.
It pre-dates most of the other tools by several years and has been in active
use by TI's customers since its creation both directly and indirectly as
we use these configs to drive our build processes for our TISDK packages
on ti.com.
The oe-layersetup script has some useful features that include:
- Specifying the git repositories, branch, and commit on the branch you
want to configure the build for.
- The layers in the repository that you want to include in the build.
- A set of templates to use in the creation of the bblayers.conf and
the local.conf.
- A message of the day feature that can print a block of text to the
screen when running the tool against a config file.
- Custom local.conf settings that you need to include for the build you
are setting up.
With the creation and rise in popularity of some of the newer tools, including
the upcoming bitbake-setup tool, it is time to broaden our support for our
build configuration into some of these other newer tools.
To that end, we have migrated all of our configurations into an XML format
that serves to capture all of the bits of information that the different tools
need. Additionally, we have created a Makefile and XSLT files that can
generate the various configuration files for oe-layersetup, kas, and
bitbake-setup.
Adding New Configurations
===============================================================================
There are only two tool requirements for adding a new config:
- make
- xsltproc
Both tools should be readily available on all distributions, but you might need
to install the packages.
There are two methods for adding a new configuration: Adding XML directly, or
converting an oe-layersetup config.
Adding XML directly
-------------------
If you want to add a new configuration, you need to create the appropriate XML
file in src/configs, run make in src, and then commit all of the new files.
- cd src
- Edit configs/.../config.xml
- make
- git status
Converting oe-layersetup config
-------------------------------
If the flow you are working with already is using a modified oe-layersetup
config, or generates a locked down oe-layersetup config as an artifact, then
you can run the convert.pl script to translate that file into the XML config.
./src/bin/convert.pl --input <file> --config-name <name>
The <file> is simply the file you want to import, and the <name> is the name
of the config to import to. The name should also include any subdirectories
under configs where the file should go. For example:
./src/bin/convert.pl \
--input saved-config.txt \
--config-name coresdk/coresdk-10.01.08-config
This will create the XML file: src/configs/coresdk/coresdk-10.01.08-config.xml
From there you run the same steps as if you had added the XML config yourself:
- cd src
- make
- git status