svn commit: r1037947 - /buildr/trunk/doc/installing.textile

[bo...@apache.org]

Author: boisvert
Date: Tue Nov 23 00:03:38 2010
New Revision: 1037947

URL: http://svn.apache.org/viewvc?rev=1037947&view=rev
Log:
Add note about using OSX + RVM.

Move "Using multiple versions of Buildr" to its own section

Modified:
    buildr/trunk/doc/installing.textile

Modified: buildr/trunk/doc/installing.textile
URL: http://svn.apache.org/viewvc/buildr/trunk/doc/installing.textile?rev=1037947&r1=1037946&r2=1037947&view=diff
==============================================================================
--- buildr/trunk/doc/installing.textile (original)
+++ buildr/trunk/doc/installing.textile Tue Nov 23 00:03:38 2010
@@ -71,6 +71,14 @@ You need to have the Apple Development T
 
 p(note). Java Update 3 for Snow Leopard removes header files necessary to compile the native Ruby-Java Bridge (RJB) gem, so installing rjb gem may fail on OS X.  The solution is to install Java for Mac OS X 10.6 Update 3 Developer Package from http://connect.apple.com before @gem install@.
 
+*Using RVM?* If you're not using the built-in ruby on OS X (e.g., if you're using RVM), you'll need to force-install the platform-independent RJB:
+
+{% highlight sh %}
+$ gem install rjb -v 1.3.3 --platform ruby
+{% endhighlight %}
+
+The darwin pre-built binary seems to only work with the built-in ruby.
+
 <br>
 
 *In details:* OS X 10.5 (Leopard) comes with a recent version of Ruby 1.8.6.  You do not need to install a different version of Ruby when running OS X 10.5.
@@ -102,16 +110,6 @@ $ sudo env JAVA_HOME=$JAVA_HOME gem upda
 $ sudo env JAVA_HOME=$JAVA_HOME gem install buildr -v 1.3.4
 {% endhighlight %}
 
-Rubygems makes it possible to install several versions of Buildr side-by-side on the same system.  If you want to run a specific version, you can do so by adding the version number between underscores ('_') as the first command-line parameter.  For example,
-
-{% highlight sh %}
-$ buildr _1.3.4_ clean   # runs Buildr v1.3.4
-
-$ buildr _1.4.4_ clean   # runs Buildr v1.4.4
-{% endhighlight %}
-
-p(note). There are two `buildr` executables installed by Rubygems.  One script serves to select the specified (or default) version of Buildr and is typically found under `/usr/bin/buildr` or `/var/lib/gems/1.8/bin/buildr`. The exact location will vary depending on your system.   The other script is the Buildr bootstrap per se and can be found under the specific version of Buildr, e.g, `/var/lib/gems/1.8/gems/buildr-1.4.0/bin/buildr`.   The first script should be on your `PATH`.   The second script should not be called directly and should not be on your `PATH`.
-
 h2(#windows).  Installing on Windows
 
 *The easy way:*  The easiest way to install Ruby is using the "one-click installer":http://rubyinstaller.rubyforge.org/.  Be sure to install Ruby 1.8.6; support for Ruby 1.9.x is still a work in progress.  Once installed, set the @JAVA_HOME@ environment variable and run @gem install buildr --platform mswin32@.
@@ -190,6 +188,17 @@ $ jruby -S buildr
 
 Run @buildr --version@ from the command line to find which version of Buildr you are using by default.  If you see @(JRuby ...)@, Buildr is running on that version of JRuby.
 
+h2. Using multiple versions of Buildr
+
+Rubygems makes it possible to install several versions of Buildr side-by-side on the same system.  If you want to run a specific version, you can do so by adding the version number between underscores ('_') as the first command-line parameter.  For example,
+
+{% highlight sh %}
+$ buildr _1.3.4_ clean   # runs Buildr v1.3.4
+
+$ buildr _1.4.4_ clean   # runs Buildr v1.4.4
+{% endhighlight %}
+
+p(note). There are two `buildr` executables installed by Rubygems.  One script serves to select the specified (or default) version of Buildr and is typically found under `/usr/bin/buildr` or `/var/lib/gems/1.8/bin/buildr`. The exact location will vary depending on your system.   The other script is the Buildr bootstrap per se and can be found under the specific version of Buildr, e.g, `/var/lib/gems/1.8/gems/buildr-1.4.0/bin/buildr`.   The first script should be on your `PATH`.   The second script should not be called directly and should not be on your `PATH`.
 
 h2(#running). Running Buildr