I was able to compile virtualT1.7, as it stands on Sourceforge, using the instructions at club100, on the following system
Ubuntu 14.04 LTS FLTK 1.3.5 obtained from FLTK site GCC 4.8.4 I got a few warnings but no errors. seems to work in linux. Why I am doing this: extend VirtualT to support REXCPM. I'll keep my updates separate until such time as there is a new release planned. cheers Steve On Sat, Feb 1, 2020 at 8:38 AM Stephen Adolph <twospru...@gmail.com> wrote: > any reason why these might not work on Ubuntu 16.04 LTS? > > On Wed, Jan 8, 2020 at 12:12 AM Brian K. White <b.kenyo...@gmail.com> > wrote: > >> Ubuntu 19.10 >> >> gcc 9.2.1 >> >> fltk 1.4.0 >> actually "git clone https://github.com/fltk/fltk.git"; >> And the CMake directions in the middle of here: >> https://github.com/fltk/fltk/blob/master/README.CMake.txt >> " >> mkdir build >> cd build >> cmake .. >> make >> sudo make install >> " >> I didn't supply any of those options shown in that doc, just the steps >> right here. >> >> You may need to install some things before the fltk build works, and I >> can't say what those might be, because it depends what you just randomly >> happen to have installed and what I happened to have already had >> installed. The main useful thing to know is just that I didn't touch the >> fltk source at all, and I didn't even give any of the configure or build >> commands any special commandline flags or set any special environment >> variables. It was literally just these bare commands above. It means >> that if fltk doesn't build for you, you *probably* only need to install >> something indicated by the error message. like "apt install libjpeg-dev" >> etc, or yum install ... for centos etc. No special tricks or anything. >> >> And the virtualt 1.7 source zip file from here: >> https://sourceforge.net/projects/virtualt/files/Source/v1.7/ >> >> Except you would not get that zip unless you wanted to start from that >> same starting point and add your own changes manually. To get the >> changes already applied, you could just clone the repo: >> git clone g...@github.com:bkw777/VirtualT.git >> >> -- >> bkw >> >> >> On 1/7/20 5:54 AM, r cs wrote: >> > What specific versions of Linux, gcc, and FLTK were used? Any changes >> > to build FLTK? >> > >> > Thank you for sharing. >> > >> > Regards, >> > rcs >> > >> > On Mon, Jan 6, 2020 at 10:17 PM Brian K. White <b.kenyo...@gmail.com >> > <mailto:b.kenyo...@gmail.com>> wrote: >> > >> > I was just now able to build the latest FLTK and VirtualT on linux >> with >> > the following changes from the v1.7 sourceforge version: >> > >> > >> https://github.com/bkw777/VirtualT/commit/fe6df94725a5fcf1989964b22cb79848dc778a6d >> > >> > I don't know if every change is quite the most correct way to >> resolve >> > the compiler warnings or errors, and I don't know if one or two >> changes >> > don't also break compiling on Windows or Mac. >> > >> > But this commit link shows everything all together and it's not very >> > much, and at least for me, it builds without even any compiler >> warnings >> > let alone errors, and the resulting binary runs. >> > >> > I started with a clean copy of the src zip file from sourceforge, >> not a >> > fork from one of the other copies of VirtualT already on github. >> > >> > For fltk I didn't I didn't have to change anything. I just cloned >> the >> > current fltk repo from github (from the fltk web site) and followed >> the >> > CMake directions for building on linux. >> > >> > -- >> > bkw >> > >> > >> > >> > -- >> > /Níl aon tinteán mar do thinteán féin. /[Irish Gaelic] >> > (There is no fireside like your own fireside.) >> > >> > >> >> >> -- >> bkw >> >
