Multispec lan file description how to#

rpmbuild -define '_topdir `pwd`' -ba SPECS/cbsample.rpmspec yum install rpm-build make gcc glibc -y

During the build phase, the code is compiled, and then the RPM package is created based on the RPM specification.Īs defined in the artifact section, the RPM file will be uploaded as a build artifact.

During the pre_build phase, the required directories are created and the required files, including the RPM build specification file, are copied to the appropriate location.

As part of the install phase, the required packages is installed using yum.

This build specification includes multiple phases: As described in the documentation, this version has different syntax for environment variables. The following build specification file ( buildspec-rpm.yml) uses build specification version 0.2. It will create the DEB package based on the control specification file (ntrol) configured in this build specification. Similarly, I have created a build specification file for DEB. It will use make to compile this code and the RPM specification file (cbsample.rpmspec) configured in the build specification to create the RPM package. I have created a build specification file for RPM.

I need to put this sample application in RPM and DEB packages so end users can easily deploy them. I’ll use a Makefile to compile these files. I have created a C program (cbsamplelib.c) that will be used to create a shared library and another utility program (cbsampleutil.c) to use that library. The AWS CLI must be installed and configured. You’ll find the source code for this post in our GitHub repo.

Multispec lan file description how to#

In this post, I’ll show you how to use different build specification files in the same repository to create different builds. In June 2017, AWS CodeBuild announced you can now specify an alternate build specification file name or location in an AWS CodeBuild project.