80
80
path : build
81
81
` ` `
82
82
83
+ For IronPython2 (RhinoV8):
84
+
85
+ ` ` ` yaml
86
+ on : [push]
87
+
88
+ jobs :
89
+ build_ipy_ghuser_components :
90
+ runs-on : windows-latest
91
+ steps :
92
+ - uses : actions/checkout@v2
93
+
94
+
95
+ - name : Install IronPython
96
+ run : |
97
+ choco install ironpython --version=2.7.8.1
98
+
99
+ - uses : compas-dev/compas-actions.ghpython_components@v5
100
+ with :
101
+ source : components
102
+ target : build
103
+ interpreter : ipy_v2
104
+
105
+ # The components have been built at this step.
106
+ # Now you can choose what to do with them, e.g.:
107
+ # upload them as artifacts:
108
+ - uses : actions/upload-artifact@v2
109
+ with :
110
+ name : ipy_ghuser-components
111
+ path : build
112
+ ` ` `
113
+
83
114
84
115
Commit, push and enjoy! 🍿
85
116
@@ -90,16 +121,19 @@ Make sure to have IronPython or Python3/pythonnet installed and the `GH_IO.dll`
90
121
Then start the script pointing it to a source and target folder, e.g. :
91
122
92
123
ipy componentize_ipy.py examples/ipy build
124
+ ipy componentize_ipy_v2.py examples/ipy_v2 build
93
125
python componentize_cpy.py examples/cpy build
94
126
95
127
Optionally, tag it with a version :
96
128
97
129
ipy componentize_ipy.py examples/ipy build --version 0.1.2
130
+ ipy componentize_ipy_v2.py examples/ipy_v2 build --version 0.1.2
98
131
python componentize_cpy.py examples/cpy build --version 0.1.2
99
132
100
133
An optional name prefix can help tell components apart from other similarly named ones :
101
134
102
135
ipy componentize_ipy.py examples/ipy build --prefix "(PACKAGE-NAME)"
136
+ ipy componentize_ipy.py examples/ipy_v2 build --prefix "(PACKAGE-NAME)"
103
137
python componentize_cpy.py examples/cpy build --prefix "(PACKAGE-NAME)"
104
138
105
139
# # How to create components
0 commit comments