Splitting Assets from Code: Difference between revisions
no edit summary
(Added category) |
No edit summary |
||
Line 103:
All we have to do is create a new C file, and in it we place a global buffer just like we did in the previous section. Except this time, we're not going to link this data to our codesegment, rather we'll tell the N64 to reserve this part of RAM for our buffer. We'll need to modify the makefile somewhat, as we'll need to compile our C file into an object file. Lets assume our buffer is in a C file called <code>texbuf.c</code>.
Your makefile should already have a dedicated <code>CODEFILES</code>
<syntaxhighlight lang="makefile">
Line 110:
</syntaxhighlight>
Now, you'll want to place the <code>DATAOBJECTS</code> in your makefile where it will compile the .o's, '''but not link them to the codesegment'''. Typically, this will be in the target section (such as <code>$(TARGETS):</code> or <code>default:</code>). Example:
<syntaxhighlight lang="makefile">
OBJECTS = $(CODESEGMENT) $(DATAFILES:.c=.o)
$(TARGETS): $(OBJECTS)
$(MAKEROM) spec $(MAKEROMFLAGS) -I$(NUSYSINC) -r $(TARGETS) -e $(APP)
makemask $(TARGETS)
</syntaxhighlight>
Since we're not linking the object file in our makefile, we'll need to do that manually afterwards:
<tabber>
Spec file =
In your spec file, all you need to do is add a new segment, but give it the <code>OBJECT</code> flag instead:
<syntaxhighlight lang="c">
beginseg
name "texbuf"
flags OBJECT
after "code" // You can use 'address' if you want to specify an exact RAM address to put the buffer at
include "texbuf.o"
endseg
</syntaxhighlight>
You can use <code>#include</code> in your spec file to include a header file with a list of address macros if you want to, and use that macro value in place of raw address numbers or the <code>after</code> keyword.
|-|
Linker script =
Line 126 ⟶ 146:
You can use this, for instance, to load your assets right after the code segment by loading them into the address at <code>_codeSegmentRomEnd</code>. You don't ''need'' to create an object file with your buffer as you can just write to any RAM address you seem fit (for instance, you can just define <code>u8* buffer = 0x80000400</code> globally, and then treat it as a buffer) but it sure helps as the compiler/linker can potentially catch buffer overflows and/or segment overlapping.
You can see an implementation of
== Finalizing the code ==
| |||