This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
notes:data:fall2023:projects:btt0 [2023/08/27 18:15] – [Prepare and build (for system/OS)] jwieland | notes:data:fall2023:projects:btt0 [2023/08/30 21:11] (current) – [Extract files, read instructions, install needed dependencies] jhimmel2 | ||
---|---|---|---|
Line 36: | Line 36: | ||
You'll likely be given a bunch of packages when running this command, look for the ones that resemble lib[package]-dev. Install it using the command format given above. You are (or will be) a developer in this class, you'll need these packages installed moving forward. When you test out command #3 from the Readme again, you'll know it worked if you don't get the error for that specific dependency. | You'll likely be given a bunch of packages when running this command, look for the ones that resemble lib[package]-dev. Install it using the command format given above. You are (or will be) a developer in this class, you'll need these packages installed moving forward. When you test out command #3 from the Readme again, you'll know it worked if you don't get the error for that specific dependency. | ||
+ | When searching for libraries, you may get the following error: | ||
+ | E: Unable to locate package | ||
+ | |||
+ | In this case first check your spelling and make sure it is correct. | ||
====Prepare and build (for system/ | ====Prepare and build (for system/ | ||
Replicate section per system/OS you are building for | Replicate section per system/OS you are building for | ||
Line 53: | Line 57: | ||
<code bash> | <code bash> | ||
- | / | + | / |
</ | </ | ||
Line 63: | Line 67: | ||
At the bottom of this file add the two commands that you used to add the file paths, and boom you can now use the command line tools from the emulator and Devtools wherever you are on your system. 8-) | At the bottom of this file add the two commands that you used to add the file paths, and boom you can now use the command line tools from the emulator and Devtools wherever you are on your system. 8-) | ||
+ | |||
+ | If you’re having trouble locating the files, you can check the install_manifest.txt file in the build directory to see where the files are stored. | ||
====Creating your hello.c, hello.xml, and make.sh file==== | ====Creating your hello.c, hello.xml, and make.sh file==== | ||
Line 70: | Line 76: | ||
* Once created, go to < | * Once created, go to < | ||
* Copy the contents of each file from GitHub into their respective files in your btt0 directory. | * Copy the contents of each file from GitHub into their respective files in your btt0 directory. | ||
- | * Make sure to go into each file and adjust the names of files as we have changed them compared to what is listed on GitHub. | + | * Make sure to go into the make.sh |
+ | |||
+ | Its important at this stage to make the make.sh an executable, to do this type chmod +x make.sh, this adds the executable file permission to the file. | ||
+ | |||
+ | <code bash> | ||
+ | pi@raspberry: | ||
+ | </ | ||
+ | |||
+ | Its finally time to compile your first vircon32 game, to do this do ./make.sh and if no errors occur it should print out build successful. | ||
+ | |||
+ | There should now be a .v32 file in the bin directory. | ||
+ | |||
+ | After that you will want to make a file similar to hello.c, |