Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workflow shits #50

Merged
merged 10 commits into from
Sep 17, 2024
Merged

Workflow shits #50

merged 10 commits into from
Sep 17, 2024

Conversation

moxie-coder
Copy link
Contributor

I updated Haxe to the latest ver (4.3.6, instead of 4.3.0 which I'm pretty sure should help with some bugs with the damn workflows)

@nebulazorua
Copy link
Collaborator

4.3.6 broke shit with Lime so we cant use that lol

@moxie-coder
Copy link
Contributor Author

moxie-coder commented Sep 17, 2024

4.3.6 broke shit with Lime so we cant use that lol

it has been working fine with the workflows on my end from what I've seen, I've been doing tests

@nebulazorua
Copy link
Collaborator

nebulazorua commented Sep 17, 2024

4.3.6 broke shit with Lime so we cant use that lol

it has been working fine with the workflows on my end from what I've seen, I've been doing tests

maybe it works when set to SPECIFICALLY 4.3.6? when set to latest lime was crying about super constructor call shit and i looked it up and its Lime <8.1.2 on Haxe 4.3.4+ (even tho we set it to 8.1.2 so it SHOULD run fine)

@moxie-coder
Copy link
Contributor Author

4.3.6 broke shit with Lime so we cant use that lol

it has been working fine with the workflows on my end from what I've seen, I've been doing tests

maybe it works when set to SPECIFICALLY 4.3.6? when set to latest lime was crying about super constructor call shit and i looked it up and its Lime <8.1.2 on Haxe 4.3.4+ (even tho we set it to 8.1.2 so it SHOULD run fine)

because Latest is Nightly builds (5.0.0 alpha)

@nebulazorua
Copy link
Collaborator

nebulazorua commented Sep 17, 2024

OH okay that'd explain it

I'll merge once the current workflows on main and this PR pass

(I'd add the unless="linux" back to the lua_allowed thing tho, cus Lua is broken on Linux atm w/ rico's luajit fork, was gonna look at what made linux work on superpower's fork later)

@moxie-coder
Copy link
Contributor Author

OH okay that'd explain it

I'll merge once the current workflows on main and this PR pass

(I'd add the unless="linux" back to the lua_allowed thing tho, cus Lua is broken on Linux atm w/ rico's luajit fork, was gonna look at what made linux work on superpower's fork later)

I've got a dual boot setup with Windows & Linux so I could take a look at it (I've got Ubuntu, and Arch)

@nebulazorua
Copy link
Collaborator

OH okay that'd explain it
I'll merge once the current workflows on main and this PR pass
(I'd add the unless="linux" back to the lua_allowed thing tho, cus Lua is broken on Linux atm w/ rico's luajit fork, was gonna look at what made linux work on superpower's fork later)

I've got a dual boot setup with Windows & Linux so I could take a look at it (I've got Ubuntu, and Arch)

was gonna ask Crow to help w/ it but if you wanna do it then go ahead, it'd help tbh

i don't have a linux machine beyond a steam deck atm and I dont wanna program on that thing without getting a USB hub n shit first lol

@moxie-coder
Copy link
Contributor Author

moxie-coder commented Sep 17, 2024

for some weird reason, Mac 11 seems to be on an indefinite queue which is strange

@nebulazorua
Copy link
Collaborator

buildwindows error is likely just due to the fact this is a PR and not the PR itself so i'll ignore that error lol
if buildmac passes i'll merge rn

@moxie-coder
Copy link
Contributor Author

buildwindows error is likely just due to the fact this is a PR and not the PR itself so i'll ignore that error lol if buildmac passes i'll merge rn

yeah the Windows one seems to just have bugged, and Mac 11 is just in hiatus for god knows what

@nebulazorua
Copy link
Collaborator

can prob remove 11 and then just go from there

@moxie-coder
Copy link
Contributor Author

can prob remove 11 and then just go from there

yeah true

@moxie-coder
Copy link
Contributor Author

alright, all of them are done (excluding 11)

@nebulazorua
Copy link
Collaborator

I'm just gonna remove 11 and then merge

@nebulazorua nebulazorua merged commit 72660e3 into riconuts:main Sep 17, 2024
0 of 5 checks passed
@moxie-coder moxie-coder deleted the moxie-coder-patch-1 branch September 18, 2024 02:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants