Is it possible to specific non-standard directories when installing a
gem? For example, I'm working in a development environment where the
libraries and headers that the gem would compile against aren't in
/usr/include and /usr/lib64 but instead are in my development
environment.
It's a PITA to install the gem and then manually go to the gem directory
and re-run "ruby extconf.rb" with the --with-qpid-{lib,include} args.
···
--
Darryl L. Pierce <mcpierce@gmail.com>
http://mcpierce.multiply.com/
"What do you care what people think, Mr. Feynman?"
% gem help install
Usage: gem install GEMNAME [GEMNAME ...] [options] -- --build-flags [options]
[... lots ...]
If an extension fails to compile during gem installation the gem
specification is not written out, but the gem remains unpacked in the
repository. You may need to specify the path to the library's headers and
libraries to continue. You can do this by adding a -- between RubyGems'
options and the extension's build options:
$ gem install some_extension_gem
[build fails]
Gem files will remain installed in \
/path/to/gems/some_extension_gem-1.0 for inspection.
Results logged to /path/to/gems/some_extension_gem-1.0/gem_make.out
$ gem install some_extension_gem -- --with-extension-lib=/path/to/lib
[build succeeds]
$ gem list some_extension_gem
···
On Jun 29, 2011, at 11:34 , Darryl L. Pierce wrote:
Is it possible to specific non-standard directories when installing a
gem? For example, I'm working in a development environment where the
libraries and headers that the gem would compile against aren't in
/usr/include and /usr/lib64 but instead are in my development
environment.
It's a PITA to install the gem and then manually go to the gem directory
and re-run "ruby extconf.rb" with the --with-qpid-{lib,include} args.
