I have a proposed changeset [1] to meet this request (they were pushed, but after a discussion this morning I've reverted the changes) and want to get feedback on it before changing the default behavior for Proton.
Currently no language binding honors the CMAKE_INSTALL_PREFIX path. So, if your current Ruby keeps its vendor extensions in /usr/share/ruby/vendor_ruby, then if you set CMAKE_INSTALL_PREFIX to /var/tmp/foo, the bindings won't isntall there. With the changes I'm proposing, the build environment asks the language for 1) the install prefix for directories and then 2) the directory for vendor extensions. It then does a string substition, replacing the install prefix in the directory with the CMAKE_INSTALL_PREFIX value provided. For power users, there's a way to override this by specifying, for each language, a different install prefix only for that language. So, for example, you could pass in RUBY_INSTALL_PREFIX to have the build environment use that instead of CMAKE_INSTALL_PREFIX. I'd like to get more input from others who use the dynamic languages as to whether this approach finds a good middle ground for what everybody expects when installing and using Proton. [1] http://reviews.apache.org/r/16004/ -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
pgpWaM6ynA2BM.pgp
Description: PGP signature
