currently, Hubris needs to know where the ruby headers are when it's installed. this is pretty awkward, and makes it harder to install. It should be possible to defer this to the time that the Hubrify binary is actually run: that way, the running ruby process can pass the configuration information on the command line. Same goes for libruby.so
currently, Hubris needs to know where the ruby headers are when it's installed. this is pretty awkward, and makes it harder to install. It should be possible to defer this to the time that the Hubrify binary is actually run: that way, the running ruby process can pass the configuration information on the command line. Same goes for libruby.so