Skip to content
This repository was archived by the owner on Jul 24, 2024. It is now read-only.

Check for other libsass installations before installing from binary #139

Closed
farneman opened this issue Aug 8, 2013 · 2 comments
Closed

Check for other libsass installations before installing from binary #139

farneman opened this issue Aug 8, 2013 · 2 comments

Comments

@farneman
Copy link

farneman commented Aug 8, 2013

It's very helpful that your're providing binaries to install libsass. However I'm curious if it would be feasible to hcekc for other installations of libsass before installing from the included binary? For instance checking against popular package management systems like Homebrew that can install libsass. There maybe other complications (such as version mismatches) that make this impossible to do reliably right now, I'm just curious.
@andrew
Copy link
Contributor

andrew commented Aug 8, 2013

That sounds like it could be good, but the c++ binding file in a particular version of node-sass is very closely linked to the version of libsass bundled with it, I suspect it would cause more headache than it's worth.

@farneman
Copy link
Author

farneman commented Aug 8, 2013

Gotcha, I was guessing that would be the case. Thanks though.

@farneman farneman closed this as completed Aug 8, 2013
saper added a commit to saper/node-sass that referenced this issue Mar 15, 2015
@saper
Build with the unbundled libsass
8c9399d 
If PKGCONFIG is set to YES in the proces
environment, use pkg-config to locate
system libsass to be linked.

This way there is no need to checkout
a src/libsass submodule at all and
the library from the package management
system can be used.

Otherwise fallback to the bundled libsass.

By default, use the bundled library.

PR: sass#139
PR: sass#389
PR: sass#744
@saper saper mentioned this issue Mar 15, 2015
Merged
saper added a commit to saper/node-sass that referenced this issue Mar 16, 2015
@saper
Build with the unbundled libsass
dd42bf3 
If PKGCONFIG is set to YES in the proces
environment, use pkg-config to locate
system libsass to be linked.

This way there is no need to checkout
a src/libsass submodule at all and
the library from the package management
system can be used.

Otherwise fallback to the bundled libsass.

By default, use the bundled library.

PR: sass#139
PR: sass#389
PR: sass#744
saper added a commit to saper/node-sass that referenced this issue Mar 16, 2015
@saper
Build with the unbundled libsass
478b2b3 
Use environment variables to control
how libsass is linked:

LIBSASS_EXT variable empty or unset

Build a bundled libsass source
(from src/libsass).
This is the default.

LIBSASS_EXT=auto

libsass is located using pkg-config
and linked dynamically

LIBSASS_EXT=yes
LIBSASS_CFLAGS=
LIBSASS_LDFLAGS=

Link libsass manually, by adding
compiler flags and linker flags
in LIBSASS_CFLAGS and LIBSASS_LDFLAGS,
respectively.

For example this way libsass can
be linked in statically (on Unix):

LIBSASS_EXT=yes
LIBSASS_CFLAGS=-I/usr/local/include
LIBSASS_LDFLAGS=/usr/local/lib/libsass.a

When using LIBSASS_EXT there is no need
to checkout the libsass source into src/libsass submodule
and the library from the package management
system can be used.

PR: sass#139
PR: sass#389
PR: sass#744
saper added a commit to saper/node-sass that referenced this issue Mar 16, 2015
@saper
Build with the unbundled libsass
19a36b4 
Use environment variables to control
how libsass is linked:

LIBSASS_EXT variable empty or unset

Build a bundled libsass source
(from src/libsass).
This is the default.

LIBSASS_EXT=auto

libsass is located using pkg-config
and linked dynamically

LIBSASS_EXT=yes
LIBSASS_CFLAGS=
LIBSASS_LDFLAGS=

Link libsass manually, by adding
compiler flags and linker flags
in LIBSASS_CFLAGS and LIBSASS_LDFLAGS,
respectively.

For example this way libsass can
be linked in statically (on Unix):

LIBSASS_EXT=yes
LIBSASS_CFLAGS=-I/usr/local/include
LIBSASS_LDFLAGS=/usr/local/lib/libsass.a

When using LIBSASS_EXT there is no need
to checkout the libsass source into src/libsass submodule
and the library from the package management
system can be used.

