-
Notifications
You must be signed in to change notification settings - Fork 22
Can't get this gem working on my project on Yosemite, so going step by step #9
Description
I can't get it working in my (non-Rails) project, it complains about the same issues as someone talked about on Stack Overflow:
https://stackoverflow.com/questions/26688631/using-libsass-with-rails-asset-pipeline
So I'm going to try to fix the problem by going step by step in this gem and getting help along each step of the way. My first obvious port of call is to clone the github sources, bundle install and ensure the automated tests run.
$ ruby -v
ruby 1.9.3p429 (2013-05-15 revision 40747) [x86_64-darwin14.0.0]
$ bundle
Fetching gem metadata from https://rubygems.org/..........
Resolving dependencies...
Using rake 10.3.2
Using hitimes 1.2.2
Using timers 4.0.1
Using celluloid 0.16.0
Using coderay 1.1.0
Using ffi 1.9.3
Using formatador 0.2.5
Using rb-fsevent 0.9.4
Using rb-inotify 0.9.5
Using listen 2.7.9
Using lumberjack 1.0.9
Using method_source 0.8.2
Using slop 3.6.0
Using pry 0.10.1
Using thor 0.19.1
Using guard 2.6.1
Using test-unit 2.5.5
Using guard-test 2.0.5
Installing rake-compiler 0.9.3
Using sassc 0.3 from source at .
Using bundler 1.7.7
Your bundle is complete!
Use `bundle show [gemname]` to see where a bundled gem is installed.
$ bundle exec rake test
$ bundle exec rake spec
$
So no tests of any description ran (or they all ran, but output nothing) and neither rake command gave an error. I'm assuming that no tests ran because doing this also outputs nothing:
$ bundle exec rake spec SPEC_OPTS="--format documentation"
$
So, can anyone else get the tests to run, if so, what am I missing?
Next step after this one is to try to create a simple test case that uses the gem and report problems with it...