Building VirtualT on Linux: Difference between revisions

From Bitchin100 DocGarden
Jump to navigationJump to search
No edit summary
 
(23 intermediate revisions by 5 users not shown)
Line 1: Line 1:
(Rough, please improve...)
== What is this "Linux" You Speak Of? ==


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?).
These instructions have been tested on


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
* Debian
* Ubuntu
* Slackware


http://sourceforge.net/cvs/?group_id=115749
Please add to the list if you have tested on another distribution.


Comes down to this:
== This Sounds Hard... Why All The Steps? ==
 
Because of the rich variety of Linux distros that grace our planet 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, Linux users simply have to build VirtualT themselves. Of course the benefit of building it yourself is that you always have the latest and greatest features, and of course bugs... but that's what makes life exciting, right?
 
A side benefit is that it increases the amount of people on the latest and greatest. That means more testers of new features. If you have a version that works well for you, keep that in mind before you
<code><pre>cvs update</pre></code>
to get latest and greatest.
 
== Download Latest VirtualT Source FOR THE FIRST TIME ==


Open a command prompt and type:
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
<code><pre>cvs -z3 -d:pserver:anonymous@virtualt.cvs.sourceforge.net:/cvsroot/virtualt co -P VirtualT
</pre></code>
 
== Download Packages FLTK Depends On ==
 
(a version of this command for RPM or source based distros would be nice)
 
Command to download FLTK dependencies on Debian:
 
sudo apt-get build-dep libfltk1.1
 
Command to download FLTK dependencies on Debian Lenny (stable):
 
sudo aptitude install libfltk1.1 libfltk1.1-dev libxext-dev build-essential
 
== Download, Build FLTK dependency ==
 
VirtualT depends on the FLTK library. FLTK is hosted at http://www.fltk.org/software.php . Download a version of fltk. These instructions were last tested with fltk-1.1.9 . Building with 1.3 versions doesn't seem to work.
 
To check out from subversion:
 
<code><pre>
svn co http://svn.easysw.com/public/fltk/fltk/branches/branch-1.1/ fltk-1.1
</pre></code>
 
Change directory into fltk-x.y.z
 
Note that if you check out from Subversion, you will need to have autoconf install and run it from within the fltk directory to generate a configure script before running the following command.
 
Configure and make fltk:


<code><pre>
./configure --enable-localjpeg --enable-localzlib --enable-localpng
make
</pre></code>
== Updating to Latest VirtualT ==
<code><pre>
cvs update
</pre></code>
== Building VirtualT ==
cd into VirtualT.
ls
If you see a folder named vt_client or vt_client_src, remove it
rmdir vt_client
or
rmdir vt_client_src
<code><pre>
export FLTKDIR=/where/is/fltk-x.y.z
export FLTKDIR=/where/is/fltk-x.y.z
make
</pre></code>


then make should work.
then make should work.
You should end up with a file titled 'virtualt' in your build directory. You can launch it by typing
<code><pre>
./virtualt
</pre></code>

Latest revision as of 10:15, 31 August 2011

What is this "Linux" You Speak Of?

These instructions have been tested on

  • Debian
  • Ubuntu
  • Slackware

Please add to the list if you have tested on another distribution.

This Sounds Hard... Why All The Steps?

Because of the rich variety of Linux distros that grace our planet 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, Linux users simply have to build VirtualT themselves. Of course the benefit of building it yourself is that you always have the latest and greatest features, and of course bugs... but that's what makes life exciting, right?

A side benefit is that it increases the amount of people on the latest and greatest. That means more testers of new features. If you have a version that works well for you, keep that in mind before you

cvs update

to get latest and greatest.

Download Latest VirtualT Source FOR THE FIRST TIME

Open a command prompt and type:

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

Download Packages FLTK Depends On

(a version of this command for RPM or source based distros would be nice)

Command to download FLTK dependencies on Debian:

sudo apt-get build-dep libfltk1.1

Command to download FLTK dependencies on Debian Lenny (stable):

sudo aptitude install libfltk1.1 libfltk1.1-dev libxext-dev build-essential

Download, Build FLTK dependency

VirtualT depends on the FLTK library. FLTK is hosted at http://www.fltk.org/software.php . Download a version of fltk. These instructions were last tested with fltk-1.1.9 . Building with 1.3 versions doesn't seem to work.

To check out from subversion:

svn co http://svn.easysw.com/public/fltk/fltk/branches/branch-1.1/ fltk-1.1

Change directory into fltk-x.y.z

Note that if you check out from Subversion, you will need to have autoconf install and run it from within the fltk directory to generate a configure script before running the following command.

Configure and make fltk:

./configure --enable-localjpeg --enable-localzlib --enable-localpng
make

Updating to Latest VirtualT

cvs update

Building VirtualT

cd into VirtualT.

ls

If you see a folder named vt_client or vt_client_src, remove it

rmdir vt_client

or

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

then make should work.

You should end up with a file titled 'virtualt' in your build directory. You can launch it by typing

./virtualt