From 431011e93252a515446c50211678e1bdcf3fd1f4 Mon Sep 17 00:00:00 2001 From: Yonas Kolb Date: Tue, 30 Jan 2018 12:20:12 +1100 Subject: [PATCH] improve scheme build documentation --- Docs/ProjectSpec.md | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/Docs/ProjectSpec.md b/Docs/ProjectSpec.md index 293d7a33..b5367278 100644 --- a/Docs/ProjectSpec.md +++ b/Docs/ProjectSpec.md @@ -411,12 +411,18 @@ Schemes allows for more control than the convenience [Target Scheme](#target-sch - [ ] ***archive***: The archive action ### Build -- [x] **targets**: **[String:String]** or **[String:[String]]** - A map of target names to build and which build types they should be enabled for. The build types can be `all`, `none`, or one or more of the following types: - - `run` - - `test` - - `profile` - - `analyze` - - `archive` +- [x] **targets**: **[String:String]** or **[String:[String]]** - A map of target names to build and which build types they should be enabled for. The build types can be `all`, `none`, or an array of the following types: + - `run` or `running` + - `test` or `testing` + - `profile` or `profiling` + - `analyze` or `analyzing` + - `archive` or `archiving` + +```yaml +targets: + myTarget: all + myTarget2: [test, run] +``` ### Common Build Action options The different actions share some properties: