Chris Friedt

That's a good question! I have not got to that part in terms of adding it to the README.md file yet. It should be very easy, and I would welcome...

If you are able to put together a fix yourself, can demonstrate that the fix works, and make a pull request, I will gladly merge your changes. However, I no...

It's been a long time since I've even had a chance to look at this. I haven't made a new build in forever, but it would be nice to use...

From [here](https://github.com/halorgium/scribe-install/blob/2f1c5c3f41d78ce1184dc398fc8434e26c1d6501/boost/boost-1.42.0-r1.ebuild), A couple of things to account for: * different prefixes * '' * '/' * '@rpath/' * embedded dylib versions * libfoo.0.1.2.dylib To correct the "soname": ``` install_name_tool...

There are two opportunities for us to do this: 1. upon install 2. every time the program starts ~~We can, of course, also do both.~~ We MUST do both. The...

Hmm... so as it turns out, it's really freaking complicated to build huge projects like this for Mac OS X. The "legacy" method of linking code on mac is by...

I would really be interested in following some tutorials about how complex projects are organized in terms of .app, .framework, .dylib, @loader_path, @rpath, and @executable_path, etc

Possibly, the whole thing is caused by Apple's SIP (System Integrity Protection) explicitly disallowing the use of "relative paths" in applications. I assume it means install names like libfoo.dylib without...

My plan of attack here is roughly the following: 1. identify all changes that hard-code library-names into .dylibs 1. rather than using hard-coded library names, use @loader_path 1. this will...

This could come in handy. https://opensource.apple.com/source/cctools/cctools-576/misc/install_name_tool.c I'm currently writing a tool to fix broken dylibs in bash, but it's likely a much better idea to do it in C or...