Windows install issue
adrian-riveresolutions opened this issue · 2 comments
Hoping that someone can help with a Windows install problem for dandelion. This what I'm getting so far:
C:\Users\adrian>gem install dandelion
Temporarily enhancing PATH to include DevKit...
Building native extensions. This could take a while...
ERROR: Error installing dandelion:
ERROR: Failed to build gem native extension.
current directory: E:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/rugged-0.23.3/ext/
rugged
E:/Ruby23-x64/bin/ruby.exe -r ./siteconf20160822-30412-1h062it.rb extconf.rb
checking for gmake... no
checking for make... yes
checking for cmake... no
ERROR: CMake is required to build Rugged.
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.
Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=E:/Ruby23-x64/bin/$(RUBY_BASE_NAME)
--use-system-libraries
To see why this extension failed to compile, please check the mkmf.log which can
be found here:
E:/Ruby23-x64/lib/ruby/gems/2.3.0/extensions/x64-mingw32/2.3.0/rugged-0.23.3/m
kmf.log
extconf failed, exit code 1
Gem files will remain installed in E:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/rugged
-0.23.3 for inspection.
Results logged to E:/Ruby23-x64/lib/ruby/gems/2.3.0/extensions/x64-mingw32/2.3.0
/rugged-0.23.3/gem_make.out
I have installed CMake 3.6.1 from https://cmake.org/download/ but I'm still getting the same result. Despite having chosen during the CMake install to add the environmental variable path it hadn't. I tried manually adding the path to the CMake.exe folder and separately tried adding the full path the CMake,exe but this didn't make any difference.
Any advice would be very much appreciated. Thanks.
This looks similar to #115. I'm not sure of the solution at this point. Perhaps @leandroruel or @ultraloveninja could help here?
Hmmm, yeah. I'm not sure either. Most of the issues that I had stemmed from Cmake on a Mac and having an outdated Ruby lib. Once I had all of those aligned, it seemed to work just fine.