ender672
Doesn't recognize vips 7.30.2
I have tried installing ruby-vips via the gem installer and via ./compile from the source here on github and both give me the same response: neither finds a suitable vips candidate. It lists from 7.29 down to 7.20 as valid options but not the current 7.30 (which I have installed).
Just for kicks I tried adding '7.30' in the ext/extconf.rb file where it lists the versions but it still failed to compile (but printed out 7.30 in the included version list it printed before).
I also tried adding '--with-pkg-config=vips' like it mentions in a comment in the extconf.rb file but still nothing.
@Bramamine, did you know that the fresh and working fork of ruby-vips exists here: https://github.com/jcupitt/ruby-vips/ ?
Please repost this issue there and close it here, if you still have this problem.
Timothy (@ender672), could you please update the README to reflect the fact that ruby-vips is alive at jcupitt/ruby-vips fork?!
/cc @jcupitt
Hey ender,
Yeah I actually got it working and have been in contact with jcupitt.
Thank you.
Brad
On Sep 24, 2012, at 3:03 AM, Stanislaw Pankevich [email protected] wrote:
@Bramamine, did you know that the fresh and working fork of ruby-vips exists here: https://github.com/jcupitt/ruby-vips/ ?
Please repost this issue there and close it here, if you still have this problem.
Timothy (@ender672), could you please update the README to reflect the fact that ruby-vips is alive at jcupitt/ruby-vips fork?!
/cc @jcupitt
— Reply to this email directly or view it on GitHub.
fwiw, I had the same problem and it was not solvable by switching to @jcupitt's fork. After a little digging, it appears that in Mountain Lion there were a few .pc files that are no longer shipped for some (probably stupid) reason, and libxml2 is one of them. I found one in /usr/local/Library/ENV/pkgconfig/mountain_lion/libxml-2.0.pc. Try doing a brew update if you need to. Then add the following to ~/.bash_profile:
export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/Library/ENV/pkgconfig/mountain_lion
Start a new terminal and hopefully you should be good to go.
