<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://bitchin100.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=96.231.70.89</id>
	<title>Bitchin100 DocGarden - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://bitchin100.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=96.231.70.89"/>
	<link rel="alternate" type="text/html" href="https://bitchin100.com/wiki/index.php?title=Special:Contributions/96.231.70.89"/>
	<updated>2026-04-12T21:47:25Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.3</generator>
	<entry>
		<id>https://bitchin100.com/wiki/index.php?title=Building_VirtualT_on_Linux&amp;diff=2020</id>
		<title>Building VirtualT on Linux</title>
		<link rel="alternate" type="text/html" href="https://bitchin100.com/wiki/index.php?title=Building_VirtualT_on_Linux&amp;diff=2020"/>
		<updated>2010-06-13T18:10:40Z</updated>

		<summary type="html">&lt;p&gt;96.231.70.89: /* Building VirtualT */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== What is this &amp;quot;Linux&amp;quot; You Speak Of? ==&lt;br /&gt;
&lt;br /&gt;
These instructions have been tested on&lt;br /&gt;
&lt;br /&gt;
* Debian&lt;br /&gt;
* Ubuntu&lt;br /&gt;
* Slackware&lt;br /&gt;
&lt;br /&gt;
Please add to the list if you have tested on another distribution.&lt;br /&gt;
&lt;br /&gt;
== This Sounds Hard... Why All The Steps? ==&lt;br /&gt;
&lt;br /&gt;
Because of the rich variety of Linux distros that grace our planet we need volunteer support to maintain good &amp;quot;packages&amp;quot; for each one. That&#039;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&#039;s what makes life exciting, right?).&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;pre&amp;gt;cvs update&amp;lt;/pre&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
to get latest and greatest.&lt;br /&gt;
&lt;br /&gt;
== Download Latest VirtualT Source FOR THE FIRST TIME ==&lt;br /&gt;
&lt;br /&gt;
Open a command prompt and type:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;pre&amp;gt;cvs -z3 -d:pserver:anonymous@virtualt.cvs.sourceforge.net:/cvsroot/virtualt co -P VirtualT&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Download Packages FLTK Depends On ==&lt;br /&gt;
&lt;br /&gt;
(a version of this command for RPM or source based distros would be nice)&lt;br /&gt;
&lt;br /&gt;
Command to download FLTK dependencies on Debian:&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get build-dep libfltk1.1&lt;br /&gt;
&lt;br /&gt;
Command to download FLTK dependencies on Debian Lenny (stable):&lt;br /&gt;
&lt;br /&gt;
 sudo aptitude install libfltk1.1 libfltk1.1-dev libxext-dev build-essential&lt;br /&gt;
&lt;br /&gt;
== Download, Build FLTK dependency ==&lt;br /&gt;
&lt;br /&gt;
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 . Decompress the package.&lt;br /&gt;
&lt;br /&gt;
Change directory into fltk-x.y.z&lt;br /&gt;
&lt;br /&gt;
Configure and make fltk:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
./configure --enable-localjpeg --enable-localzlib --enable-localpng&lt;br /&gt;
make&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Updating to Latest VirtualT ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
cvs update&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Building VirtualT ==&lt;br /&gt;
&lt;br /&gt;
cd into VirtualT.&lt;br /&gt;
&lt;br /&gt;
 ls&lt;br /&gt;
&lt;br /&gt;
If you see a folder named vt_client or vt_client_src, remove it&lt;br /&gt;
&lt;br /&gt;
 rmdir vt_client&lt;br /&gt;
or&lt;br /&gt;
 rmdir vt_client_src&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
export FLTKDIR=/where/is/fltk-x.y.z&lt;br /&gt;
make&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
then make should work.&lt;br /&gt;
&lt;br /&gt;
You should end up with a file titled &#039;virtualt&#039; in your build directory. You can launch it by typing&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
./virtualt&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/code&amp;gt;&lt;/div&gt;</summary>
		<author><name>96.231.70.89</name></author>
	</entry>
	<entry>
		<id>https://bitchin100.com/wiki/index.php?title=Building_VirtualT_on_Linux&amp;diff=2019</id>
		<title>Building VirtualT on Linux</title>
		<link rel="alternate" type="text/html" href="https://bitchin100.com/wiki/index.php?title=Building_VirtualT_on_Linux&amp;diff=2019"/>
		<updated>2010-06-13T18:09:24Z</updated>

		<summary type="html">&lt;p&gt;96.231.70.89: /* Download Packages FLTK Depends On */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== What is this &amp;quot;Linux&amp;quot; You Speak Of? ==&lt;br /&gt;
&lt;br /&gt;
These instructions have been tested on&lt;br /&gt;
&lt;br /&gt;
* Debian&lt;br /&gt;
* Ubuntu&lt;br /&gt;
* Slackware&lt;br /&gt;
&lt;br /&gt;
Please add to the list if you have tested on another distribution.&lt;br /&gt;
&lt;br /&gt;
== This Sounds Hard... Why All The Steps? ==&lt;br /&gt;
&lt;br /&gt;
Because of the rich variety of Linux distros that grace our planet we need volunteer support to maintain good &amp;quot;packages&amp;quot; for each one. That&#039;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&#039;s what makes life exciting, right?).&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;pre&amp;gt;cvs update&amp;lt;/pre&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
to get latest and greatest.&lt;br /&gt;
&lt;br /&gt;
== Download Latest VirtualT Source FOR THE FIRST TIME ==&lt;br /&gt;
&lt;br /&gt;
Open a command prompt and type:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;pre&amp;gt;cvs -z3 -d:pserver:anonymous@virtualt.cvs.sourceforge.net:/cvsroot/virtualt co -P VirtualT&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Download Packages FLTK Depends On ==&lt;br /&gt;
&lt;br /&gt;
(a version of this command for RPM or source based distros would be nice)&lt;br /&gt;
&lt;br /&gt;
Command to download FLTK dependencies on Debian:&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get build-dep libfltk1.1&lt;br /&gt;
&lt;br /&gt;
Command to download FLTK dependencies on Debian Lenny (stable):&lt;br /&gt;
&lt;br /&gt;
 sudo aptitude install libfltk1.1 libfltk1.1-dev libxext-dev build-essential&lt;br /&gt;
&lt;br /&gt;
== Download, Build FLTK dependency ==&lt;br /&gt;
&lt;br /&gt;
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 . Decompress the package.&lt;br /&gt;
&lt;br /&gt;
Change directory into fltk-x.y.z&lt;br /&gt;
&lt;br /&gt;
Configure and make fltk:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
./configure --enable-localjpeg --enable-localzlib --enable-localpng&lt;br /&gt;
make&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Updating to Latest VirtualT ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
cvs update&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Building VirtualT ==&lt;br /&gt;
&lt;br /&gt;
cd into VirtualT.&lt;br /&gt;
&lt;br /&gt;
 ls&lt;br /&gt;
&lt;br /&gt;
If you see a folder named vt_client, remove it&lt;br /&gt;
&lt;br /&gt;
 rmdir vt_client&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
export FLTKDIR=/where/is/fltk-x.y.z&lt;br /&gt;
make&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
then make should work.&lt;br /&gt;
&lt;br /&gt;
You should end up with a file titled &#039;virtualt&#039; in your build directory. You can launch it by typing&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
./virtualt&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/code&amp;gt;&lt;/div&gt;</summary>
		<author><name>96.231.70.89</name></author>
	</entry>
</feed>