Building VirtualT on Linux

From Bitchin100 DocGarden
Revision as of 15:02, 26 January 2008 by 64.81.88.222 (talk) (New page: (Rough, please improve...) Because of the variety of Linux distros we need volunteer support to maintain good "packages" for each one. That's the best route... then no documentation is ne...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

(Rough, please improve...)

Because of the variety of Linux distros we need volunteer support to maintain good "packages" for each one. That's the best route... then no documentation is needed for install. Short of that, everyone just has to build VirtualT themselves. Of course the benefit of building it yourself is that you always have the latest and greatest features (and bugs... but that's what makes life so exciting, right?).

If someone else wants to beat me to writing good docs building on Ubuntu, please do. Here's a placeholder for the documentation, anyone can edit it:

http://bitchin100.com/wiki/index.php?title=Building_VirtualT_on_Ubuntu&action=edit

FWIW, checking out the latest and greatest code from cvs is a "basic skill" all Linux users should acquire. It's easy, cheap, and free. To get latest VirtualT code, there are instructions at

http://sourceforge.net/cvs/?group_id=115749

Comes down to this:

Open a command prompt and type:

cvs -z3 -d:pserver:anonymous@virtualt.cvs.sourceforge.net:/cvsroot/virtualt co -P VirtualT

If you cd into VirtualT, you can type 'make'. Most likely that won't work since you need to set FLTKDIR since VirtualT is dependent upon FLTK. That's probably the only dependency you won't have. So you need to google for the FLTK site, download its source package and build it on your system. Once it's built, you

export FLTKDIR=/where/is/fltk-x.y.z

then make should work.