PR: sass#139
PR: sass#389
PR: sass#744
saper added a commit to saper/node-sass that referenced this issue Mar 16, 2015
@saper
Build with the unbundled libsass
1a9b7b4 
Use environment variables to control
how libsass is linked:

LIBSASS_EXT variable empty or unset

Build a bundled libsass source
(from src/libsass).
This is the default.

LIBSASS_EXT=auto

libsass is located using pkg-config
and linked dynamically

LIBSASS_EXT=yes
LIBSASS_CFLAGS=
LIBSASS_LDFLAGS=

Link libsass manually, by adding
compiler flags and linker flags
in LIBSASS_CFLAGS and LIBSASS_LDFLAGS,
respectively.

For example this way libsass can
be linked in statically (on Unix):

LIBSASS_EXT=yes
LIBSASS_CFLAGS=-I/usr/local/include
LIBSASS_LDFLAGS=/usr/local/lib/libsass.a

When using LIBSASS_EXT there is no need
to checkout the libsass source into src/libsass submodule
and the library from the package management
system can be used.

PR: sass#139
PR: sass#389
PR: sass#744
saper added a commit to saper/node-sass that referenced this issue Mar 16, 2015
@saper
Build with the unbundled libsass
a96905e 
Use environment variables to control
how libsass is linked:

LIBSASS_EXT variable empty or unset

Build a bundled libsass source
(from src/libsass).
This is the default.

LIBSASS_EXT=auto

libsass is located using pkg-config
and linked dynamically

LIBSASS_EXT=yes
LIBSASS_CFLAGS=
LIBSASS_LDFLAGS=

Link libsass manually, by adding
compiler flags and linker flags
in LIBSASS_CFLAGS and LIBSASS_LDFLAGS,
respectively.

For example this way libsass can
be linked in statically (on Unix):

LIBSASS_EXT=yes
LIBSASS_CFLAGS=-I/usr/local/include
LIBSASS_LDFLAGS=/usr/local/lib/libsass.a

When using LIBSASS_EXT there is no need
to checkout the libsass source into src/libsass submodule
and the library from the package management
system can be used.

PR: sass#139
PR: sass#389
PR: sass#744
saper added a commit to saper/node-sass that referenced this issue Mar 16, 2015
@saper
Build with the unbundled libsass
61f8535 
Use environment variables to control
how libsass is linked:

LIBSASS_EXT variable empty or unset

Build a bundled libsass source
(from src/libsass).
This is the default.

LIBSASS_EXT=auto

libsass is located using pkg-config
and linked dynamically

LIBSASS_EXT=yes
LIBSASS_CFLAGS=
LIBSASS_LDFLAGS=

Link libsass manually, by adding
compiler flags and linker flags
in LIBSASS_CFLAGS and LIBSASS_LDFLAGS,
respectively.

For example this way libsass can
be linked in statically (on Unix):

LIBSASS_EXT=yes
LIBSASS_CFLAGS=-I/usr/local/include
LIBSASS_LDFLAGS=/usr/local/lib/libsass.a

When using LIBSASS_EXT there is no need
to checkout the libsass source into src/libsass submodule
and the library from the package management
system can be used.

PR: sass#139
PR: sass#389
PR: sass#744
saper added a commit to saper/node-sass that referenced this issue Mar 16, 2015
@saper
Build with the unbundled libsass
b5075f0 
Use environment variables to control
how libsass is linked:

LIBSASS_EXT variable empty or unset

Build a bundled libsass source
(from src/libsass).
This is the default.

LIBSASS_EXT=auto

libsass is located using pkg-config
and linked dynamically

LIBSASS_EXT=yes
LIBSASS_CFLAGS=    compiler flags
LIBSASS_LDFLAGS=   linker flags
LIBSASS_LIBRARY=   library to link

Link libsass manually, by adding
compiler and linker flags.

For example this way libsass can
be linked in statically (on Unix):

LIBSASS_EXT=yes
LIBSASS_CFLAGS=-I/usr/local/include
LIBSASS_LIBRARY=/usr/local/lib/libsass.a

When using LIBSASS_EXT there is no need
to checkout the libsass source into src/libsass submodule
and the library from the package management
system can be used.

PR: sass#139
PR: sass#389
PR: sass#744
saper added a commit to saper/node-sass that referenced this issue Mar 16, 2015
@saper
Build with the unbundled libsass
cdf5ab2 
Use environment variables to control
how libsass is linked:

