We support builds via MingGW and via Visual Studio Community 2013. Both should be considered experimental (MinGW was better tested)!
First grab the latest MinGW for windows 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:
Next we need to install git for windows. 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 and a few gems available. Grab the latest installer and make sure to add it the global path. Then install the missing gems:
gem install minitest
As mentioned in the MinGW Getting Started guide, you should edit C:\MinGW\msys\1.0\etc\fstab
to contain the following line:
C:\MinGW /mingw
Create a batch file with this content:
@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
!
# 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
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:
set BUILD="shared"
mingw32-make -C libsass
$ ls libsass/lib
libsass.a libsass.dll libsass.so
mingw32-make -C libsass test_build
Building libass to dll on window 64bit.
downloads MinGW64 for windows7 64bit , and unzip to "C:\mingw64".
Create a batch file with this content:
@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
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
mingw32-make -C libsass
By the way , if you are using java jna , JNAerator is a good tool.
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).
# 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
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.
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 -c win\bin\sassc.exe -s --impl libsass sass-spec/spec
cd ..
Any scripts or data that you put into this service are public.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.