Recent changes to VirtualMachine_v1

VirtualMachine_v1 modified by Ulf Lorenz

Ulf Lorenz — Fri, 01 Dec 2017 18:46:44 -0000

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Thu, 27 Apr 2017 19:16:46 -0000

--- v33
+++ v34
@@ -31,13 +31,13 @@

 Finally, we install the required software:

-* Enter "sudo nano /etc/apt/sources.list", and enter your password (sudo gives you administrator (root) privileges for the command, nano is an editor).
-* In the URLs with the form "ftp.de.\*", replace "de" by the country code where you are in (e.g., "ftp.dk.debian.org" for Danish). This should speed up the download.
-* Save the changes ("Ctrl-x", "y", "Return")
 * Run the installation script by entering "bash installAll.sh"
 * You might be asked (possibly repeatedly) to enter your password, just type it in then.
 * You might be asked to select some options. They should not usually matter, so just select the default (push Return or Space+Return if you have to select something)
 * Reboot the system. We just installed a new operating system kernel, this needs to be loaded or the steps below may fail.
+
+The minimal installation that we are going to do here should only require packages that are already downloaded and locally available in the VM, so you should not even need a network connection for this step.
+

 ## 2. Installing the Guest Add-ons ##

@@ -103,6 +103,12 @@
     * Rebuild the Guest Add-ons (the graphical integration add-on failed to build before because the graphical environment was not installed)
     * You can enter the graphical mode by typing "startx" on the command line

+* Note that if you want to install additional software, it may be a good idea to use local package mirrors instead of the main debain server (usually much faster):
+    * Enter "sudo nano /etc/apt/sources.list", and enter your password (sudo gives you administrator (root) privileges for the command, nano is an editor).
+    * In the URLs with the form "ftp.de.\*", replace "de" by the country code where you are in (e.g., "ftp.dk.debian.org" for Danish). This should speed up the download.
+    * Save the changes ("Ctrl-x", "y", "Return")
+
+
 * You can have a look at the scripts installAll.sh and compileAll.sh to get a feeling what all the magic was about. If you feel confident enough, you might want to redo the installation in a VM with a 64 bit system (use, e.g., a Debian netinstall image) or even install Linux on your actual machine, optimize it etc.

 ## Problems and Solutions ##

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Sun, 18 Dec 2016 20:46:24 -0000

--- v32
+++ v33
@@ -2,9 +2,9 @@

 The solution is the bare minimum to install / compile /run the programs in the VM on the command line, and share the input/output with your host system. There are some drawbacks ranging from possibly reduced speed to rather generous resource consumption (especially memory, which the VM may claim permanently while running). These issues are only rudimentarily addressed towards the end of this document.

-Finally, note that this document may be slightly biased towards WavePacket *developers*. For example, pulling the git repository may be overkill for normal users, although it is small enough that this should not really hurt.
+Note that no matter what strange system you have or what changes we did to the code, the installation described in this page should *always* work out of the box. If it does not, drop us an email, so that we can fix it or possibly update the documentation.

-Note that no matter what strange system you have or what changes we did to the code, the installation described in this page should *always* work out of the box. If it does not, drop us an email, so that we can fix it or possibly update the documentation.
+Finally, note that this document is slightly biased towards WavePacket *developers*. For example, pulling the git repository is overkill for normal users, although the download is small enough that this should not  hurt.

 [TOC]

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Sun, 18 Dec 2016 20:45:29 -0000

--- v31
+++ v32
@@ -32,7 +32,7 @@
 Finally, we install the required software:

 * Enter "sudo nano /etc/apt/sources.list", and enter your password (sudo gives you administrator (root) privileges for the command, nano is an editor).
-* In the two URLs with the form "ftp.de.\*", replace "de" by the country code where you are in (e.g., "ftp.dk.debian.org" for Danish). This should speed up the download.
+* In the URLs with the form "ftp.de.\*", replace "de" by the country code where you are in (e.g., "ftp.dk.debian.org" for Danish). This should speed up the download.
 * Save the changes ("Ctrl-x", "y", "Return")
 * Run the installation script by entering "bash installAll.sh"
 * You might be asked (possibly repeatedly) to enter your password, just type it in then.
@@ -41,12 +41,12 @@

 ## 2. Installing the Guest Add-ons ##

-The most important reason for installing these add-ons are shared folders, i.e., directories on your host machine that are also mounted as pseudo partitions inside the VM.
+The most important reason for installing these add-ons are shared folders, i.e., directories on your host machine that are also visible inside the VM.

 Installing the add-ons is reasonably simple:

-* In the terminal menu, click on "Devices / Install Guest Additions" or push (default config) <Right Ctrl>-D. This ddownloads a CD image if required and inserts it in the virtural CD drive.
-* make it available via "sudo mount /media/cdrom"
+* In the terminal menu, click on "Devices / Install Guest Additions". This downloads a CD image if required and inserts it in the virtural CD drive.
+* make it available via "mount /media/cdrom"
 * install the guest additions with "sudo bash /media/cdrom/VBoxLinuxAdditions.run". This should work out of the box.
 * Add yourselves to the new group to have access to shared folders: "sudo adduser wavepacket vboxsf".
 * Power down your system "sudo halt"
