diff options
| author | auriamg <auria.mg@gmail.com> | 2014-05-30 04:23:49 +0400 |
|---|---|---|
| committer | auriamg <auria.mg@gmail.com> | 2014-05-30 04:23:49 +0400 |
| commit | dc1c1ee30cd6caf61fee7458dd5be849a11c51ce (patch) | |
| tree | 520e8a1d8f7c31b9f77a1a1fc940d44d21c00e65 | |
| parent | db9c8917a9dbea05384efb22f9bb2826caf58f7e (diff) | |
Update README.md
| -rw-r--r-- | README.md | 21 |
1 files changed, 9 insertions, 12 deletions
@@ -52,30 +52,27 @@ fixes dependencies where bundled libraries depend on each other. If this option </blockquote> `-i`, `--ignore` (path) -<blockquote> -Dylibs in (path) will be ignored. By default, dylibbundler will ignore libraries installed in /usr/lib since they are assumed to be present by default on all OS X installations.*(It is usually recommend not to install additional stuff in `/usr/`, always use ` /usr/local/` or another prefix to avoid confusion between system libs and libs you added yourself)* -</blockquote> +> Dylibs in (path) will be ignored. By default, dylibbundler will ignore libraries installed in `/usr/lib` since they are assumed to be present by default on all OS X installations.*(It is usually recommend not to install additional stuff in `/usr/`, always use ` /usr/local/` or another prefix to avoid confusion between system libs and libs you added yourself)* + `-d`, `--dest-dir` (directory) -<blockquote> -Sets the name of the directory in wich distribution-ready dylibs will be placed, relative to the current working directory. (Default is `./libs`) For an app bundle, it is often conveniant to set it to something like `./MyApp.app/Contents/libs`. -</blockquote> +> Sets the name of the directory in wich distribution-ready dylibs will be placed, relative to the current working directory. (Default is `./libs`) For an app bundle, it is often conveniant to set it to something like `./MyApp.app/Contents/libs`. + `-p`, `--install-path` (libraries install path) -<blockquote>Sets the "inner" installation path of libraries, usually inside the bundle and relative to executable. (Default is `@executable_path/../libs/`, -which points to a directory named `libs` inside the `Contents` directory of the bundle.) -</blockquote> +> Sets the "inner" installation path of libraries, usually inside the bundle and relative to executable. (Default is `@executable_path/../libs/`, which points to a directory named `libs` inside the `Contents` directory of the bundle.) + *The difference between `-d` and `-p` is that `-d` is the location dylibbundler will put files at, while `-p` is the location where the libraries will be expected to be found when you launch the app. Both are often related.* `-of`, `--overwrite-files` -<blockquote>When copying libraries to the output directory, allow overwriting files when one with the same name already exists.</blockquote> +> When copying libraries to the output directory, allow overwriting files when one with the same name already exists. `-od`, `--overwrite-dir` -<blockquote>If the output directory already exists, completely erase its current content before adding anything to it. (This option implies --create-dir)</blockquote> +> If the output directory already exists, completely erase its current content before adding anything to it. (This option implies --create-dir) `-cd`, `--create-dir` -<blockquote>If the output directory does not exist, create it.</blockquote> +> If the output directory does not exist, create it. A command may look like `% dylibbundler -od -b -x ./HelloWorld.app/Contents/MacOS/helloworld -d ./HelloWorld.app/Contents/libs/` |