Apple-2-Tools/Apple2BuildPipeline
1
0
Fork 0
mirror of https://github.com/jeremysrand/Apple2BuildPipeline.git synced 2024-12-04 05:49:23 +00:00
Code Issues Projects Releases Wiki Activity

Update the readme

Browse Source
This commit is contained in:
Jeremy Rand 2014-09-29 23:34:56 -04:00
parent 686d0c1cb7
commit f4391caf5f
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -27,11 +27,11 @@ $ sudo make -f make/gcc.mak install
6. In the dialog, you will see an Apple \]\[ option below the OS X section. Select that and select "Apple \]\[ Project". Click "Next".
7. A dialog box with a few text fields will appear. In product name, put in the name of the Apple \]\[ executable you want to build. Organization Name and Organization Identifier can be anything you want it to be. Leave Build Tool set to "/usr/bin/make". Click "Next".
8. Xcode now prompts you where you want to save your project. The name of the project will be the product name you already gave. Pick a good directory for your project. Your Documents foler is a reasonable option. Click "Create".
9. You will now have your project ready for you. If you select Product->Build, it will build and execute the template code in Virtual \]\[. If everything works, you should see "HELLO, WORLD!" on the emulator. Press any key in the emulator to quit the executable.
9. Your project is now ready for you. If you select Product->Build, it will build and execute the template code in Virtual \]\[. If everything works, you should see "HELLO, WORLD!" in the emulator. Press any key in the emulator to quit the executable and go back to the BASIC prompt.
10. Review the Makefile and set any options you want. The file has lots of comments to help you understand the configuration options.
11. Change main.c and write more code in new C or assembly files until you have the program you always wanted to build...
This build infrastructure can be used in a non-Mac environment. You need cc65 and the instructions for downloading and building it should be approximately correct for most UNIX-like environments. From there, you can edit the Makefile and add new source files as described above. Be sure to set PGM to the name of your executable in the Makefile. When you build the project in a non-Mac environment, you should end up with a .dsk file but it will not try to execute that like it would on a Mac. In theory, other emulators on the Mac or on other host systems could be added to the build infrastructure and feel free to add support for your favourite.
This build infrastructure can be used in a non-Mac environment. You need cc65 and the instructions above for downloading and building it should be approximately correct for most UNIX-like environments. From there, you can edit the Makefile and add new source files as described above. Be sure to set PGM to the name of your executable in the Makefile. When you build the project in a non-Mac environment, you should end up with a .dsk file but it will not try to execute that like it would on a Mac. In theory, other emulators on the Mac or on other host systems could be added to the build infrastructure and feel free to add support for your favourite.
Acknowledgements:
=================