Sassc Ruby should detect presence of existing libsass.so

[edward]

@bolandrm how would you feel about having the ext/Rakefile check for an existing libsass.so before it compiles its own? This would also involve performing the detection or setting something in SassC::Native.

I say this because having just the one built libsass.so will speed up CI times for projects that use sassc-ruby.

[bolandrm]

i'm a bit fuzzy on how this would work. where does the libsass.so live? For most CIs, isn't the whole environment cleaned up after each run?

[edward]

The libsass.so will live where ever lib files get installed; somewhere like /usr/local/lib depending on your environment setup.

If we can pre-install binaries of libsass.so then we won’t have to compile them every CI run.

[edward]

Actually… let’s forget this for now. Gem caching should be sufficient to do what I need.

[agis]

This is useful for people that don't want to use the bundled libsass. Is there any interest in moving this forward?

cc @edward @bolandrm

[edward]

@agis I think it’d be neat! I didn’t follow up on this since I had to focus on other stuff urgently but it could still be helpful.

I’d be open to taking a look at a PR with the caveat that I haven’t looked at the code in 3 years and am just coming back to work after being off on parental leave for a year 😬

[ebgc]

1+

pls support this - no need to add redundancy - each gem compiling its own lib if lib exists on system already.

i.e. nokogiri supports it via NOKOGIRI_USE_SYSTEM_LIBRARIES variable

it also reduces overhead of installing compilers to system where gem has to be installed