[Esbox-commits] r2302 - www/2nd_edition
eswartz at garage.maemo.org
eswartz at garage.maemo.org
Wed Oct 14 20:00:05 EEST 2009
Author: eswartz
Date: 2009-10-14 19:59:59 +0300 (Wed, 14 Oct 2009)
New Revision: 2302
Modified:
www/2nd_edition/shared_folders.html
www/2nd_edition/virtual_machines.html
Log:
Slight reorg
Modified: www/2nd_edition/shared_folders.html
===================================================================
--- www/2nd_edition/shared_folders.html 2009-10-14 16:34:04 UTC (rev 2301)
+++ www/2nd_edition/shared_folders.html 2009-10-14 16:59:59 UTC (rev 2302)
@@ -1,6 +1,8 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head>
+
+
<script><head>
<script></script>
@@ -23,6 +25,7 @@
+
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<title>Setting Up Shared Folders</title>
@@ -55,6 +58,7 @@
+
@@ -69,6 +73,8 @@
+
+
<meta name="description" content="">
@@ -85,6 +91,7 @@
+
@@ -100,6 +107,7 @@
+
<meta name="keywords" content="">
@@ -116,6 +124,7 @@
+
@@ -131,6 +140,7 @@
+
<link href="css/main.css" rel="stylesheet" type="text/css">
@@ -147,6 +157,7 @@
+
@@ -162,20 +173,8 @@
+
<link rel="shortcut icon" href="images/favicon.ico">
-
-
-
-
-
-
-
-
-
-
-
-
-
</head><body>
<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
@@ -211,6 +210,7 @@
+
<div id="banner">
<div class="wrap">
<div id="box">
@@ -233,6 +233,7 @@
+
<div class="wrap">
<div id="container">
@@ -249,7 +250,9 @@
</li>
</ul>
</li>
+ <li><a href="shared_folders.html#defaults">Default Shared Folders Configuration</a></li>
<li><a href="#sharing_xp">How to Make Shares in Windows XP</a></li>
+
<li><a href="#sharing_vista">How to Make Shares in Windows Vista</a><br>
</li>
<li><a href="#sharing_osx">How to Make Shares in MacOS X</a></li>
@@ -257,8 +260,7 @@
</li>
- <li><a href="#defaults">Default Shared Folders Configuration</a><br>
- </li></ul><ul><li><a href="#troubleshooting">Troubleshooting</a></li>
+ </ul><ul><li><a href="#troubleshooting">Troubleshooting</a></li>
</ul>
@@ -378,6 +380,83 @@
due to time constraints and limitations in CDT 5. In any case,
it's worthwhile to expose the SDK contents to the host so you can
browse Maemo headers in the editor.</p>
+
+<p id="defaults">
+</p>
+<h3 id="heading">Default Shared Folders Configuration<br>
+</h3>
+
+
+
+<p>ESbox publishes default shares when you configure a new build machine.</p>
+
+
+<p>For <span style="font-weight: bold;">Eclipse project sharing</span>, ESbox provides these shares:</p>
+
+
+
+<ul>
+<li>Local share? = Yes</li><li>Share path = c:\maemo\shared or /home/<user>/Public<br>
+</li><li>Mount path = /scratchbox/users/maemo/home/maemo/shared</li>
+</ul>
+
+
+
+<p>and</p>
+
+
+
+<ul>
+<li>Local share? = Yes</li><li>Share path = c:\maemo\shared or /home/<user>/Public<br>
+</li><li>Mount path = /home/maemo/shared<br>
+ </li>
+</ul>
+
+
+
+
+
+<p>Feel free to change the Share Path to whatever you have on your system. The Mount Paths, though, have
+been selected specially. They point into the user's home on
+the VM so that
+Scratchbox 1 and Scratchbox 2 can see the projects in the same
+Scratchbox-relative directory at build time. Additionally, they point
+to a location that will map the same no matter which target you're
+building. </p><br>
+<p>For <span style="font-weight: bold;">Maemo SDK sharing</span>, ESbox provides these shares:</p>
+
+
+
+
+<ul>
+<li>Local share? = No<br>
+</li><li>Share path = /scratchbox</li><li>Mount path = S: or /Volumes/scratchbox<br>
+</li>
+</ul>
+
+
+
+
+<p>and</p>
+
+
+
+
+<ul>
+<li>Local share? = No</li><li>Share path = /home/maemo</li><li>Mount path = T: or /Volumes/maemo<br>
+ </li>
+</ul>
+
+
+<p>Again, change the Mount Path according to your preferences. <br>
+</p>
+
+<p>These shares will allow access to enough of the SDK to allow full C/C++ indexing. The
+home directory is exposed mainly because Scratchbox 2 places SDKs under
+~/.maemo-sdk. But we suggest the whole home directory, which may
+be useful, if you want to move files back and forth between the host
+and VM.<br>
+</p><br>
<p id="sharing_xp">
</p>
@@ -533,106 +612,7 @@
</p>
<br>
<p><img style="width: 371px; height: 344px;" alt="GNOME Sharing Dialog" src="images/vm/gnome-share-dialog.png"></p>
-<p>Such shares are created as user shares, as described above.<br>
-</p>
-
-<p id="defaults">
-</p><h3 id="heading">Default Shared Folders Configuration<br>
-</h3>
-
-
-<p>ESbox publishes default shares when you configure a new build machine.</p>
-
-<p>For <span style="font-weight: bold;">Eclipse project sharing</span>, ESbox provides these shares:</p>
-
-
-<ul>
-<li>Local share? = Yes</li><li>Share path = c:\maemo\shared or /home/<user>/Public<br>
-</li><li>Mount path = /scratchbox/users/maemo/home/maemo/shared</li>
-</ul>
-
-
-<p>and</p>
-
-
-<ul>
-<li>Local share? = Yes</li><li>Share path = c:\maemo\shared or /home/<user>/Public<br>
-</li><li>Mount path = /home/maemo/shared<br>
- </li>
-</ul>
-
-
-
-
-<p>Feel free to change the Share Path to whatever you have on your system. The Mount Paths, though, have
-been selected specially. They point into the user's home on
-the VM so that
-Scratchbox 1 and Scratchbox 2 can see the projects in the same
-Scratchbox-relative directory at build time. Additionally, they point
-to a location that will map the same no matter which target you're
-building. </p>
-<p>Once your build machine
-and shared folder mappings are configured, ESbox will automatically
-select a project location inside a shared folder for you, when you
-create or import a project:</p>
-
-
-<p><img style="width: 467px; height: 528px;" alt="Default location for new project is inside shared folder" src="images/vm/esbox-new-project-vm.png"></p>
-
-<p>In fact, if the dialog presents an error about the project
-location not being visible, this means your shared folder mappings are
-insufficient, because no valid mapping satisfies the goal. This
-mapping depends on the mapping constraints for the union of the
-selected targets.<br>
-</p>
-
-<p><img style="width: 459px; height: 525px;" alt="Error when attempting to select a location not visible in a share" src="images/vm/esbox-new-project-vm-bad.png"><br>
-</p>
-
-
-<p>For <span style="font-weight: bold;">Maemo SDK sharing</span>, ESbox provides these shares:</p>
-
-
-
-<ul>
-<li>Local share? = No<br>
-</li><li>Share path = /scratchbox</li><li>Mount path = S: or /Volumes/scratchbox<br>
-</li>
-</ul>
-
-
-
-<p>and</p>
-
-
-
-<ul>
-<li>Local share? = No</li><li>Share path = /home/maemo</li><li>Mount path = T: or /Volumes/maemo<br>
- </li>
-</ul>
-
-<p>Again, change the Mount Path according to your preferences. <br>
-</p>
-<p>These shares will allow access to enough of the SDK to allow full C/C++ indexing. The
-home directory is exposed mainly because Scratchbox 2 places SDKs under
-~/.maemo-sdk. But we suggest the whole home directory, which may
-be useful, if you want to move files back and forth between the host
-and VM.<br>
-</p>
-<p>Once you have set up and configured such shares, ESbox will use
-these mappings to populate the C/C++ indexer settings when you create,
-import, or convert a project:</p>
-
-
-
-<p><img style="width: 879px; height: 597px;" alt="C/C++ Include Paths and Symbols populated with directories from shared folder mappings" src="images/vm/esbox-project-indexer-settings.png"><br>
-</p>
-
-
-<p>(If you need to change your shared folder setup, or change other things that invalidate these settings, you can use <em><strong>Project > Index > Reset Paths and Symbols</strong></em> or <em><strong>Project > Index > </strong></em><em>Add Missing Paths and Symbols</em> to regenerate them from the current mappings.)</p>
-
-
-<p id="troubleshooting">
+<p>Such shares are created as user shares, as described above.</p><p id="troubleshooting">
</p><h3 id="heading">Troubleshooting</h3>
@@ -676,7 +656,7 @@
<ul>
- <tt class="cmdbox">make: Warning: File `Makefile' has modification time 1.1e+07 s in the future<br><br>
+ <tt class="cmdbox">make: Warning: File `Makefile' has modification time 1.1e+07 s in the future<br>
rm -f *.o helloworld<br>make: warning: Clock skew detected. Your build may be incomplete. </tt>
<p>
then install the appropriate virtualization tools to ensure the time is synchronized.
@@ -749,6 +729,7 @@
+
<div id="footer">
<div class="part">
<table style="" cellspacing="5" width="100%">
@@ -782,4 +763,5 @@
+
</body></html>
\ No newline at end of file
Modified: www/2nd_edition/virtual_machines.html
===================================================================
--- www/2nd_edition/virtual_machines.html 2009-10-14 16:34:04 UTC (rev 2301)
+++ www/2nd_edition/virtual_machines.html 2009-10-14 16:59:59 UTC (rev 2302)
@@ -384,10 +384,12 @@
to map filesystem paths between the host and VM filesystem. <br>
</p>
<p>You specify here
-mappings for the <span style="font-weight: bold;">existing and configured </span>shared
+mappings for the existing and configured<span style="font-weight: bold;"> </span>shared
folders in the host and VM. You must manually configure
-file sharing yourself. <a href="shared_folders.html">See this document</a> for an overview and setup instructions.</p>
+file sharing yourself.</p>
+<p><a href="shared_folders.html">See this document</a> for an overview and setup instructions.</p>
+
<p><span style="font-weight: bold;">NOTE</span>: ESbox only supports Samba (Windows/CIFS) shared folders currently. <br>
</p>
@@ -459,10 +461,13 @@
<h3 id="heading">ESbox Virtual Machine Behavior</h3>
+<h4>Launching<br>
+</h4>
<p>ESbox will connect to a running virtual machine that responds to
the configured machine engine, target address, and SSH port in the Machine Access
settings. <br>
</p>
+
<p>If the specified engine is not running, then ESbox will prompt you to launch the
configured machine:</p>
<p><img src="images/vm/esbox-launch-vm.png" alt="">
@@ -492,7 +497,47 @@
<p><img src="images/vm/esbox-launching-vm-expanded.png" alt=""></p>
<p>Closing this dialog will not cancel any operation. It is only
informative, to help you look for common problems and solutions while
-configuring the machine.</p><p id="indexing">
+configuring the machine.</p>
+<h4>Shared folder mappings</h4>
+<p>Once you have configured mapping that expose the project to the VM, ESbox will automatically
+select a project location inside a shared folder for you, when you
+create or import a project:</p>
+
+
+
+
+<p><img style="width: 467px; height: 528px;" alt="Default location for new project is inside shared folder" src="images/vm/esbox-new-project-vm.png"></p>
+
+
+
+<p>In fact, if the dialog presents an error about the project
+location not being visible, this means your shared folder mappings are
+insufficient, because no valid mapping satisfies the goal. This
+mapping depends on the mapping constraints for the union of the
+selected targets.<br>
+</p>
+
+
+
+<img style="width: 459px; height: 525px;" alt="Error when attempting to select a location not visible in a share" src="images/vm/esbox-new-project-vm-bad.png"><br>
+<p><br>
+</p>
+<p>Once you have established mappings exposing the Maemo SDK to the host, ESbox will use
+these mappings to populate the C/C++ indexer settings when you create,
+import, or convert a project:</p>
+
+
+
+
+
+<p><img style="width: 879px; height: 597px;" alt="C/C++ Include Paths and Symbols populated with directories from shared folder mappings" src="images/vm/esbox-project-indexer-settings.png"><br>
+</p>
+
+
+
+
+<p>(If you need to change your shared folder setup, or change other things that invalidate these settings, you can use <em><strong>Project > Index > Reset Paths and Symbols</strong></em> or <em><strong>Project > Index > </strong></em><em>Add Missing Paths and Symbols</em> to regenerate them from the current mappings.)</p>
+<p id="indexing">
</p><p id="pcconn">
</p>
<h3 id="heading">PC-Connectivity Interaction</h3>
More information about the Esbox-commits
mailing list