vim/YouCompleteMe
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Updating to latest ycmd

Browse Source
This commit is contained in:
Strahinja Val Markovic 2015-03-27 12:59:19 -07:00
parent 9bfdb98b0d
commit 2f81090206
2 changed files with 18 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -126,8 +126,9 @@ using Vundle and the ycm_support_libs library APIs have changed (happens
rarely), YCM will notify you to recompile it. You should then rerun the install rarely), YCM will notify you to recompile it. You should then rerun the install
process. process.
It's recommended that you have the latest Xcode installed along with the latest **NOTE:** If you want C-family completion, you MUST have the latest Xcode
Command Line Tools (that you install from within Xcode). installed along with the latest Command Line Tools (they are installed when you
start Xcode for the first time).
Install CMake. Preferably with [Homebrew][brew], but here's the [stand-alone Install CMake. Preferably with [Homebrew][brew], but here's the [stand-alone
CMake installer][cmake-download]. CMake installer][cmake-download].
@ -1928,12 +1929,15 @@ cases; if we find the request to be reasonable, we'll find a way to address it.
### Completion doesn't work with the C++ standard library headers ### Completion doesn't work with the C++ standard library headers
This is caused by an issue with libclang. Compiling from `clang` the binary uses This is caused by an issue with libclang that only affects some operating
the correct default header search paths but compiling from `libclang.so` does systems. Compiling with `clang` the binary will use the correct default header
not. The issue seems to impact some OS's more than others. It appears that OS X search paths but compiling with `libclang.so` (which YCM uses) does not.
Mavericks in particular has problems with this.
The current workaround is to call `echo | clang -v -E -x c++ -` and look at the Mac OS X is normally affected, but there's a workaround in YCM for that specific
OS. If you're not running that OS but still have the same problem, continue
reading.
The workaround is to call `echo | clang -v -E -x c++ -` and look at the
paths under the `#include <...> search starts here:` heading. You should take paths under the `#include <...> search starts here:` heading. You should take
those paths, prepend `-isystem` to each individual path and append them all to those paths, prepend `-isystem` to each individual path and append them all to
the list of flags you return from your `FlagsForFile` function in your the list of flags you return from your `FlagsForFile` function in your

2
third_party/ycmd vendored

@ -1 +1 @@
Subproject commit 03d18ea3daff24aefb412ef3c4d5681868ce7d84 Subproject commit 11edf122edcdfe03313aa57d50bc56521da1e226