Forum: Ruby Ruby hard-codes load-path into dll/dylib?

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
D2bff075522befb15313dab85f3a671b?d=identicon&s=25 Kevin Walzer (codebykevin)
on 2014-04-28 02:54
(Received via mailing list)
I am still working on creating a system for deploying a standalone Ruby
app on the Mac, i.e. self-contained with all libraries and code in the
application package, so that users do not have to install anything
separately.

The Mac provides good tools for this, including a command-line program
called install_name_tool that allows you to re-link executables to other
libraries. It appears, though, that this tool has no effect on the Ruby
dylib I am including in my application; the load path is hard-coded into
the library based on the original compilation, and Ruby searches there
rather than within the Ruby installation in my application bundle.

Is there any way to override this? I'm doing so from C with an emedded
interpreter.

--Kevin
D5ce39acdbd95936845dd06827b75689?d=identicon&s=25 Chris Tonkinson (Guest)
on 2014-04-28 03:10
(Received via mailing list)
> self-contained

Sounds like a job for Docker https://www.docker.io/
04f5e260b2169925efcdffa51c52419e?d=identicon&s=25 Zipizap zipizap (zipizap)
on 2014-04-28 18:31
(Received via mailing list)
Have a look at Tokaido - its purpose is very similar to what you seem to
be
doing...
04f5e260b2169925efcdffa51c52419e?d=identicon&s=25 Zipizap zipizap (zipizap)
on 2014-04-28 18:31
(Received via mailing list)
This topic is locked and can not be replied to.