When I went to build VirtualT under Linux some moons ago I got some advice off this list about what older version of FLTK to use, but I haven't gotten back to that yet. I can go find it later if it's not immediately obvious in the archives (I haven't posted much here yet). I didn't explore the Windows path, but it would be interesting to hear about either way. It would be good for all of us trying a VirtualT rebuild to share notes here on the path to a successful rebuild as a start.
So I know about the REX chip and have bought a few but not installed them yet. What is REXCPM? Is that CP/M-80 as a ModelT ROM or something? Happy New Year to all! rcs On Wed, Jan 1, 2020 at 4:44 PM Brian White <bw.al...@gmail.com> wrote: > I failed to build it the other day using the latest version of fltk, so it > may need an older version. I didn't give it much effort so maybe it's not > much to fix, but it didn't build out of the box. > > On Wed, Jan 1, 2020, 3:54 PM John R. Hogerhuis <jho...@pobox.com> wrote: > >> I contributed a little code to VirtualT. But it's mainly Ken's work. I'm >> fine with your plan. Are we still operating on sourceforge? I assume >> eventually we should move to GitHub. >> >> As to toolchain, if you can build it you're good. May want to learn to >> use GDB if you don't already know it. >> >> >> -- John. >> >> >> On Mon, Dec 30, 2019, 7:14 AM Stephen Adolph <twospru...@gmail.com> >> wrote: >> >>> Hi all, >>> >>> I would like to modify virtualT to support REXCPM. >>> >>> I downloaded the source, and while I don't know C too well, I think >>> modifying the code may be within my reach. >>> >>> Questions >>> 1) when I'm happy with the changes, should I submit them to the broader >>> team for review/inclusion? >>> 2) what is the tool set needed? looks like GCC and FLTK? anything else? >>> >>> Any thoughts? >>> cheers >>> Steve >>> >>> -- *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic] (There is no fireside like your own fireside.)
