You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+18-7Lines changed: 18 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# aws4embeddedlinux-ci-examples
2
2
3
3
## Getting Started
4
-
This repository shows ways to use the [aws4embeddedlinux-ci](https://github.com/aws4embeddedlinux/aws4embeddedlinux-ci.git) library.
4
+
This repository shows ways to use the [aws4embeddedlinux-ci](https://github.com/aws4embeddedlinux/aws4embeddedlinux-ci.git) library.
5
5
6
6
In order to use these examples, you must setup [CDK](https://docs.aws.amazon.com/cdk/v2/guide/getting_started.html) including installing the CDK tool and bootstrapping the account you wish to deploy to. Additionally, you must have [Node](https://nodejs.org/en/) installed.
7
7
@@ -20,10 +20,10 @@ Note that while often CDK projects do not require separately invoking the build
20
20
To deploy _all_ the pipeline examples, you can use the CDK deploy command:
21
21
22
22
```bash
23
-
cdk deploy --all
23
+
cdk deploy --all --require-approval never
24
24
```
25
25
26
-
The pipelines can be found in the `Developer Tools > Code Pipeline > Pipelines` Console page. The newly created pipeline `ubuntu_22_04BuildImagePipeline` should start automatically. If not, it will need to be run before other pipelines will work correctly. Once it is complete, the DemoPipeline in the CodePipeline console page is ready to run.
26
+
The pipelines can be found in the `Developer Tools > Code Pipeline > Pipelines` Console page. The newly created pipeline `ubuntu_22_04BuildImagePipeline` should start automatically. If not, it will need to be run before other pipelines will work correctly. Once it is complete, the EmbeddedLinuxPipeline in the CodePipeline console page is ready to run.
27
27
28
28
### Removing Pipelines
29
29
The `cdk destroy` command can be used to remove individual pipelines and their related resources. This can also be done in the CloudFormation Console Page.
@@ -44,18 +44,29 @@ The recommended place to view this is from the `Developer Tools > Code Pipeline
44
44
#### Using Kas
45
45
The Kas example shows how to use a [Kas Config](https://github.com/aws4embeddedlinux/aws4embeddedlinux-ci/blob/main/source-repo/kas/kas.yml) to manage layers. This tool can help programatically manage layers and config with tighter Yocto integration than Git Submodules or the Repo tool.
46
46
47
-
See AWS CodeBuild pipeline: KasPipeline-DemoPipeline*
47
+
See AWS CodeBuild pipeline: KasPipeline-EmbeddedLinuxPipeline*
48
48
49
49
#### A slightly modified version building a qemu pipeline:
50
-
This example builds a Qemu based image using [meta-aws-demos](https://github.com/aws4embeddedlinux/meta-aws-demos). The Qemu image can be run in the CodeBuild environment. Using SLIRP networking, [OEQA testing](https://docs.yoctoproject.org/singleindex.html#performing-automated-runtime-testing) such as ptest can be run in the pipeline.
50
+
This example builds a Qemu based image using [meta-aws-demos](https://github.com/aws4embeddedlinux/meta-aws-demos). The Qemu image can be run in the CodeBuild environment. Using SLIRP networking, [OEQA testing](https://docs.yoctoproject.org/singleindex.html#performing-automated-runtime-testing) such as ptest can be run in the pipeline.
51
51
52
-
See AWS CodeBuild pipeline: QemuDemoPipeline-DemoPipeline*
52
+
See AWS CodeBuild pipeline: QemuEmbeddedLinuxPipeline-EmbeddedLinuxPipeline*
53
53
54
54
### A Poky Based EC2 AMI Pipeline
55
55
Yocto can be used to create an EC2 AMI. This example builds an AMI based on Poky and meta-aws and exports it to your AMI registry using the [VM Import/Export Service](https://docs.aws.amazon.com/vm-import/latest/userguide/what-is-vmimport.html).
56
56
57
57
The pipeline name starts with `PokyAmiPipeline-` in the CodePipeline page.
58
58
59
+
### A NXP / IMX Pipeline
60
+
This example will build an image for the [i.MX 6ULL EVK](https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/evaluation-kit-for-the-i-mx-6ull-and-6ulz-applications-processor:MCIMX6ULL-EVK) board.
61
+
62
+
Accepting the EULA is required. For this you need to uncomment the
63
+
```
64
+
# - EULA=y
65
+
```
66
+
line in the build.buildspec.yml file in the nxp-imx-layer-repo CodeCommit repo.
67
+
68
+
The pipeline name starts with `NxpImxPipeline-` in the CodePipeline page.
69
+
59
70
### Using pre-built, proprietary artifacts in a Pipeline
60
71
61
72
This example is based on this [work](https://elinux.org/R-Car/Boards/Yocto-Gen3/v5.9.0) to build an image for Renesas R-Car-H3 Starter Kit Premier (unofficial name - H3ULCB) board including the proprietary graphics and multimedia drivers from Renesas.
@@ -76,7 +87,7 @@ Create a folder named `proprietary` in the root of the source repo. Put those tw
76
87
77
88
Now a build should automatically start, succeed and you will get an image containing the proprietary graphics and multimedia drivers.
78
89
79
-
See AWS CodeBuild pipeline: RenesasPipeline-DemoPipeline*
90
+
See AWS CodeBuild pipeline: RenesasPipeline-EmbeddedLinuxPipeline*
0 commit comments