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

FEATURE: Add windows support to CLI #183

Open
HoldUpFjord opened this issue Jan 13, 2025 · 10 comments
Open

FEATURE: Add windows support to CLI #183

HoldUpFjord opened this issue Jan 13, 2025 · 10 comments
Assignees
Labels
Command Line Having to do with commands or the command line itself enhancement New feature or request feature Desired feature or current feature enhancment

Comments

@HoldUpFjord
Copy link

In my mind we could either:
1.) add to the documentation to use Windows Subsystem for Linux (WSL) and the steps it takes to get that working
2.) Perform a native solution; use conditionals for Unix specific functions and logic.

@HoldUpFjord
Copy link
Author

Reference SO for option 2: https://stackoverflow.com/questions/51723857/how-to-make-a-windows-cli-from-a-mac

@SchoolyB SchoolyB added enhancement New feature or request feature Desired feature or current feature enhancment Command Line Having to do with commands or the command line itself labels Jan 13, 2025
@SchoolyB SchoolyB added this to the Pre_Rel_v0.6.0_dev milestone Jan 13, 2025
@SchoolyB
Copy link
Collaborator

I will take a look at this on my Windows machine tomorrow and add to the issue. Need to set up a dev environment @HoldUpFjord

@SchoolyB
Copy link
Collaborator

SchoolyB commented Jan 14, 2025

Got everything set up and ran the build.sh script....This should be a fun one😂 @HoldUpFjord want to take this one? Previously I had to manage certain variables differently based of Linux operating systems vs MacOS machines. I imagine the same would be done for Windows machine. You can find that documentation somewhere in here.

And an example of how I did it here

@HoldUpFjord
Copy link
Author

HoldUpFjord commented Jan 14, 2025

Yeah I'll take it! Already drew down the repo and started installing Odin etc.

I will definitely be asking questions throughout. Thanks for the links man!

@HoldUpFjord
Copy link
Author

I have been trying to get Clang installed for 2 days

@SchoolyB
Copy link
Collaborator

@HoldUpFjord Here are the directions to get Odin up and running on Windows :https://odin-lang.org/docs/install/#release-requirements--notes

They are a bit lacking so you can reference it with how I did it too

Steps I followed:

  1. Download the Odin source code here: https://github.com/odin-lang/Odin/releases/tag/dev-2025-01

  2. Download Visual Studio (Installed the specified package in the screenshot in the link i sent)

3.. Unzipped the files.

  1. Added the odin to my PATH

The instructions they gave to install Odin on Windows are very lacking tbh but hopefully my steps helpes

@HoldUpFjord
Copy link
Author

Ah I was trying to download Clang and LLVM without checking the odin docs directly.

@HoldUpFjord
Copy link
Author

then install odin

@HoldUpFjord
Copy link
Author

I've been on a whole journey going about it the way I did

@SchoolyB
Copy link
Collaborator

Let me know If I can help in any way

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Command Line Having to do with commands or the command line itself enhancement New feature or request feature Desired feature or current feature enhancment
Projects
None yet
Development

No branches or pull requests

2 participants