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

installation guide #2

Open
Mu0n opened this issue Feb 8, 2021 · 0 comments
Open

installation guide #2

Mu0n opened this issue Feb 8, 2021 · 0 comments

Comments

@Mu0n
Copy link

Mu0n commented Feb 8, 2021

I just started getting cygwin set up on my Win10 machine, diligently following your instructions. Everything went well. I chose option 2 for the symbolic links (doing them inside the cygwin terminal rather than in my Windows path parameters). When I arrived at the x16 rom and emulator steps, it took me a while that I should git clone those repos as well. Downloading the binaries works well, but from a close-to-unix-noob status, I wanted to clone the repos so I can easily replace them as new versions arrive.

there doesn't seem to be a specific step for installing SDL2 on cygwin after the fact inside the terminal. I followed your other repo's readme (https://github.com/SlithyMatt/x16-assembly-tutorial) and I wish I would have just checked in SDL2 at that step.

The other missing step I found is that the cygwin environment is not finding ld65,exe, so I added it by going to /usr/bin and doing ln -s /cygdrive/c/users/whatever/workspace/cc65/bin/ld65.exe

Not doing so makes the rom make step complain about its absence. Just thought you'd add a line about these in the otherwise excellent readme files, which guided me well by the hand despite my 20 year old rust in unix navigation

edit - you already answered in the x16 community forums that it makes little sense to attempt a compilation of the emulator...inside the cygwin environment - just stick with the windows binary. makes sense! Although the ROM step was a very minor issue that would remain here if and only if they don't package the bleeding edge version every time in their win compiled binairies.

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

No branches or pull requests

1 participant