DuraCOR 312
Appendix C
MNL-0670-01 Rev A2
ECO-5931
Effective: 03 Jun 20
Page 51 of 59
mkdir <path>/<workspace_name>
tar -C <path>/<workspace_name> -Jxvf /opt/ARC/c-w_c312_resource.tar.xz
2. Create an overlay
This is done automatically as part of the next step.
3. Mount the overlay by sourcing the setup script (as root user)
Please note that the setup script sets many environment variables needed for nvidia build tasks. The
script will also create or mount the overlay as needed. The overlay can only be created by root so you will
need to be root at least the first time this is sourced. May of the development tasks also need to be run as
root so at Curtiss Wright we currently do the build tasks that require the environment as root. If
permissions allow editing projects files an some other tasks can be done as a non-root user. Currently
you will need to watch the output of the script carefully. Currently trying to mount a second (independent)
development overlay fails.
sudo bash # Note that both setup and some of the build steps need to be done as root.
cd <path>/<workspace_name>/Resource
source c-w_setup.sourceme
Choose Option 4A or 4B
4A. Set up a release image for Deploy
In this section we see how to restore a correctly stored release image named release_name.tar.xz. The
process of correctly capturing a release image is discussed in Step 6.
Restoring an image to the workspace: (as root)
tar -C $DEVDIR -Jxpvf release_name.tar.xz
Deploying a release image is actually a bit different from step 5 because we do not want to recreate or
resign any componants in the image set. So instead we do the following:
C312_ImageFlash reuse
4B. Develop a new image
First set up the
<path>/<workspace_name>Resource/bin has been added to the PATH in your environment by the
sourceme script. The scripts starting with 'C312_' can be used to do most of the development tasks