Code segmentation guide: Difference between revisions

Added links to the repository used by these guides.
m (Minor sentence fixes)
(Added links to the repository used by these guides.)
Line 11:
== Where to go from here? ==
 
These pages are aimed at providing users who are new to embedded systems programming to work around this limitation. It is expected that you have '''a strong understanding of C'''. TheyThe shouldcode hopefullyfor providethe youexample withROMs useful techniques and sample code to aidprovided in yourthese homebrewpages development,should andall itbe isavailable recommended that they be read[https://github.com/n64brew/N64-Codesplit-Tutorial in thethis providedrepository]. order:
 
Before you do anything, have a brief look over the code of the [https://github.com/n64brew/N64-Codesplit-Tutorial/tree/main/original original sample], as this is our "bad" starting ROM which we will improve upon. As soon as you've done that, look through the following pages (preferably in order):
 
* [[Splitting Assets from Code]]
Line 17 ⟶ 19:
* [[Data Compression]]
 
OnceAfter you have read through those three pages (and more importantly, '''understood them'''), it is also recommended you look into techniques to split your code. It is preferable that you write your game to support at least one of these methods '''before''' you start adding too much to it, as it might become more challenging to modify such an intricate part of your engine after the fact:
 
* [[Overlays]]