turtle-build 0.5.13

Ninja-compatible build system for high-level programming languages
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158

Feature: Dynamic dependency

  Scenario: Use a dyndep file
    Given a file named "build.ninja" with:
      """
      rule cp
        command = cp $in $out
      rule dd
        command = sh -c 'echo ok && echo ninja_dyndep_version = 1 >> $out && echo build foo: dyndep >> $out'

      build foo: cp bar || foo.dd
        dyndep = foo.dd
      build foo.dd: dd

      """
    And a file named "bar" with ""
    When I successfully run `turtle`
    Then the stdout should contain exactly "ok"

  Scenario: Use a dyndep file with an addtional input
    Given a file named "build.ninja" with:
      """
      rule touch
        command = touch $out
      rule cp
        command = sh -c 'echo ok && cp $in $out'
      rule dd
        command = sh -c 'echo ninja_dyndep_version = 1 >> $out && echo build foo: dyndep "|" bar >> $out'

      build foo: touch || foo.dd
        dyndep = foo.dd
      build foo.dd: dd
      build bar: cp baz

      """
    And a file named "baz" with ""
    When I successfully run `turtle`
    Then the stdout should contain exactly "ok"

  Scenario: Rebuild a dependent of a dynamic input updated in the same run
    Given a file named "build.ninja" with:
      """
      rule cp
        command = cp $in $out
      rule cat
        command = sh -c 'cat bar > $out'
      rule dd
        command = sh -c 'printf "ninja_dyndep_version = 1\nbuild foo: dyndep | bar\n" > $out'

      build foo: cat || foo.dd
        dyndep = foo.dd
      build foo.dd: dd
      build bar: cp baz

      """
    And a file named "baz" with "1"
    When I successfully run `turtle`
    And a file named "baz" with "2"
    And I successfully run `turtle`
    Then the file named "foo" should contain "2"

  Scenario: Use a dyndep file declared in a rule
    Given a file named "build.ninja" with:
      """
      rule touch
        command = touch $out
        dyndep = $out.dd
      rule cp
        command = sh -c 'echo ok && cp $in $out'
      rule dd
        command = sh -c 'echo ninja_dyndep_version = 1 >> $out && echo build foo: dyndep "|" bar >> $out'

      build foo: touch || foo.dd
      build foo.dd: dd
      build bar: cp baz

      """
    And a file named "baz" with ""
    When I successfully run `turtle foo`
    Then the stdout should contain exactly "ok"

  Scenario: Use a dyndep file naming an implicit output
    Given a file named "build.ninja" with:
      """
      rule touch
        command = touch $out
      rule cp
        command = sh -c 'echo ok && cp $in $out'
      rule dd
        command = sh -c 'echo ninja_dyndep_version = 1 >> $out && echo build baz: dyndep "|" bar >> $out'

      build foo | baz: touch || foo.dd
        dyndep = foo.dd
      build foo.dd: dd
      build bar: cp qux

      """
    And a file named "qux" with ""
    When I successfully run `turtle foo`
    Then the stdout should contain exactly "ok"

  Scenario: Use a dyndep file shared by builds
    Given a file named "build.ninja" with:
      """
      rule touch
        command = touch $out
      rule cp
        command = sh -c 'echo $out && cp $in $out'
      rule dd
        command = sh -c 'printf "ninja_dyndep_version = 1\nbuild foo: dyndep | baz\nbuild bar: dyndep | qux\n" > $out'

      build foo: touch || foo.dd
        dyndep = foo.dd
      build bar: touch foo || foo.dd
        dyndep = foo.dd
      build foo.dd: dd
      build baz: cp quux
      build qux: cp quux

      """
    And a file named "quux" with ""
    When I successfully run `turtle bar`
    Then the stdout should contain "baz"
    And the stdout should contain "qux"

  Scenario: Fail to use a dyndep file that is not an input
    Given a file named "build.ninja" with:
      """
      rule touch
        command = touch $out
      rule dd
        command = sh -c 'echo ninja_dyndep_version = 1 >> $out && echo build foo: dyndep >> $out'

      build foo: touch
        dyndep = foo.dd
      build foo.dd: dd

      """
    When I run `turtle foo`
    Then the exit status should not be 0
    And the output should contain "foo.dd"

  Scenario: Fail to use a dyndep file naming an unknown output
    Given a file named "build.ninja" with:
      """
      rule touch
        command = touch $out
      rule dd
        command = sh -c 'echo ninja_dyndep_version = 1 >> $out && echo build baz: dyndep "|" bar >> $out'

      build foo: touch || foo.dd
        dyndep = foo.dd
      build foo.dd: dd

      """
    When I run `turtle foo`
    Then the exit status should not be 0
    And the output should contain "baz"