tag:help.appveyor.com,2012-11-13:/discussions/problems/13941-build-for-android-and-windows-in-the-same-yaml-fileAppVeyor: Discussion 2018-08-25T02:28:16Ztag:help.appveyor.com,2012-11-13:Comment/451924622018-04-30T16:09:40Z2018-04-30T16:09:53ZBuild for Android and Windows in the same YAML file<div><p>Have you read <a href="https://www.appveyor.com/docs/build-configuration/#build-matrix">this part</a> of the docs?<br>
If you already have, you might want to give this <a href="https://www.appveyor.com/blog/2018/04/25/specialized-build-matrix-configuration-in-appveyor/">blog post</a>, which explains more advanced matrix configuration, a look.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/451924622018-05-01T14:26:27Z2018-05-01T14:26:27ZBuild for Android and Windows in the same YAML file<div><p>Thank you for your quick answer McDonnell, but even with the provided links, I'm still struggling to do what I want.</p>
<p>The problem is I want to build for 2 different target platforms, but for the same configuration. From what I understood from the documentation, the "matrix" keyword won't be useful for me exactly for that reason. However, the "for" keyword one could be what I was looking for, but it doesn't seem to work as I expected, building only for the first element of the list (here is the appveyor file with these changes: <a href="https://github.com/Noxalus/BulletMLI-Editor/blob/4b254708d839a40b9d91f0813db1dd40d0886af0/appveyor.yml#L19">https://github.com/Noxalus/BulletMLI-Editor/blob/4b254708d839a40b9d...</a>).</p>
<p>Did I do something wrong?</p></div>noxalustag:help.appveyor.com,2012-11-13:Comment/451924622018-05-01T16:11:48Z2018-05-01T16:11:48ZBuild for Android and Windows in the same YAML file<div><p>When you are making your configuration file, first ignore the <code>for:</code> node and determine what jobs your build matrix will consist of. In the example you last linked to there is only one job. That is because, before the <code>for:</code> node, you have only the <code>version:</code> key (<em>not</em> a matrix dimension) and some environment variables (also <em>not</em> a matrix dimension unless subkeyed with <code>matrix:</code>).</p>
<p>After you have multiple jobs in the build matrix, the for node is used to identify a job or jobs (therefore first key should define which job/s) and then make specific overrides to it.</p>
<p>If you are still confused it might be helpful to define two distinct configuration yaml files and i could go over how to combine them into one.</p></div>Owen McDonnell