dylibbundler
brew install dylibbundler
v1.0.5
MIT
Utility to bundle libraries into executables for macOS
889
30-day installs · #1361
1.8k
90-day · #1663
3.0k
365-day · #2405
611
★ GitHub stars · updated 2y ago
Links
- https://github.com/auriamg/macdylibbundler
- GitHub: auriamg/macdylibbundler
- Brew formula source: Formula/d/dylibbundler.rb
Raw metadata
{
"aliases": [],
"alternatives": [],
"build_dependencies": [],
"categories": [],
"caveats": null,
"conflicts_with": [],
"dependencies": [],
"deprecated": 0,
"deprecation_reason": null,
"desc": "Utility to bundle libraries into executables for macOS",
"disable_reason": null,
"disabled": 0,
"enrichment_fetched_at": "2026-06-20T23:37:12+00:00",
"first_seen": "2026-06-20T23:34:18+00:00",
"full_name": "dylibbundler",
"github_default_branch": "master",
"github_last_commit_at": "2024-02-21T15:32:59Z",
"github_readme_excerpt": "[](https://travis-ci.org/auriamg/macdylibbundler)\n\nmac dylib bundler\n================\n\n\nAbout\n-----\n\nMac OS X introduced an innovative and very useful way to package applications : app bundles.\nWhile their design has all that is needed to ease distribution of resources and frameworks, it\nseems like dynamic libraries (.dylib) are very complicated to distribute. Sure, applications developed\nspecifically for OS X won\u0027t make use of them, however applications ported from Linux or other Unices may have\ndependencies that will only compile as dylibs. By default, there exists no mechanism to bundle them but some command-line utilities provided by Apple - however it turns out that for a single program it is often necessary to issue dozens of commands! This often leads each porter to develop their own \"home solution\" wich are often hacky, poorly portable and/or non-optimal.\n\n**dylibbundler** is a small command-line programs that aims to make bundling .dylibs as easy as possible.\nIt automatically determines which dylibs are needed by your program, copies these libraries inside the app bundle, and fixes both them and the executable to be ready for distribution... all this with a single command on the terminal! It will also work if your program uses plug-ins that have dependencies too.\n\nIt usually involves 2 actions :\n* Creating a directory (by default called *libs*) that can be placed inside the *Contents* folder of the app bundle.\n* Fixing the executable file so that it is aware of the new location of its dependencies.\n\n\n\n\nInstallation\n------------\nIn the terminal, cd to the main directory of dylibbundler and type ```make```. You can install with ```sudo make install```.\n\n**Install with MacPorts**\n\n```sudo port install dylibbundler```\n\n**Install with Brew**\n\n```brew install dylibbundler```\n\n\nFeedback / Contact\n------------------\nYou can contact me here on github, for instance by creating a ticket or",
"github_repo": "auriamg/macdylibbundler",
"github_stars": 611,
"github_topics": [],
"homepage": "https://github.com/auriamg/macdylibbundler",
"homepage_og_description": null,
"homepage_og_image": null,
"homepage_title": null,
"installs_30d": 889,
"installs_365d": 3026,
"installs_90d": 1839,
"keg_only": 0,
"keg_only_reason": null,
"last_seen": "2026-06-20T23:34:18+00:00",
"license": "MIT",
"llm_generated_at": null,
"llm_model": null,
"name": "dylibbundler",
"oldnames": [],
"one_liner": null,
"optional_dependencies": [],
"rank_30d": 1361,
"rank_365d": 2405,
"rank_90d": 1663,
"raw_hash": "169de2399c0f4dc2",
"recommended_dependencies": [],
"revision": 0,
"ruby_source_path": "Formula/d/dylibbundler.rb",
"tap": "homebrew/core",
"test_dependencies": [],
"uses_from_macos": [],
"version_head": "HEAD",
"version_stable": "1.0.5",
"versioned_formulae": [],
"why_use_this": null
}