@@ -70,18 +70,18 @@

 Thanks to the prepared scripts, this should now be the simplest part.

-* Create some directory where you want to put all your sources: "mkdir <directory>". I would recommend /media/sf_<shared_folder_name>/src, so that you have access to it from both systems.
-* Change to this directory: "cd <directory>"
-* Run the automatic downloading and compilation script: "bash ~/compileAll.sh"  ("~" expands to your user's home directory)
+* Create a source directory in your home folder where all sources are downloaded to: "mkdir ~/src" ("~" expands to your user's home directory).
+* Change to this directory: "cd ~/src"
+* Run the automatic downloading and compilation script: "bash ~/compileAll.sh"  
 * Go get some coffee. It will take quite some time. You will be asked for your password here and there again.

 Now all WavePacket dependencies should have been compiled, and you can continue with compiling WavePacket itself.

-* Go into the wavepacket source directory. By default, this would require "cd wavepacket"
+* Go into the wavepacket source directory. By default, this would require "cd ~/src/wavepacket"
 * Get the version that you want to have. By default, you are on the "master" branch, which is the current somewhat stable development state.
     * Run "git tag" and "git branch -r". The former lists the tagged states (releases), the latter available branches
     * Select the release or branch <name> that you want to have and run "git checkout <name>". For branches, ignore the "origin/" part.
-* Set up everything according to the instructions in the README. Unless something goes wrong, you should only have to modify the LIB_SRCDIR parameter.
+* Set up everything according to the instructions in the README. You should not have to modify anything (versions>= 0.1.2) or only the LIB_SRCDIR parameter (versions <0.1.2)

 ## 4. Where to go from here ##

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Sun, 18 Dec 2016 20:41:02 -0000

--- v30
+++ v31
@@ -16,7 +16,7 @@
 * Download the rudimentary set up operating system (xxx.ova) from https://sourceforge.net/projects/cpp.wavepacket.p/files/Compilation%20images/
 * Start VirtualBox, select File / Import Appliance, and select the downloaded .ova file.

-You should now have a set up virtual machine "WavePacket" with a rudimentary Linux (for insiders: the distribution is Debian wheezy, because Debian ships with the Atlas library). Now it is time to start your VM the first time. Select it and push "Start", wait for it to boot, and then login.
+You should now have a set up virtual machine "WavePacket" with a rudimentary Linux (for insiders: the distribution is  Debian wheezy/jessie, because Debian ships with the Atlas library). Now it is time to start your VM the first time. Select it and push "Start", wait for it to boot, and then login.

 * User: wavepacket
 * Password: wavepacket1
@@ -32,11 +32,12 @@
 Finally, we install the required software:

 * Enter "sudo nano /etc/apt/sources.list", and enter your password (sudo gives you administrator (root) privileges for the command, nano is an editor).
-* In the first two URLs, replace "de" by the country code where you are in (e.g., "ftp.dk.debian.org" for Danish). This should speed up the download.
+* In the two URLs with the form "ftp.de.\*", replace "de" by the country code where you are in (e.g., "ftp.dk.debian.org" for Danish). This should speed up the download.
 * Save the changes ("Ctrl-x", "y", "Return")
 * Run the installation script by entering "bash installAll.sh"
 * You might be asked (possibly repeatedly) to enter your password, just type it in then.
 * You might be asked to select some options. They should not usually matter, so just select the default (push Return or Space+Return if you have to select something)
+* Reboot the system. We just installed a new operating system kernel, this needs to be loaded or the steps below may fail.

 ## 2. Installing the Guest Add-ons ##

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Thu, 15 Dec 2016 14:46:06 -0000

--- v29
+++ v30
@@ -1,9 +1,8 @@
-While developing WavePacket, it turned out that many people had problems compiling the library and the dependencies. As a simple solution, this document describes how to use a virtual machine (VM) to help with this task. A virtual machine is essentially a program that behaves like a very kind computer, and in which you can install another operating system (a guest), for example to ease compiling.
+While developing WavePacket, it turned out that many people had problems compiling the library and the dependencies. As a simple solution, this document describes how to use a virtual machine (VM) to help with this task. A virtual machine is essentially a program that behaves like a computer with very kind hardware, and in which you can install another operating system (a guest), for example to ease compiling.

-The solution is the bare minimum to install / compile /run the programs in the VM on the command line, and share the input/output with your host system. There are some further drawbacks ranging from possibly reduced speed to rather generous resource consumption (especially memory, which the VM may claim permanently while running). These issues are only rudimentarily addressed.
+The solution is the bare minimum to install / compile /run the programs in the VM on the command line, and share the input/output with your host system. There are some drawbacks ranging from possibly reduced speed to rather generous resource consumption (especially memory, which the VM may claim permanently while running). These issues are only rudimentarily addressed towards the end of this document.

-Finally, note that this document may be slightly biased towards WavePacket *developers*. For example, pulling the git repository may be overkill for normal users, although you do not have to use it.
-Of course, you can always install a stable release instead of the automatically downloaded one without major complications.
+Finally, note that this document may be slightly biased towards WavePacket *developers*. For example, pulling the git repository may be overkill for normal users, although it is small enough that this should not really hurt.

 Note that no matter what strange system you have or what changes we did to the code, the installation described in this page should *always* work out of the box. If it does not, drop us an email, so that we can fix it or possibly update the documentation.

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Sun, 11 Sep 2016 20:42:29 -0000

--- v28
+++ v29
@@ -77,6 +77,7 @@

 Now all WavePacket dependencies should have been compiled, and you can continue with compiling WavePacket itself.

+* Go into the wavepacket source directory. By default, this would require "cd wavepacket"
 * Get the version that you want to have. By default, you are on the "master" branch, which is the current somewhat stable development state.
     * Run "git tag" and "git branch -r". The former lists the tagged states (releases), the latter available branches
     * Select the release or branch <name> that you want to have and run "git checkout <name>". For branches, ignore the "origin/" part.

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Sun, 11 Sep 2016 20:41:10 -0000

--- v27
+++ v28
@@ -75,7 +75,12 @@
 * Run the automatic downloading and compilation script: "bash ~/compileAll.sh"  ("~" expands to your user's home directory)
 * Go get some coffee. It will take quite some time. You will be asked for your password here and there again.

-Now all WavePacket dependencies should have been compiled, and you can continue with compiling WavePacket itself according to the instructions in the README. This should not be too hard now (you should only have to modify the LIB_SRCDIR parameter).
+Now all WavePacket dependencies should have been compiled, and you can continue with compiling WavePacket itself.
+
+* Get the version that you want to have. By default, you are on the "master" branch, which is the current somewhat stable development state.
+    * Run "git tag" and "git branch -r". The former lists the tagged states (releases), the latter available branches
+    * Select the release or branch <name> that you want to have and run "git checkout <name>". For branches, ignore the "origin/" part.
+* Set up everything according to the instructions in the README. Unless something goes wrong, you should only have to modify the LIB_SRCDIR parameter.

 ## 4. Where to go from here ##

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Sun, 11 Sep 2016 20:36:17 -0000

--- v26
+++ v27
@@ -2,10 +2,12 @@

 The solution is the bare minimum to install / compile /run the programs in the VM on the command line, and share the input/output with your host system. There are some further drawbacks ranging from possibly reduced speed to rather generous resource consumption (especially memory, which the VM may claim permanently while running). These issues are only rudimentarily addressed.

-Finally, note that this document is slightly biased towards WavePacket *developers*. For example, we will always pull the latest software, which might not be essential for normal users (though it should not hurt).
+Finally, note that this document may be slightly biased towards WavePacket *developers*. For example, pulling the git repository may be overkill for normal users, although you do not have to use it.
 Of course, you can always install a stable release instead of the automatically downloaded one without major complications.

 Note that no matter what strange system you have or what changes we did to the code, the installation described in this page should *always* work out of the box. If it does not, drop us an email, so that we can fix it or possibly update the documentation.
+
+[TOC]

 ## 1. Basic installation ##

@@ -96,3 +98,8 @@
     * You can enter the graphical mode by typing "startx" on the command line

 * You can have a look at the scripts installAll.sh and compileAll.sh to get a feeling what all the magic was about. If you feel confident enough, you might want to redo the installation in a VM with a 64 bit system (use, e.g., a Debian netinstall image) or even install Linux on your actual machine, optimize it etc.
+
+## Problems and Solutions ##
+
+* *Image version 1 does not compile out of the box*
+    This is an unfortunate problem of a dependency (googletest and googlemock) no longer being available. Google has removed hosting of the downloads, which led to some restructuring of these two projects. The net effect is that the download that I originally used for the virtual machine image no longer exists, and the default paths of versions < 0.1.1b is not compatible with current versions of these libraries.

VirtualMachine modified by Ulf Lorenz

Ulf Lorenz — Sat, 03 Sep 2016 20:08:13 -0000

--- v25
+++ v26
@@ -35,7 +35,7 @@
 * Save the changes ("Ctrl-x", "y", "Return")
 * Run the installation script by entering "bash installAll.sh"
 * You might be asked (possibly repeatedly) to enter your password, just type it in then.
-* You might be asked to select some options. They should not usually matter, so just select the default (push Return)
+* You might be asked to select some options. They should not usually matter, so just select the default (push Return or Space+Return if you have to select something)

 ## 2. Installing the Guest Add-ons ##