Added install target and using updated submodule

[4c0n]

Just adding some install targets again :) Could not create this PR before because it depended on the memorymap repository pr getting merged first.

Thanks in advance :1st_place_medal: :100:

[4c0n]

@bweir Could you spare a little time on this please? Thank you! :smiling_face_with_three_hearts:

[4c0n]

@bweir ping

[4c0n]

@bweir Hi Brett, could you check this out please?

[4c0n]

@bweir are you :ghost: ing me?

[bweir]

Sorry this is so late. I'm going to spend some time building out the CI so that it'd be possible to make releases again. The old Travis configs atrophied away, and in any case, Travis seems like its going downhill. Gotta replace all the old CI with Actions or otherwise.

[4c0n]

@bweir Awesome :smiley: thanks for the merge, I updated the repository url and opened a PR on flathub a while a go!

https://github.com/flathub/flathub/pull/1904

The build was passing not long ago, so it shouldn't be long before it's available through flathub :tada:

[bweir]

Awesome! Question, how does this connect to CI? So for example, when it's time to make a new release, how can we set it up to push a new release to flathub?

On Sat, Nov 7, 2020, 11:38 AM Youri Westerman notifications@github.com wrote:

@bweir https://github.com/bweir Awesome 😃 thanks for the merge, I updated the repository url and opened a PR on flathub a while a go!

flathub/flathub#1904 https://github.com/flathub/flathub/pull/1904

The build was passing not long ago, so it shouldn't be long before it's available through flathub 🎉

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/parallaxinc/PropellerIDE/pull/60#issuecomment-723485867, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACIRYGDIUT5UVS2XSXVTTITSOWO2XANCNFSM4QMGBURQ .

[4c0n]

@bweir the manifest file will end up in its own repository flathub/com.parallax.PropellerIDE and it contains the version number and the git commit hash. When you push to the new repository it should schedule a build and eventually push a new release, so you might want to somehow generate/modify the manifest from the CI here I suppose. Maybe there already is an action available to generate json configuration files and a way for it to access another repository, wouldn't be surprised 🙂

[barthalion]

You can take a look at https://github.com/flathub/io.openrct2.OpenRCT2/pull/5 – it's used for beta builds, but should be easy to use only "tags" events. (Using Flathub as CI for every commit is not recommended as we have limited resources.)