feat+fix:cx_Freeze, Actions, etc.

[im-coder-lg]

Success! Raw logs: https://pipelines.actions.githubusercontent.com/m6uqHNCtCOVuhJiAJ3KWo8a4OKe5xHQUII9SafEtrG12bZTpyc/_apis/pipelines/1/runs/11/signedlogcontent/2?urlExpires=2021-12-04T10%3A12%3A49.1060900Z&urlSigningMethod=HMACV1&urlSignature=O6FJk3AtUZhbTwCUqVxO%2FMDtJNsX%2F6TT4MX4JYOiVxI%3D

We need to add Ubuntu and Mac soon.
Closes #5

[not-nef]

gg, still need a tester?

[im-coder-lg]

Yup! To check if the GUI loads+installer test for Macs, etc.

[im-coder-lg]

Release workflow works, it drafts a release, you can edit via the web client on mobile/desktop.
We fixed everything related to Windows builds. Now, I will test macOS and Linux builds.

[im-coder-lg]

The build error resides in UBUNTU!!!
That's the error with our actions, Mac and Linux are Unix-like, POSIX-compliant systems. PyInstaller doesn't work well with them, I think I might find a solution.

[im-coder-lg]

Something that might seem unrelated:

AppImage” file you download them as. Users of macOS will be very familiar with the concept of AppImages as macOS applications are packaged in a very similar way. ... To run an AppImage, simply right-click it, select Properties, go to the Permissions tab and make sure Allow executing file as program is ticked.

We can release one file for two OSes. What do you say?

[sumeshir26]

@im-coder-lg Yeah, AppImage for both might work, but is it required to edit the permissions?

[im-coder-lg]

Yeah, I guess it sends a chmod command since we know that GUIs run on top of CLIs, so toggling+saving that might mean that chmod ran. But the hardest question is this: How the heck can we transform the main file into an AppImage? Seems too complex, if you ask me.

[im-coder-lg]

And everyone says that PyInstaller creates Mac/Linux binaries. I found one on my Raspberry Pi but couldn't execute it. Maybe it's a bug in the OS. I am hoping to switch to Zorin soon, I want to do it myself but I can't find a competent USB.

[sumeshir26]

For now,the current implimentation is fine, appimages can be added after v1.0

[im-coder-lg]

Okay 👍 And PS: It's implementation, not implimentation. Just correcting.

[im-coder-lg]

Linking PRs.
https://github.com/im-coder-lg/TimerX/pull/2

[im-coder-lg]

I have added a set of commits in im-coder-lg#2, mainly a6d5b04, aa0db69, and 26b7003. But still, it fails.

[im-coder-lg]

Maybe we shouldn't use PyInstaller for Mac and Linux... What should we do?

[im-coder-lg]

Sorry, I pushed the change :( but I think it's fixed

[sumeshir26]

@im-coder-lg Run it!

[im-coder-lg]

Test initiating

[sumeshir26]

@im-coder-lg It seems to be running the build on the master branch. Can you run on actions-fix?

[im-coder-lg]

Give me a minute, Vivaldi kinda slowed down.

[im-coder-lg]

You did a mistake, maybe you added the Windows MSI on the Mac build.
I think it doesn't work like that, fixing that.

[im-coder-lg]

I'll fix this later, too confused with this. Maybe I got an idea coming up... What do you think of this:
Windows and macOS create separate release drafts.
You can download the draft release's binary installers, the MSIs and DMGs and re-upload it into your version of the release since there's actually no way we can combine releases like linking two OSes together.

[sumeshir26]

@im-coder-lg That might work...

[im-coder-lg]

Yup, that might work...

[im-coder-lg]

I will work on this after some time.

[sumeshir26]

@im-coder-lg You know what, to improve my actions skills, I will try to work on this myself.

[im-coder-lg]

Remember to add the workflow dispatch code too!

[sumeshir26]

@im-coder-lg Run the mac workfow

[im-coder-lg]

2 minutes, starting Chrome up, Vivaldi again slowed down(resource hogged)

[im-coder-lg]

There is no workflow_dispatch section! Did we create a glitch?

[sumeshir26]

@im-coder-lg Moving to #9

[im-coder-lg]

Got the mail, writing a comment there!