aee11f266b
The current scripts append the line -include $(TOP)/../RELEASE.local at the end of the configure/RELEASE file (if needed). While this works for most EPICS modules, there is one drawback: Definitions like SUPPORT=/myfavorite/build/server are not allways overwritten (better say undefined). Fix this and create a configure/RELEASE file which is the same for all EPICS modules. Simply overwrite configure/RELEASE with what we want. Thanks to the EPICS community for this suggestion
Travis-CI Scripts for EPICS Modules
Features
- Use different compilers (gcc, clang)
- Use different gcc versions
- Cross-compile for Windows 32bit and 64bit using MinGW and WINE
- Cross-compile for RTEMS 4.9 and 4.10
- Compile on MacOS
- Released versions of dependencies are cached (for faster builds)
How to Use these Scripts
-
Get an account on Travis-CI, connect it to your GitHub account and activate your support module's repository. For more details, please refer to the Travis-CI Tutorial. Make sure to use
travis-ci.organd not their.comsite. -
Add the ci-scripts respository as a Git Submodule (see README one level above).
-
Add settings files defining which dependencies in which versions you want to build against (see README one level above).
-
Create a Travis configuration by copying one of the examples into the root directory of your module.
$ cp .ci/travis/.travis.yml.example-full .travis.yml -
Edit the
.travis.ymlconfiguration to include the jobs you want Travis to run.Build jobs are declared in the list following the
jobs: include:declaration. Each element (starting with-in column 3) defines the settings for one build job.env:controls the setting of environment variables,dist:specifies the Linux distribution,os:the operating system. Also see the comments in the examples for more hints, and the Travis-CI documentation for more options and more details. -
Push your changes and check travis-ci.org for your build results.