This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
notes:comporg:spring2025:projects:btt0 [2025/02/05 15:11] – [Obtain source of latest stable release of Vircon32 emulator] cburling | notes:comporg:spring2025:projects:btt0 [2025/02/06 04:11] (current) – [Hello World] tkastne1 | ||
---|---|---|---|
Line 9: | Line 9: | ||
====API==== | ====API==== | ||
+ | https:// | ||
=====Vircon32===== | =====Vircon32===== | ||
Line 40: | Line 41: | ||
After the rest of the Readme is followed everything should be installed properly. It is then imperative you add Vircon32 to your path.\\ | After the rest of the Readme is followed everything should be installed properly. It is then imperative you add Vircon32 to your path.\\ | ||
The installed location should be **/ | The installed location should be **/ | ||
- | Once added to your path you should be able to run the Vircon32 command anywhere to run the emulator. | + | Once added to your path you should be able to run the Vircon32 command anywhere to run the emulator.\\ |
+ | To add it to your path add the line: < | ||
=====Hello World===== | =====Hello World===== | ||
Bootstrap a fairly simple “Hello, World” example, modified sufficiently from any provided tutorial or demo code. | Bootstrap a fairly simple “Hello, World” example, modified sufficiently from any provided tutorial or demo code. | ||
Line 46: | Line 48: | ||
This is a link to the provided tutorials on the Vircon Github page: | This is a link to the provided tutorials on the Vircon Github page: | ||
https:// | https:// | ||
+ | |||
+ | Alternatively you can create a " | ||
+ | |||
+ | The documentation needed for printing can be found [[https:// | ||
+ | * **TIP** If you want to see what exactly a function from a header file does you can find the source files at / | ||
Indicate some potential changes/ | Indicate some potential changes/ | ||
Line 61: | Line 68: | ||
Part of your task is to author your own custom build script. Do not just use an existing script, and do not just lightly modify the provided scripts: craft your own, with descriptive comments, that suit your individual effort. | Part of your task is to author your own custom build script. Do not just use an existing script, and do not just lightly modify the provided scripts: craft your own, with descriptive comments, that suit your individual effort. | ||
+ | |||
+ | The script you make now does not have to be the only one you make; in fact you should improve the functionality of your build script when you find ways to, or run into inconveniences that can be mitigated | ||