Commander X16

There was a flurry of pull requests being accepted, and then nothing. The current state of the code in GitHub uses $00-$01 for ram/rom banking control. I'm really hoping that someone pushes a button soon and makes the official R39 snapshot, because I'm still writing any code I intend to share/post for R38 and not updating cc65/ca65 until R39 is official.

 

5 hours ago, ZeroByte said:

There was a flurry of pull requests being accepted, and then nothing. The current state of the code in GitHub uses $00-$01 for ram/rom banking control. I'm really hoping that someone pushes a button soon and makes the official R39 snapshot, because I'm still writing any code I intend to share/post for R38 and not updating cc65/ca65 until R39 is official.



 

yes, want also to check if the rest of the memory is intact. Especially the amount of zero pages that are available to the user is of interest to me ...

23 hours ago, Ender said:

A while ago, like early April, Michael was active again and had seemed to plan to have R39 out soon at that time (I think he said something like he planned to have it out that weekend).  However, it looks like there may have been some sort of hang-up, since there doesn't seem to have been any activity since then.

Yeah, if the main emulator developer is busy, maybe they can call on the main Kernel developer to pitch in ...

... oh, wait ... no, never mind.

Wait, what's that other strategy? Ah, yes, patience. Unlike my fitness, I am going to have to see to it that my patience actually gets some exercise.

I know this isn't helping, but... every time this thread gets bumped, I keep hoping it's r39.

Just a reminder of the group rules for everyone. Please don’t ask for updates. Updates come when they are ready on a proactive not reactive basis. We get a number of emails, messages, and posts asking for various updates and it puts unfair pressure on the team. We are 5 people with a wonderful community of over 20,000 people. The machine has not been launched yet. Updates will be posted here when ready, not because we are asked to give interim ones. Thank you for understanding.

18 hours ago, StephenHorn said:

I know this isn't helping, but... every time this thread gets bumped, I keep hoping it's r39.

r39 is on GitHub, but it's not compiled there for Windows. If you walk back in the thread, you'll find I've posted a Windows binary, and compiling for Mac or Linux should be straightforward. I actually compiled the Windows binary on a Linux computer....

5 hours ago, TomXP411 said:

I actually compiled the Windows binary on a Linux computer

Do you have a guide to compiling the windows binary on linux? 

27 minutes ago, JimmyDansbo said:

Do you have a guide to compiling the windows binary on linux? 

No, I just looked at the Makefile for switch settings. It's been a few months, so I don't remember the exact process.... 

 

6 hours ago, TomXP411 said:

r39 is on GitHub, but it's not compiled there for Windows. If you walk back in the thread, you'll find I've posted a Windows binary, and compiling for Mac or Linux should be straightforward. I actually compiled the Windows binary on a Linux computer....

Oh, believe me, I'm well aware of the github repo, I've been one of the more active contributors. ? But there is no release tag for r39, because r39 is not released yet. It is nice, however, that the current head revisions of the emulator and ROM work together at the moment, and that they currently preview the next revision of the hardware that will be in r39.

But if I were to, say, upload a new program for r39 right now, then relatively few people would be able to run it, and in particular it would not work under the "Try It Now" feature.

25 minutes ago, JimmyDansbo said:

Do you have a guide to compiling the windows binary on linux? 

I don't compile the Windows binary on Linux, personally. I actually have my own VS2019 solution setup, with some additional source files to handle the platform compatibility differences between the cross-compiling environment of the official build and a native Windows environment. It sounds like one of the folks on the unofficial Discord server has recently rolled their own CMake script as well for compiling on Windows.

31 minutes ago, JimmyDansbo said:

Do you have a guide to compiling the windows binary on linux? 

I cross-compiled the emulator a few days ago. Here are the important make variables that need to be set on the command line:

• 
  WIN_SDL2 must be a path to a directory containing bin and lib subdirectories. The bin subdirectory must contain the sdl2-config executable, while the lib subdirectory must contain the MinGW 32-bit SDL2 libraries. These files can be obtained here by downloading SDL2-devel-2.0.14-mingw.tar.gz.
  


• 
  MINGW32 must be a path to a directory containing a lib subdirectory, which contains the MinGW 32-bit standard libraries.
  


• 
  CROSS_COMPILE_WINDOWS must be equal to 1.
  

For example, on my system, the command I use is:

Quote

make WIN_SDL2=/opt/local/i686-w64-mingw32/ MINGW32=/usr/i686-w64-mingw32/ CROSS_COMPILE_WINDOWS=1