nokogiri should compile with system libs #124

Merged
merged 1 commit into from Aug 5, 2013

Conversation

Projects
None yet
2 participants
Owner

hone commented Aug 5, 2013

As of nokogiri 1.6.0, they default to using the vendored libxml2 libs.
This is problematic for two reasons. First, with the way the heroku
build environment works,
sparklemotion/nokogiri#923. This means it
won't link nokogiri.so properly since it's dependent on hardcoded paths
that don't exist during runtime. Second, compiling libxml2 and friends
is unnecessary since we have them already setup. We should skip this to
speed up deploys.

@hone hone nokogiri should compile with system libs
As of nokogiri 1.6.0, they default to using the vendored libxml2 libs.
This is problematic for two reasons. First, with the way the heroku
build environment works,
sparklemotion/nokogiri#923. This means it
won't link nokogiri.so properly since it's dependent on hardcoded paths
that don't exist during runtime. Second, compiling libxml2 and friends
is unnecessary since we have them already setup. We should skip this to
speed up deploys.
05a8582
Owner

hone commented Aug 5, 2013

tests are passing for me locally. Not sure what's up with Travis.

@hone hone added a commit that referenced this pull request Aug 5, 2013

@hone hone Merge pull request #124 from heroku/nokogiri
nokogiri should compile with system libs
b6687d1

@hone hone merged commit b6687d1 into master Aug 5, 2013

1 check failed

default The Travis CI build failed
Details

hone deleted the nokogiri branch Aug 5, 2013

Owner

danp commented Aug 6, 2013

Nice, does this make the slug smaller too?

Owner

hone commented Aug 6, 2013

it should b/c it doesn't compile the ext/ stuff, but i haven't done comparison tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment