ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Installing Chilliproject on Windows XP system - troubles

Added by Ivan Cenov at 2011-11-10 11:04 am

I'm trying to install Chilliproject 2.4.0 on my Windows system but with no success at the very beginning. Here is the log:

D:\biz\apps\chilliproject>bundle install
Fetching source index for http://rubygems.org/
Using rake (0.9.2.2)
Using activesupport (2.3.14)
Using rack (1.1.2)
Using actionpack (2.3.14)
Using actionmailer (2.3.14)
Using activerecord (2.3.14)
Using activeresource (2.3.14)
Using coderay (0.9.8)
Using columnize (0.3.4)
Using edavis10-object_daddy (0.4.3)
Using fastercsv (1.5.4)
Using i18n (0.4.2)
Installing json (1.6.1) with native extensions
Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.

"d:/Program Files/Ruby/bin/ruby.exe" extconf.rb
checking for re.h... yes
checking for ruby/st.h... yes
creating Makefile

make
'make' is not recognized as an internal or external command,
operable program or batch file.

Gem files will remain installed in d:/Program Files/Ruby/lib/ruby/gems/1.8/gems/json-1.6.1 for inspection.
Results logged to d:/Program Files/Ruby/lib/ruby/gems/1.8/gems/json-1.6.1/ext/json/ext/parser/gem_make.out
An error occured while installing json (1.6.1), and Bundler cannot continue.
Make sure that `gem install json -v '1.6.1'` succeeds before bundling.

The log of gem install json -v '1.6.1' is

D:\biz\apps\chilliproject>gem install json -v '1.6.1'
Building native extensions.  This could take a while...
ERROR:  Error installing json:
        ERROR: Failed to build gem native extension.

"d:/Program Files/Ruby/bin/ruby.exe" extconf.rb
checking for re.h... yes
checking for ruby/st.h... yes
creating Makefile

make
'make' is not recognized as an internal or external command,
operable program or batch file.

Gem files will remain installed in d:/Program Files/Ruby/lib/ruby/gems/1.8/gems/json-1.6.1 for inspection.
Results logged to d:/Program Files/Ruby/lib/ruby/gems/1.8/gems/json-1.6.1/ext/json/ext/parser/gem_make.out

What have I to do now? I tried with Redmine, and there were no such bad things. Something bundler related. Redmine installs without bundler.


Replies (5)

RE: Installing Chilliproject on Windows XP system - troubles - Added by Felix Schäfer at 2011-11-10 02:02 pm

Hi Ivan,

The problem is not with bundler but with the json gem that doesn't provide windows binaries anymore (see the gem's history and this post on the RubyInstaller Google Group). The current way to install the json gem on windows, according to the mentioned post and this StackOverflow question seems to be to install the RubyInstaller to get everything necessary installed to compile the json gem's binary parts directly.

(It might be that Redmine doesn't have this problem because the required json gem is older, can't say for sure).

RE: Installing Chilliproject on Windows XP system - troubles - Added by Holger Just at 2011-11-10 02:12 pm

Just as a remark, if I'm not mistaken, you don't need the json gem for a production ChiliProject (as well as a couple of other gems). Just run bundle install --without test development. See the Bundler page for more information about groups and which to install.

RE: Installing Chilliproject on Windows XP system - troubles - Added by Ivan Cenov at 2011-11-10 04:51 pm

Thank you for your answers. I tried with RubyInstaller DevKit. It installed. Then I saw this

D:\Program Files\Ruby\Rdevkit>gem install rdiscount --platform=ruby
Temporarily enhancing PATH to include DevKit...
Building native extensions.  This could take a while...
ERROR:  Error installing rdiscount:
        ERROR: Failed to build gem native extension.

"d:/Program Files/Ruby/bin/ruby.exe" extconf.rb
checking for random()... yes
checking for srandom()... yes
checking for rand()... yes
checking for srand()... yes
creating Makefile

make
Makefile:130: warning: overriding commands for target `d:/Program'
Makefile:124: warning: ignoring old commands for target `d:/Program'
make: *** No rule to make target `ruby.h', needed by `basename.o'.  Stop.

It seems that 'Program Files' is not a good place because of the space between 'Program' and 'Files'. By now, I am going to giving up [temporarily] because of lack of time (Redmine/Chilli administration is not my main duty at work...). Will stay with Redmine because even now we don't use all its functionality.

Thank you.

Ivan

RE: Installing Chilliproject on Windows XP system - troubles - Added by Felix Schäfer at 2011-11-10 07:23 pm

You shouldn't need rdiscount for ChiliProject if I remember well, and there again, it seems windows isn't (well) supported, sorry.

RE: Installing Chilliproject on Windows XP system - troubles - Added by Anthony Ordner at 2011-11-23 01:52 pm

Hopefully the following will be helpful to someone. Tony

On windows this is a bit tricky because the bundler/some gems want to compile native. The DevKit is needed and must be on a path without spaces... I run mine on Windows Server 2008 under c:\devkit as I have Ruby in c:\ruby. There is also an installer routine you must run to setup the devkit correctly and I think I had to edit one config file. The brief instructions are in the install.txt file inside the zip file for the devkit.
Here is the text in it:
"After extraction, place devkit and bin at the same level where Ruby was installed
(C:\Ruby for example)

Please change devkit/msys/1.0.11/etc/fstab to properly point to the right
directories for mingw and /usr/local

It provides fakes to GCC, make and sh needed by extension compilation process."

The second part about the directories for mingw and usr/local are pretty vague and very linuxy...
I never renamed it from fstab.sample so I do not think it even needed it.

I did run into additional problems with imagemagik as well which I used this to get it to work it needed the headers available to compile:
2.Install ImageMagick 6.6.x with windows installer with headers.
NOTE:
Do not install ImageMagick in a path which has spaces in it.
The default path C:/Program Files/... will not work.
Install it at a simpler path.
-
Remove any older installations of ImageMagick and RMagick
3.Set the paths in Environment Variables:

set DFImageMagick environment variable to where ImageMagick is installed
set PATH=%DFImageMagick%;%PATH% (if you don't already have it in PATH)
set CPATH=%DFImageMagick%\include;%CPATH%
set LIBRARY_PATH=%DFImageMagick%\lib;%LIBRARY_PATH%

(1-5/5)