Commander X16

Since cc65 is pretty much stuck in limbo until R39 is made official, would it make sense to create a new system target -t cx16r39 and thus allow cc65 to progress without having to wait on the Kernal version to update officially?

I know that's really more like an issue to post to the project's github, but I know certain "movers and shakers" from over there do read the forums here, so I figured I'd post it here because it's an issue that affects anyone wanting to write in C for Commander X16 and use R39.

Probably makes more sense to create a fork for R39 support, and then do a pull request when it's released. Creating a different target for a temporary situation is not ideal.

On 11/15/2021 at 12:12 PM, SlithyMatt said:

Probably makes more sense to create a fork for R39 support, and then do a pull request when it's released. Creating a different target for a temporary situation is not ideal.

Yeah, I know what you mean. I just had the idea while working on my zsound library which has the same challenge: how to easily support multiple build targets for something that's essentially the same thing?

It's clearly not ideal, but at least whenever R39 becomes official, all that needs to be done is drop the R38 support and rename the cx16r39 target to cx16. It's a workaround, yes, but at least one that doesn't require having two installations of cc65. Maybe I should just look into doing that anyway... I just feel like I have bigger fish to fry than getting two builds to coexist on one system. I guess it's really not THAT hard to do - I think I managed to do it before back in the R26/R27 days when VERA was still likely to have drastic changes...