LIBSASS_EXT variable empty or unset

Build a bundled libsass source
(from src/libsass).
This is the default.

LIBSASS_EXT=auto

libsass is located using pkg-config
and linked dynamically

LIBSASS_EXT=yes
LIBSASS_CFLAGS=    compiler flags
LIBSASS_LDFLAGS=   linker flags
LIBSASS_LIBRARY=   library to link

Link libsass manually, by adding
compiler and linker flags.

For example this way libsass can
be linked in statically (on Unix):

LIBSASS_EXT=yes
LIBSASS_CFLAGS=-I/usr/local/include
LIBSASS_LIBRARY=/usr/local/lib/libsass.a

When using LIBSASS_EXT there is no need
to checkout the libsass source into src/libsass submodule
and the library from the package management
system can be used.

PR: sass#139
PR: sass#389
PR: sass#744

Conflicts:
	scripts/build.js
saper added a commit to saper/node-sass that referenced this issue Mar 17, 2015
@saper
Build with the unbundled libsass
fb3eb14 
Use environment variables to control
how libsass is linked:

LIBSASS_EXT variable empty or unset

Build a bundled libsass source
(from src/libsass).
This is the default.

LIBSASS_EXT=auto

libsass is located using pkg-config
and linked dynamically

LIBSASS_EXT=yes
LIBSASS_CFLAGS=    compiler flags
LIBSASS_LDFLAGS=   linker flags
LIBSASS_LIBRARY=   library to link

Link libsass manually, by adding
compiler and linker flags.

For example this way libsass can
be linked in statically (on Unix):

LIBSASS_EXT=yes
LIBSASS_CFLAGS=-I/usr/local/include
LIBSASS_LIBRARY=/usr/local/lib/libsass.a

When using LIBSASS_EXT there is no need
to checkout the libsass source into src/libsass submodule
and the library from the package management
system can be used.

PR: sass#139
PR: sass#389
PR: sass#744
saper added a commit to saper/node-sass that referenced this issue Mar 17, 2015
@saper
Build with the unbundled libsass
054440d 
Use environment variables to control
how libsass is linked:

LIBSASS_EXT variable empty or unset

Build a bundled libsass source
(from src/libsass).
This is the default.

LIBSASS_EXT=auto

libsass is located using pkg-config
and linked dynamically

LIBSASS_EXT=yes
LIBSASS_CFLAGS=    compiler flags
LIBSASS_LDFLAGS=   linker flags
LIBSASS_LIBRARY=   library to link

Link libsass manually, by adding
compiler and linker flags.

For example this way libsass can
be linked in statically (on Unix):

LIBSASS_EXT=yes
LIBSASS_CFLAGS=-I/usr/local/include
LIBSASS_LIBRARY=/usr/local/lib/libsass.a

When using LIBSASS_EXT there is no need
to checkout the libsass source into src/libsass submodule
and the library from the package management
system can be used.

PR: sass#139
PR: sass#389
PR: sass#744

Conflicts:
	scripts/build.js
saper added a commit to saper/node-sass that referenced this issue Mar 20, 2015
@saper
Build with the unbundled libsass
b03a226 
Use environment variables to control
how libsass is linked:

LIBSASS_EXT variable empty or unset

Build a bundled libsass source
(from src/libsass).
This is the default.

LIBSASS_EXT=auto

libsass is located using pkg-config
and linked dynamically

LIBSASS_EXT=yes
LIBSASS_CFLAGS=    compiler flags
LIBSASS_LDFLAGS=   linker flags
LIBSASS_LIBRARY=   library to link

Link libsass manually, by adding
compiler and linker flags.

For example this way libsass can
be linked in statically (on Unix):

LIBSASS_EXT=yes
LIBSASS_CFLAGS=-I/usr/local/include
LIBSASS_LIBRARY=/usr/local/lib/libsass.a

When using LIBSASS_EXT there is no need
to checkout the libsass source into src/libsass submodule
and the library from the package management
system can be used.

PR: sass#139
PR: sass#389
PR: sass#744

Conflicts:
	binding.gyp
	scripts/build.js
	src/sass_context_wrapper.h
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@andrew @farneman