Use #pragma code-name, data-name, bss-name, and you can decide what segment each goes in.NOOPr wrote:But it have a drawback: each bank will going to have data from segment "CODE" from every other bank
cc65 - 32KiB PRG banks and segments
Moderator: Moderators
- rainwarrior
- Posts: 8732
- Joined: Sun Jan 22, 2012 12:03 pm
- Location: Canada
- Contact:
Re: cc65 - 32KiB PRG banks and segments
Re: cc65 - 32KiB PRG banks and segments
You cannot do this for data imported from runtime.librainwarrior wrote:Use #pragma code-name, data-name, bss-name, and you can decide what segment each goes in.NOOPr wrote:But it have a drawback: each bank will going to have data from segment "CODE" from every other bank
- rainwarrior
- Posts: 8732
- Joined: Sun Jan 22, 2012 12:03 pm
- Location: Canada
- Contact:
Re: cc65 - 32KiB PRG banks and segments
That's true but it is the only thing that has to use those segments, so you can place the runtime where it is needed in your .cfg and for all other code send it to other segments.