-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Any chance of Linux support? #43
Comments
Yeah, tests and build use backslashes all over the place, but the bulk of the main code should be close to compatible with Linux/MacOS (using os.path functions). As I don't have either OS, I haven't tested them for real. Also note that most of the code has been made specifically for the built releases, which means that I have little to no idea how well it works as it's organized in the repo. To answer the main question, yes, I would like Linux support at some point. While you're at it, may I see the crash for main.py on Linux? |
Sure! Here: https://pastebin.com/c394VmL0 |
Ah yes, forward slashes and backslashes in the same path lol |
Going down the line and fixing the errors it complains about eventually leaves me off here after running main.py: https://pastebin.com/Xmvwdez7 (ps by fix i mean using a hacky solution and just replacing the It starts, but doesn't want to do much else
|
|
yo thanks :) |
if its too much of a hassle, dont worry about it, i can live without telling the whole world that im a friendly murderer on 2Fort |
Nice! |
|
Seeing as its all python it should be relatively easy to port -- trying to run build.py or main.py just crashes on me -- perhaps because of using \ for paths instead of / ?
Output of tests.py is here
The text was updated successfully, but these errors were encountered: