sassc 2.0.0 → 2.4.0

data/ext/libsass/docs/build-on-windows.md

@@ -1,139 +0,0 @@
-We support builds via MingGW and via Visual Studio Community 2013.
-Both should be considered experimental (MinGW was better tested)!
-
-## Building via MingGW (makefiles)
-
-First grab the latest [MinGW for windows][1] installer. Once it is installed, you can click on continue or open the Installation Manager via `bin\mingw-get.exe`.
-
-You need to have the following components installed:
-![Visualization of components installed in the interface](https://cloud.githubusercontent.com/assets/282293/5525466/947bf396-89e6-11e4-841d-4aa916f14de1.png)
-
-Next we need to install [git for windows][2]. You probably want to check the option to add it to the global path, but you do not need to install the unix tools.
-
-If you want to run the spec test-suite you also need [ruby][3] and a few gems available. Grab the [latest installer][3] and make sure to add it the global path. Then install the missing gems:
-
-```bash
-gem install minitest
-```
-
-### Mount the mingw root directory
-
-As mentioned in the [MinGW Getting Started](http://www.mingw.org/wiki/Getting_Started#toc5) guide, you should edit `C:\MinGW\msys\1.0\etc\fstab` to contain the following line:
-
-```
-C:\MinGW   /mingw
-```
-
-### Starting a "MingGW" console
-
-Create a batch file with this content:
-```bat
-@echo off
-set PATH=C:\MinGW\bin;%PATH%
-REM only needed if not already available
-set PATH=%PROGRAMFILES%\git\bin;%PATH%
-REM C:\MinGW\msys\1.0\msys.bat
-cmd
-```
-
-Execute it and make sure these commands can be called: `git`, `mingw32-make`, `rm` and `gcc`! Once this is all set, you should be ready to compile `libsass`!
-
-### Get the sources
-
-```bash
-# using git is preferred
-git clone https://github.com/sass/libsass.git
-# only needed for sassc and/or testsuite
-git clone https://github.com/sass/sassc.git libsass/sassc
-git clone https://github.com/sass/sass-spec.git libsass/sass-spec
-```
-
-### Decide for static or shared library
-
-`libsass` can be built and linked as a `static` or as a `shared` library. The default is `static`. To change it you can set the `BUILD` environment variable:
-
-```bat
-set BUILD="shared"
-```
-
-### Compile the library
-```bash
-mingw32-make -C libsass
-```
-
-### Results can be found in
-```bash
-$ ls libsass/lib
-libsass.a  libsass.dll  libsass.so
-```
-
-### Run the spec test-suite
-```bash
-mingw32-make -C libsass test_build
-```
-
-## Building via MingGW 64bit (makefiles)
-Building libass to dll on window 64bit.
-
-+ downloads  [MinGW64 for windows7 64bit](http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.2/threads-win32/seh/x86_64-4.9.2-release-win32-seh-rt_v3-rev0.7z/download) , and unzip to "C:\mingw64".
-
-+ Create a batch file with this content:
-
-```bat
-@echo off
-set PATH=C:\mingw64\bin;%PATH%
-set CC=gcc
-REM only needed if not already available
-set PATH=%PROGRAMFILES%\Git\bin;%PATH%
-REM C:\MinGW\msys\1.0\msys.bat
-cmd
-```
-
-+ By default , mingw64 dll will depends on "​m​i​n​g​w​m​1​0​.​d​l​l​、​ ​l​i​b​g​c​c​_​s​_​d​w​2​-​1​.​d​l​l​" , we can modify Makefile to fix this:(add "-static")
-
-``` bash
-lib/libsass.dll: $(COBJECTS) $(OBJECTS) $(RCOBJECTS)
-	$(MKDIR) lib
-	$(CXX) -shared $(LDFLAGS) -o $@ $(COBJECTS) $(OBJECTS) $(RCOBJECTS) $(LDLIBS) -s -static -Wl,--subsystem,windows,--out-implib,lib/libsass.a
-```
-
-+ Compile the library
-
-```bash
-mingw32-make -C libsass
-```
-
-By the way , if you are using java jna , [JNAerator](http://jnaerator.googlecode.com/) is a good tool.
-
-## Building via Visual Studio Community 2013
-
-Open a Visual Studio 2013 command prompt:
-- `VS2013 x86 Native Tools Command Prompt`
-
-Note: When I installed the community edition, I only got the 2012 command prompts. I copied them from the Startmenu to the Desktop and adjusted the paths from `Visual Studio 11.0` to `Visual Studio 12.0`. Since `libsass` uses some `C++11` features, you need at least a MSVC 2013 compiler (v120).
-
-### Get the source
-```bash
-# using git is preferred
-git clone https://github.com/sass/libsass.git
-git clone https://github.com/sass/sassc.git libsass/sassc
-# only needed if you want to run the testsuite
-git clone https://github.com/sass/sass-spec.git libsass/sass-spec
-```
-
-### Compile sassc
-
-Sometimes `msbuild` seems not available from the command prompt. Just search for it and add it to the global path. It seems to be included in the .net folders too.
-
-```bat
-cd libsass
-REM set PATH=%PATH%;%PROGRAMFILES%\MSBuild\12.0\Bin
-msbuild /m:4 /p:Configuration=Release win\libsass.sln
-REM running the spec test-suite manually (needs ruby and minitest gem)
-ruby sass-spec\sass-spec.rb -V 3.5 -c win\bin\sassc.exe -s --impl libsass sass-spec/spec
-cd ..
-```
-
-[1]: http://sourceforge.net/projects/mingw/files/latest/download?source=files
-[2]: https://msysgit.github.io/
-[3]: http://rubyinstaller.org/

data/ext/libsass/docs/build-shared-library.md

@@ -1,35 +0,0 @@
-This page is mostly intended for people that want to build a system library that gets distributed via RPMs or other means. This is currently in a experimental phase, as we currently do not really guarantee any ABI forward compatibility. The C API was rewritten to make this possible in the future, but we want to wait some more time till we can call this final and stable.
-
-Building via autotools
---
-
-You want to build a system library only via autotools, since it will create the proper `libtool` files to make it loadable on multiple systems. We hope this works correctly, but nobody of the `libsass` core team has much knowledge in this area. Therefore we are open for comments or improvements by people that have more experience in that matter (like package maintainers from various linux distributions).
-
-```bash
-apt-get install autoconf libtool
-git clone https://github.com/sass/libsass.git
-cd libsass
-autoreconf --force --install
-./configure \
-  --disable-tests \
-  --disable-static \
-  --enable-shared \
-  --prefix=/usr
-make -j5 install
-cd ..
-```
-
-This should install these files
-```bash
-# $ ls -la /usr/lib/libsass.*
-/usr/lib/libsass.la
-/usr/lib/libsass.so -> libsass.so.0.0.9
-/usr/lib/libsass.so.0 -> libsass.so.0.0.9
-/usr/lib/libsass.so.0.0.9
-# $ ls -la /usr/include/sass*
-/usr/include/sass.h
-/usr/include/sass2scss.h
-/usr/include/sass/context.h
-/usr/include/sass/functions.h
-/usr/include/sass/values.h
-```

data/ext/libsass/docs/build-with-autotools.md

@@ -1,78 +0,0 @@
-### Get the sources
-```bash
-# using git is preferred
-git clone https://github.com/sass/libsass.git
-# only needed for sassc and/or testsuite
-git clone https://github.com/sass/sassc.git libsass/sassc
-git clone https://github.com/sass/sass-spec.git libsass/sass-spec
-```
-
-### Prerequisites
-
-In order to run autotools you need a few tools installed on your system.
-```bash
-yum install automake libtool # RedHat Linux
-emerge -a automake libtool # Gentoo Linux
-pkgin install automake libtool # SmartOS
-```
-
-
-### Create configure script
-```bash
-cd libsass
-autoreconf --force --install
-cd ..
-```
-
-### Create custom makefiles
-```bash
-cd libsass
-./configure \
-  --disable-tests \
-  --disable-shared \
-  --prefix=/usr
-cd ..
-```
-
-### Build the library
-```bash
-make -C libsass -j5
-```
-
-### Install the library
-The library will be installed to the location given as `prefix` to `configure`. This is standard behavior for autotools and not `libsass` specific.
-```bash
-make -C libsass -j5 install
-```
-
-### Configure options
-The `configure` script is created by autotools. To get an overview of available options you can call `./configure --help`. When you execute this script, it will create specific makefiles, which you then use via the regular make command.
-
-There are some `libsass` specific options:
-
-```
-Optional Features:
-  --enable-tests              enable testing the build
-  --enable-coverage           enable coverage report for test suite
-  --enable-shared             build shared libraries [default=yes]
-  --enable-static             build static libraries [default=yes]
-
-Optional Packages:
-  --with-sassc-dir=<dir>      specify directory of sassc sources for
-                              testing (default: sassc)
-  --with-sass-spec-dir=<dir>  specify directory of sass-spec for testing
-                              (default: sass-spec)
-```
-
-### Build sassc and run spec test-suite
-
-```bash
-cd libsass
-autoreconf --force --install
-./configure \
-  --enable-tests \
-  --enable-shared \
-  --prefix=/usr
-make -j5 test_build
-cd ..
-```

data/ext/libsass/docs/build-with-makefiles.md

@@ -1,68 +0,0 @@
-### Get the sources
-```bash
-# using git is preferred
-git clone https://github.com/sass/libsass.git
-# only needed for sassc and/or testsuite
-git clone https://github.com/sass/sassc.git libsass/sassc
-git clone https://github.com/sass/sass-spec.git libsass/sass-spec
-```
-
-### Decide for static or shared library
-
-`libsass` can be built and linked as a `static` or as a `shared` library. The default is `static`. To change it you can set the `BUILD` environment variable:
-
-```bash
-export BUILD="shared"
-```
-
-Alternatively you can also define it directly when calling make:
-
-```bash
-BUILD="shared" make ...
-```
-
-### Compile the library
-```bash
-make -C libsass -j5
-```
-
-### Results can be found in
-```bash
-$ ls libsass/lib
-libsass.a libsass.so
-```
-
-### Install onto the system
-
-We recommend to use [autotools to install](build-with-autotools.md) libsass onto the
-system, since that brings all the benefits of using libtools as the main install method.
-If you still want to install libsass via the makefile, you need to make sure that gnu
-`install` utility (or compatible) is installed on your system.
-```bash
-yum install coreutils # RedHat Linux
-emerge -a coreutils # Gentoo Linux
-pkgin install coreutils # SmartOS
-```
-
-You can set the install location by setting `PREFIX`
-```bash
-PREFIX="/opt/local" make install
-```
-
-
-### Compling sassc
-
-```bash
-# Let build know library location
-export SASS_LIBSASS_PATH="`pwd`/libsass"
-# Invokes the sassc makefile
-make -C libsass -j5 sassc
-```
-
-### Run the spec test-suite
-
-```bash
-# needs ruby available
-# also gem install minitest
-make -C libsass -j5 test_build
-```

data/ext/libsass/docs/build-with-mingw.md

@@ -1,107 +0,0 @@
-## Building LibSass with MingGW (makefiles)
-
-First grab the latest [MinGW for windows][1] installer. Once it is installed, you can click on continue or open the Installation Manager via `bin\mingw-get.exe`.
-
-You need to have the following components installed:
-![](https://cloud.githubusercontent.com/assets/282293/5525466/947bf396-89e6-11e4-841d-4aa916f14de1.png)
-
-Next we need to install [git for windows][2]. You probably want to check the option to add it to the global path, but you do not need to install the unix tools.
-
-If you want to run the spec test-suite you also need [ruby][3] and a few gems available. Grab the [latest installer][3] and make sure to add it the global path. Then install the missing gems:
-
-```bash
-gem install minitest
-```
-
-### Mount the mingw root directory
-
-As mentioned in the [MinGW Getting Started](http://www.mingw.org/wiki/Getting_Started#toc5) guide, you should edit `C:\MinGW\msys\1.0\etc\fstab` to contain the following line:
-
-```
-C:\MinGW   /mingw
-```
-
-### Starting a "MingGW" console
-
-Create a batch file with this content:
-```bat
-@echo off
-set PATH=C:\MinGW\bin;%PATH%
-REM only needed if not already available
-set PATH=%PROGRAMFILES%\git\bin;%PATH%
-REM C:\MinGW\msys\1.0\msys.bat
-cmd
-```
-
-Execute it and make sure these commands can be called: `git`, `mingw32-make`, `rm` and `gcc`! Once this is all set, you should be ready to compile `libsass`!
-
-### Get the sources
-
-```bash
-# using git is preferred
-git clone https://github.com/sass/libsass.git
-# only needed for sassc and/or testsuite
-git clone https://github.com/sass/sassc.git libsass/sassc
-git clone https://github.com/sass/sass-spec.git libsass/sass-spec
-```
-
-### Decide for static or shared library
-
-`libsass` can be built and linked as a `static` or as a `shared` library. The default is `static`. To change it you can set the `BUILD` environment variable:
-
-```bat
-set BUILD="shared"
-```
-
-### Compile the library
-```bash
-mingw32-make -C libsass
-```
-
-### Results can be found in
-```bash
-$ ls libsass/lib
-libsass.a  libsass.dll  libsass.so
-```
-
-### Run the spec test-suite
-```bash
-mingw32-make -C libsass test_build
-```
-
-## Building via MingGW 64bit (makefiles)
-Building libass to dll on window 64bit.
-
-Download [MinGW64 for windows7 64bit](http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.2/threads-win32/seh/x86_64-4.9.2-release-win32-seh-rt_v3-rev0.7z/download) and unzip to "C:\mingw64".
-
-Create a batch file with this content:
-
-```bat
-@echo off
-set PATH=C:\mingw64\bin;%PATH%
-set CC=gcc
-REM only needed if not already available
-set PATH=%PROGRAMFILES%\Git\bin;%PATH%
-REM C:\MinGW\msys\1.0\msys.bat
-cmd
-```
-
-By default, mingw64 dll will depends on "​m​i​n​g​w​m​1​0​.​d​l​l​、​ ​l​i​b​g​c​c​_​s​_​d​w​2​-​1​.​d​l​l​", we can modify Makefile to fix this:(add "-static")
-
-``` bash
-lib/libsass.dll: $(COBJECTS) $(OBJECTS) $(RCOBJECTS)
-	$(MKDIR) lib
-	$(CXX) -shared $(LDFLAGS) -o $@ $(COBJECTS) $(OBJECTS) $(RCOBJECTS) $(LDLIBS) -s -static -Wl,--subsystem,windows,--out-implib,lib/libsass.a
-```
-
-Compile the library
-
-```bash
-mingw32-make -C libsass
-```
-
-By the way, if you are using java jna, [JNAerator](http://jnaerator.googlecode.com/) is a good tool.
-
-[1]: http://sourceforge.net/projects/mingw/files/latest/download?source=files
-[2]: https://msysgit.github.io/
-[3]: http://rubyinstaller.org/

data/ext/libsass/docs/build-with-visual-studio.md

@@ -1,90 +0,0 @@
-## Building LibSass with Visual Studio
-
-### Requirements:
-
-The minimum requirement to build LibSass with Visual Studio is "Visual Studio 2013 Express for Desktop".
-
-Additionally, it is recommended to have `git` installed and available in `PATH`, so to deduce the `libsass` version information. For instance, if GitHub for Windows (https://windows.github.com/) is installed, the `PATH` will have an entry resembling: `X:\Users\<YOUR_NAME>\AppData\Local\GitHub\PortableGit_<SOME_GUID>\cmd\` (where `X` is the drive letter of system drive). If `git` is not available, inquiring the LibSass version will result in `[NA]`.
-
-### Build Steps:
-
-#### From Visual Studio:
-
-On opening the `win\libsass.sln` solution and build (Ctrl+Shift+B) to build `libsass.dll`.
-
-To Build LibSass as a static Library, it is recommended to set an environment variable `LIBSASS_STATIC_LIB` before launching the project:
-
-```cmd
-cd path\to\libsass
-SET LIBSASS_STATIC_LIB=1
-::
-:: or in PowerShell:
-:: $env:LIBSASS_STATIC_LIB=1
-::
-win\libsass.sln
-```
-
-Visual Studio will form the filtered source tree as shown below:
-
-![image](https://cloud.githubusercontent.com/assets/3840695/9298985/aae9e072-44bf-11e5-89eb-e7995c098085.png)
-
-`Header Files` contains the .h and .hpp files, while `Source Files` covers `.c` and `.cpp`. The other used headers/sources will appear under `External Dependencies`.
-
-If there is a LibSass code file appearing under External Dependencies, it can be changed by altering the `win\libsass.vcxproj.filters` file or dragging in Solution Explorer.
-
-#### From Command Prompt:
-
-Notice that in the following commands:
-
-* If the platform is 32-bit Windows, replace `ProgramFiles(x86)` with `ProgramFiles`.
-* To build with Visual Studio 2015, replace `12.0` with `14.0` in the aforementioned command.
-
-Open a command prompt:
-
-To build dynamic/shared library (`libsass.dll`):
-
-```cmd
-:: debug build:
-"%ProgramFiles(x86)%\MSBuild\12.0\Bin\MSBuild" win\libsass.sln
-
-:: release build:
-"%ProgramFiles(x86)%\MSBuild\12.0\Bin\MSBuild" win\libsass.sln ^
-/p:Configuration=Release
-```
-
-To build static library (`libsass.lib`):
-
-```cmd
-:: debug build:
-"%ProgramFiles(x86)%\MSBuild\12.0\Bin\MSBuild" win\libsass.sln ^
-/p:LIBSASS_STATIC_LIB=1
-
-:: release build:
-"%ProgramFiles(x86)%\MSBuild\12.0\Bin\MSBuild" win\libsass.sln ^
-/p:LIBSASS_STATIC_LIB=1 /p:Configuration=Release
-```
-
-#### From PowerShell:
-
-To build dynamic/shared library (`libsass.dll`):
-
-```powershell
-# debug build:
-&"${env:ProgramFiles(x86)}\MSBuild\12.0\Bin\MSBuild" win\libsass.sln
-
-# release build:
-&"${env:ProgramFiles(x86)}\MSBuild\12.0\Bin\MSBuild" win\libsass.sln `
-/p:Configuration=Release
-```
-
-To build static library (`libsass.lib`):
-
-```powershell
-# build:
-&"${env:ProgramFiles(x86)}\MSBuild\12.0\Bin\MSBuild" win\libsass.sln `
-/p:LIBSASS_STATIC_LIB=1
-
-# release build:
-&"${env:ProgramFiles(x86)}\MSBuild\12.0\Bin\MSBuild" win\libsass.sln `
-/p:LIBSASS_STATIC_LIB=1 /p:Configuration=Release
-```