You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 14, 2019. It is now read-only.
Libsass is just a library, but if you want to RUN libsass,
11
11
then go to http://github.com/hcatlin/sassc or
12
-
http://github.com/hcatlin/sassruby or find your local
13
-
implementer.
12
+
http://github.com/hcatlin/sassruby or
13
+
[find your local implementer](https://github.com/hcatlin/libsass/wiki/Implementations).
14
14
15
15
About
16
16
-----
@@ -22,10 +22,10 @@ This library strives to be light, simple, and easy to build and integrate with a
22
22
Developing
23
23
----------
24
24
25
-
As you may have noticed, the libsass repo itself has
25
+
As you may have noticed, the libsass repo itself has
26
26
no executables and no tests. Oh noes! How can you develop???
27
27
28
-
Well, luckily, SassC is the official binary wrapper for
28
+
Well, luckily, SassC is the official binary wrapper for
29
29
libsass and is *always* kept in sync. SassC uses a git submodule
30
30
to include libsass. When developing libsass, its best to actually
31
31
check out SassC and develop in that directory with the SassC spec
@@ -38,15 +38,7 @@ Tests
38
38
39
39
Since libsass is a pure library, tests are run through the [SassSpec](http://github.com/hcatlin/sass-spec) project using the [SassC](http://github.com/hcatlin/sassc) driver.
40
40
41
-
To run tests against libsass while developing, please ensure you have the latest version of the above projects cloned, and then define the following environment variables:
42
-
43
-
export SASS_SPEC_PATH=~/path/sass-spec
44
-
export SASS_SASSC_PATH=~/path/sassc
45
-
export SASS_LIBSASS_PATH=~/path/libsass
46
-
47
-
Obviously, update them to your local environment. Then, its just a matter of running...
48
-
49
-
make test
41
+
To run tests against libsass while developing, you can run `./script/spec`. This will clone SassC and Sass-Spec under the project folder and then run the Sass-Spec test suite. You may want to update the clones to ensure you have the latest version.
50
42
51
43
Usage
52
44
-----
@@ -56,19 +48,21 @@ C interface that is defined in [sass_interface.h]. Its usage is pretty
56
48
straight forward.
57
49
58
50
First, you create a sass context struct. We use these objects to define
59
-
different execution parameters for the library. There are three
60
-
different context types.
51
+
different execution parameters for the library. There are three
0 commit comments