You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@buildr.apache.org by Will Rogers <wj...@gmail.com> on 2009/12/17 16:48:34 UTC
rjb-1.1.9 does not build on Windows with JDK in default location
I just went through an unpleasant two hours trying to get buildr to install
on Windows. May I make two suggestions to improve your "Installing on
Windows" section at http://buildr.apache.org/installing.html ?
1. Installing the Ruby one-click installer is not enough, you also need the
devkit so you have a compiler and make. The devkit is a 7zip file available
on the same page as the one-click installer. You just extract it to your
Ruby directory and make sure the paths in devkit/msys/1.0.11/etc/fstab are
accurate.
2. The version rjb-1.1.9 required by buildr-1.3.5 does not build when your
JAVA_HOME has spaces in the path. The default install location is in
"C:/Program Files", which means rjb will not build. rjb-1.2.0 works, so
please either release an updated buildr gem that works with this fixed
version of rjb or suggest a work-around of installing the JDK to a
non-default location with no spaces in the path.
Thanks,
-- Will
Re: rjb-1.1.9 does not build on Windows with JDK in default location
Posted by Will Rogers <wj...@gmail.com>.
On Thu, Dec 17, 2009 at 1:43 PM, Assaf Arkin <as...@labnotes.org> wrote:
> I think they're just using a different platform identifier, because their
> suggestion is:
>
> gem install --platform=mswin32
Thanks for clarifying the problem. To follow up, I can confirm that
buildr installs and works with:
gem install buildr --platform mswin32
Maybe that's what you should put in your installation guide? Contrary
to what I said in my first mail, with this fix the ruby installer
devkit is not necessary because rubygems installs the binary gems as
you intended. It might also be worth mentioning that you need Ruby
1.8, not Ruby 1.9, because the ruby installer page lists both without
guidance. Users might tend to choose the higher number ;)
-- Will
Re: rjb-1.1.9 does not build on Windows with JDK in default location
Posted by Assaf Arkin <as...@labnotes.org>.
On Thu, Dec 17, 2009 at 10:29 AM, Will Rogers <wj...@gmail.com> wrote:
> On Thu, Dec 17, 2009 at 1:23 PM, Assaf Arkin <as...@labnotes.org> wrote:
> > > 2. The version rjb-1.1.9 required by buildr-1.3.5 does not build when
> your
> > > JAVA_HOME has spaces in the path
> >
> > I'm not sure why you're getting the all-platforms gem with RJB 1.1.9
> > dependency, but you shouldn't. Could be one of the gems was in the
> > switchover from Rubyforge to Gemcutter?
>
> The latest versions of the Ruby one click installer are compiled with
> mingw, not msvc6, and I believe that means they are not binary
> compatible with -mswin32 gems. Rubygems selects the basic
> all-platforms gems with this build of Ruby.
>
I think they're just using a different platform identifier, because their
suggestion is:
gem install --platform=mswin32
http://wiki.github.com/oneclick/rubyinstaller/gem-list
Could be targeted with a specific Buildr gem that's identical to -mswin32
but has the proper platform identifier to match one-click installer.
Assaf
Re: rjb-1.1.9 does not build on Windows with JDK in default location
Posted by Will Rogers <wj...@gmail.com>.
On Thu, Dec 17, 2009 at 1:23 PM, Assaf Arkin <as...@labnotes.org> wrote:
> > 2. The version rjb-1.1.9 required by buildr-1.3.5 does not build when your
> > JAVA_HOME has spaces in the path
>
> I'm not sure why you're getting the all-platforms gem with RJB 1.1.9
> dependency, but you shouldn't. Could be one of the gems was in the
> switchover from Rubyforge to Gemcutter?
The latest versions of the Ruby one click installer are compiled with
mingw, not msvc6, and I believe that means they are not binary
compatible with -mswin32 gems. Rubygems selects the basic
all-platforms gems with this build of Ruby.
Re: rjb-1.1.9 does not build on Windows with JDK in default location
Posted by Assaf Arkin <as...@labnotes.org>.
On Thu, Dec 17, 2009 at 7:48 AM, Will Rogers <wj...@gmail.com> wrote:
> I just went through an unpleasant two hours trying to get buildr to install
> on Windows. May I make two suggestions to improve your "Installing on
> Windows" section at http://buildr.apache.org/installing.html ?
>
> 1. Installing the Ruby one-click installer is not enough, you also need the
> devkit so you have a compiler and make. The devkit is a 7zip file available
> on the same page as the one-click installer. You just extract it to your
> Ruby directory and make sure the paths in devkit/msys/1.0.11/etc/fstab are
> accurate.
>
> 2. The version rjb-1.1.9 required by buildr-1.3.5 does not build when your
> JAVA_HOME has spaces in the path. The default install location is in
> "C:/Program Files", which means rjb will not build. rjb-1.2.0 works, so
> please either release an updated buildr gem that works with this fixed
> version of rjb or suggest a work-around of installing the JDK to a
> non-default location with no spaces in the path.
>
RJB gems intended for windows include the DDL, so there's nothing to build,
just install and use it. RJB 1.1.9 was introduced to fix build issues under
Snow Leopard, but adds nothing new over 1.1.6 for Windows users.
If you see a gem with -x86-mswin32 in that name, that release has relevant
changes that affect all platforms (including Windows). All other releases
not intended for Windows:
http://rubyforge.org/frs/?group_id=2010
Buildr handles that by publishing three gems for each release: -java for
JRuby (no RJB), -x86-mswin32 for Windows (RJB 1.1.6) and one for all other
platforms (RJB 1.1.9):
http://rubyforge.org/frs/?group_id=3180
http://github.com/apache/buildr/blob/trunk/buildr.gemspec
I'm not sure why you're getting the all-platforms gem with RJB 1.1.9
dependency, but you shouldn't. Could be one of the gems was in the
switchover from Rubyforge to Gemcutter?
Assaf
>
>
> Thanks,
>
> -- Will
>
Re: rjb-1.1.9 does not build on Windows with JDK in default location
Posted by Alex Boisvert <al...@gmail.com>.
Hi Will,
Thanks for sharing your experience. I'm sure it will be useful to others.
On Thu, Dec 17, 2009 at 7:48 AM, Will Rogers <wj...@gmail.com> wrote:
> I just went through an unpleasant two hours trying to get buildr to install
> on Windows. May I make two suggestions to improve your "Installing on
> Windows" section at http://buildr.apache.org/installing.html ?
>
> 1. Installing the Ruby one-click installer is not enough, you also need the
> devkit so you have a compiler and make. The devkit is a 7zip file available
> on the same page as the one-click installer. You just extract it to your
> Ruby directory and make sure the paths in devkit/msys/1.0.11/etc/fstab are
> accurate.
>
Ok, added a mention of the devkit under the Windows section. (Website not
yet updated)
> 2. The version rjb-1.1.9 required by buildr-1.3.5 does not build when your
> JAVA_HOME has spaces in the path. The default install location is in
> "C:/Program Files", which means rjb will not build. rjb-1.2.0 works, so
> please either release an updated buildr gem that works with this fixed
> version of rjb or suggest a work-around of installing the JDK to a
> non-default location with no spaces in the path.
>
Ok, we'll upgrade to rjb-1.2.0 for Buildr 1.4.0 so this shouldn't be an
issue in the future.
http://issues.apache.org/jira/browse/BUILDR-356
alex