Skip to content

Commit 8c67148

Browse files
committed
doc: add brew install tip
1 parent d44a5b8 commit 8c67148

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

Readme.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,10 @@ or
1818

1919
`git clone "https://github.com/SolaWing/xcode-build-server.git" && ln -s "$PWD"/xcode-build-server/xcode-build-server /usr/local/bin`
2020

21+
or install from brew
22+
23+
`brew install xcode-build-server`
24+
2125
# Usage
2226

2327
choose one of the following usage. No matter which method you use, you need to ensure that the directory where `buildServer.json` is located is **the root directory** of lsp
@@ -54,12 +58,13 @@ xcode-build-server parse [-a] <build_log_file>
5458
this will parse the log, save compile info in a `.compile` file, and update `buildServer.json` with a `kind: manual` key to instruct `xcode-build-server` to use the flags from the `.compile` file.
5559

5660

57-
`<build_log_file>` can be created by redirecting `xcodebuild build` output to a file, or exported from xcode's build log.
61+
`<build_log_file>` can be created by redirecting `xcodebuild build` output to a file, or exported from xcode's build log UI.
5862

5963
`<cmd generate build log>` will usually be xcodebuild, or `pbpaste` if copy from xcode's build log. for example:
6064

6165
```base
6266
xcodebuild -workspace *.xcworkspace -scheme <XXX> -configuration Debug build | xcode-build-server parse [-a]
67+
6368
pbpaste | xcode-build-server parse [-a]
6469
```
6570

@@ -94,4 +99,4 @@ current implementation is basicly work, but may have some rough edges. Please re
9499
## Release new version
95100
1. Create a new tag with `git tag -a v0.1.0 -m "release 0.1.0"`
96101
2. Push tag with `git push origin v0.1.0`
97-
3. GitHub action will create release
102+
3. GitHub action will create release

0 commit comments

Comments
 (0)