https://github.com/dhirsch1138/cc65_devcontainer_1

https://github.com/dhirsch1138/cc65_devcontainer_1

Last synced: 22 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/dhirsch1138/cc65_devcontainer_1
• Owner: dhirsch1138
• Created: 2024-11-18T02:56:05.000Z (3 months ago)
• Default Branch: main
• Last Pushed: 2024-11-28T15:53:59.000Z (3 months ago)
• Last Synced: 2024-11-28T16:46:28.861Z (3 months ago)
• Language: Makefile
• Size: 223 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Changelog: changes.txt

Awesome Lists containing this project

README

        
# Notice #

The 6502 development evironment has been moved into a Dev Container template @ https://github.com/dhirsch1138/cc65_template . This makes its intended use case (providing a starting point for your own projects) a lot easier.  I am leaving this repository, and its dev container, up in case folks were following my work here. I have made this dev container basically a shell, it'll try to overwrite itself and apply the new Dev Container Template upon itself.

**WARNING** BACK UP YOUR CODE BEFORE TRYING TO APPLY THIS UPDATE TO AN EXISTING CONTAINER VOLUME, APPLYING THE TEMPLATE MIGHT OVERWRITE ANY LOCAL CHANGES

Documentation about the 6502 development environment is now in https://github.com/dhirsch1138/cc65_template

# How do get this dev container on my machine?

As you have probably noticed, there isn't much in this repo anymore. I moved it all into a template to its use case (you using it to code your own projects, in your own repos) easier. The remaining container is just a shell.

I can offer two ways to use this:

* **RECOMMENDED**: Use the cc65_template I created @ https://github.com/dhirsch1138/cc65_template . Read the documentation there for setup, it is much easier than using this container.

* I shared this repo first, so I tried to leave a shell here that loads the new template. Once this dev container is opened, it'll pull down the template https://github.com/dhirsch1138/cc65_template automatically. You'll be prompted to rebuild the container, say yes. If you aren't prompted you can invoke a rebuild using the VS Code task (F1) "Dec Containers: Rebuild Container".

  * If you want everything in a container (including your source code) to keep stuff nice and tidy use the VS Code task (F1) "Dev Containers: Clone Repository in Container Volume". Provide this repo.

  * If you want the code easily accessible outside the container use the native VS Code task (F1) "Git: Clone". Provide this repo and open the folder after cloning. VS Code will notice it is a dev container and prompt you to connect.

  * Any other method. Just get this repo's contents in a folder and open it as a Dev Container in VS Code.

**Recommended**: Use your own repo to track your changes and push them somewhere outside of the container. I don't know how permenant docker containers are, I wouldn't trust a lot of work to one without having it backed up.