process gic 頭文件 anti fig filename comm .mm connect

轉自：Vim安裝YouCompleteMe插件。

安裝前的準備

1.首先必須要保證Vim的版本至少是7.3584，並且支持python2腳本。

在vim中輸入:version 來查看版本，如果版本低於7.3.584，那麽就需要重裝vim。 直接在終端中輸入python就可查看自己的python版本號。

2.安裝vundle插件

首先保證在用戶目錄下有.vim文件夾和.vimrc文件，沒有就新建。

[cpp] view plain copy print?

1. <span style="font-size:18px;">cd
2. mkdir .vim
3. vim .vimrc</span>

安裝git

Ubuntu下直接輸入以下代碼即可： [cpp] view plain copy print?

1. <span style="font-size:18px;">sudo apt-get install git</span>

使用如下命令，查看git版本 [cpp] view plain copy print?

1. <span style="font-size:18px;">git --version</span>

若終端裏輸出版本信息則說明安裝成功。

使用git安裝Vundle

[cpp] view plain copy

print?

1. <span style="font-size:18px;">$ git clone https://github.com/VundleVim/Vundle.vim.git ~/.vim/bundle/Vundle.vim</span>

修改配置文件

以下是官方配置文件，根據修改即可。 [cpp] view plain copy print?

1. <span style="font-size:18px;">set nocompatible " be iMproved, required
2. filetype off " required
4. " set the runtime path to include Vundle and initialize
5. set rtp+=~/.vim/bundle/Vundle.vim
6. call vundle#begin()
7. " alternatively, pass a path where Vundle should install plugins
8. "call vundle#begin(‘~/some/path/here‘)
10. " let Vundle manage Vundle, required
11. Plugin ‘VundleVim/Vundle.vim‘
13. " The following are examples of different formats supported.
14. " Keep Plugin commands between vundle#begin/end.
15. " plugin on GitHub repo
16. Plugin ‘tpope/vim-fugitive‘
17. " plugin from http://vim-scripts.org/vim/scripts.html
18. Plugin ‘L9‘
19. " Git plugin not hosted on GitHub
20. Plugin ‘git://git.wincent.com/command-t.git‘
21. " git repos on your local machine (i.e. when working on your own plugin)
22. Plugin ‘file:///home/gmarik/path/to/plugin‘
23. " The sparkup vim script is in a subdirectory of this repo called vim.
24. " Pass the path to set the runtimepath properly.
25. Plugin ‘rstacruz/sparkup‘, {‘rtp‘: ‘vim/‘}
26. " Install L9 and avoid a Naming conflict if you‘ve already installed a
27. " different version somewhere else.
28. Plugin ‘ascenator/L9‘, {‘name‘: ‘newL9‘}
30. " All of your Plugins must be added before the following line
31. call vundle#end() " required
32. filetype plugin indent on " required
33. " To ignore plugin indent changes, instead use:
34. "filetype plugin on
35. "
36. " Brief help
37. " :PluginList - lists configured plugins
38. " :PluginInstall - installs plugins; append `!` to update or just :PluginUpdate
39. " :PluginSearch foo - searches for foo; append `!` to refresh local cache
40. " :PluginClean - confirms removal of unused plugins; append `!` to auto-approve removal
41. "
42. " see :h vundle for more details or wiki for FAQ
43. " Put your non-Plugin stuff after this line</span>

下面是我的配置文件 [cpp] view plain copy print?

1. <span style="font-size:18px;">""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
3. set nocompatible " be iMproved, required
4. filetype off " required
5. "設置Vundle的運行路徑並初始化
6. set rtp+=~/.vim/bundle/Vundle.vim
7. call vundle#begin()
8. " Vundle安裝位置與插件路徑不同時，需要Vundle插件的路徑
9. "call vundle#begin(‘~/some/path/here‘)
10. "------------------要安裝的插件不能寫在此行前！------------------
12. "Vundle對自己的調用，不可刪去
13. Plugin ‘VundleVim/Vundle.vim‘
15. "以下是所支持的各種不同格式的示例
16. "需要安裝的插件應寫在調用的vundle#begin和vundle#end之間
18. "如果插件托管在Github上，寫在下方，只寫作者名/項目名就行了
20. Plugin ‘Valloric/YouCompleteMe‘
21. Plugin ‘majutsushi/tagbar‘
22. Plugin ‘vim-syntastic/syntastic‘
23. Plugin ‘vim-airline/vim-airline-themes‘
24. Plugin ‘vim-airline/vim-airline‘
26. "如果插件來自vim-scripts(官方)，寫插件名就行了
27. " Plugin ‘L9‘
29. "如果Git倉庫不在Github上，需要提供完整的鏈接
30. " Plugin ‘git://git.wincent.com/command-t.git‘
32. "本地的插件需要提供文件路徑
33. " Plugin ‘file:///home/gmarik/path/to/plugin‘
34. "一定要確保插件就在提供路徑的文件夾中(沒有子文件夾，直接在這層目錄下)
36. "運行時目錄的路徑
37. "Plugin ‘rstacruz/sparkup‘, {‘rtp‘: ‘vim/‘}
39. "避免插件間的命名沖突
40. "Plugin ‘ascenator/L9‘, {‘name‘: ‘newL9‘}
42. "------------------要安裝的插件不能寫在此行後！------------------
43. call vundle#end() " required
44. filetype plugin indent on " required
45. "要忽略插件縮進更改，請改用：
46. "filetype plugin on
47. "
48. " 安裝插件的相關指令
49. ":PluginList - 列出已安裝插件
50. ":PluginInstall - 安裝新添加的插件;添加`!`或使用`:PluginUpdate`來更新已安裝插件
51. ":PluginSearch xxx - 尋找名字帶有xxx的插件;添加`!`刷新本地緩存
52. ":PluginClean - 刪除已經從列表移除的插件;添加`!`靜默卸載
53. ":h - 幫助和說明文檔
54. "Vundle的設置到此為止了
55. "</span>

安裝完成之後在vim中執行 [cpp] view plain copy print?

1. :PluginInstall

等待安裝即可（安裝時間視網速而定完成後會有Done!提示）如圖所示：

安裝開始

1.Ubuntu快速安裝

下載完成後檢查倉庫的完整性

切換到YouCompleteMe目錄下，執行以下命令： [cpp] view plain copy print?

1. git submodule update --init --recursive

[cpp] view plain copy print?

1. <pre code_snippet_id="2320416" snippet_file_name="blog_20170408_8_6616764"></pre>
2. <pre></pre>
3. <pre></pre>
4. <pre></pre>

安裝編譯YouCompleteMe的必要插件

YouCompleteMe需要編譯之後才能使用所以接下來需要編譯 確保安裝Cmake，和一些Python頭文件，如果沒有安裝執行下面的語句 [cpp] view plain copy print?

1. sudo apt-get install build-essential cmake
2. sudo apt-get install python-dev python3-dev

不需要語義補全： [cpp] view plain copy print?

1. cd ~/.vim/bundle/YouCompleteMe
2. ./install.py

需要語義補全的： [cpp] view plain copy print?

1. cd ~/.vim/bundle/YouCompleteMe
2. ./install.py --clang-completer

過程有點漫長，期間可以看個電影放松一下。

配置YCM

打開.vimrc文件加上 [cpp] view plain copy print?

1. "YouCompleteMe 插件配置
2. let g:ycm_global_ycm_extra_conf=‘~/.vim/bundle/YouCompleteMe/third_party/ycmd/cpp/ycm/.ycm_extra_conf.py‘
3. nnoremap <leader>jd :YcmCompleter GoToDefinitionElseDeclaration<CR>
4. let g:ycm_python_binary_path = ‘/usr/bin/python3‘
5. nmap<C-a> :YcmCompleter FixIt<CR>

然後修改.ycm_extra_conf.py [cpp] view plain copy print?

1. vim .vim/bundle/YouCompleteMe/third_party/ycmd/cpp/ycm/.ycm_extra_conf.py

在這個文件中加入 [cpp] view plain copy print?

1. ‘-isystem‘,
2. ‘/usr/include‘,
3. ‘-isystem‘,
4. ‘/usr/include/c++/5.4.0‘,
5. ‘-isystem‘,
6. ‘/usr/include‘,
7. ‘/usr/include/x86_64-linux-gnu/c++‘,

註意以上的路徑都是自己的路徑，參照自己的路徑修改即可。
以下是我的配置文件 [cpp] view plain copy print?

1. # This file is NOT licensed under the GPLv3, which is the license for the rest
2. # of YouCompleteMe.
3. #
4. # Here‘s the license text for this file:
5. #
6. # This is free and unencumbered software released into the public domain.
7. #
8. # Anyone is free to copy, modify, publish, use, compile, sell, or
9. # distribute this software, either in source code form or as a compiled
10. # binary, for any purpose, commercial or non-commercial, and by any
11. # means.
12. #
13. # In jurisdictions that recognize copyright laws, the author or authors
14. # of this software dedicate any and all copyright interest in the
15. # software to the public domain. We make this dedication for the benefit
16. # of the public at large and to the detriment of our heirs and
17. # successors. We intend this dedication to be an overt act of
18. # relinquishment in perpetuity of all present and future rights to this
19. # software under copyright law.
20. #
21. # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
22. # EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
23. # MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
24. # IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR
25. # OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
26. # ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
27. # OTHER DEALINGS IN THE SOFTWARE.
28. #
29. # For more information, please refer to <http://unlicense.org/>
31. import os
32. import ycm_core
34. # These are the compilation flags that will be used in case there‘s no
35. # compilation database set (by default, one is not set).
36. # CHANGE THIS LIST OF FLAGS. YES, THIS IS THE DROID YOU HAVE BEEN LOOKING FOR.
37. flags = [
38. ‘-Wall‘,
39. ‘-Wextra‘,
40. ‘-Werror‘,
41. ‘-Wno-long-long‘,
42. ‘-Wno-variadic-macros‘,
43. ‘-fexceptions‘,
44. ‘-DNDEBUG‘,
45. # You 100% do NOT need -DUSE_CLANG_COMPLETER in your flags; only the YCM
46. # source code needs it.
47. ‘-DUSE_CLANG_COMPLETER‘,
48. # THIS IS IMPORTANT! Without a "-std=<something>" flag, clang won‘t know which
49. # language to use when compiling headers. So it will guess. Badly. So C++
50. # headers will be compiled as C headers. You don‘t want that so ALWAYS specify
51. # a "-std=<something>".
52. # For a C project, you would set this to something like ‘c99‘ instead of
53. # ‘c++11‘.
54. ‘-std=c++11‘,
55. # ...and the same thing goes for the magic -x option which specifies the
56. # language that the files to be compiled are written in. This is mostly
57. # relevant for c++ headers.
58. # For a C project, you would set this to ‘c‘ instead of ‘c++‘.
59. ‘-x‘,
60. ‘c++‘,
61. ‘-isystem‘,
62. ‘../BoostParts‘,
63. ‘-isystem‘,
64. # This path will only work on OS X, but extra paths that don‘t exist are not
65. # harmful
66. ‘/System/Library/Frameworks/Python.framework/Headers‘,
67. #‘-isystem‘,
68. #‘../llvm/include‘,
69. #‘-isystem‘,
70. #‘../llvm/tools/clang/include‘,
71. #‘-I‘,
72. #‘.‘,
73. #‘-I‘,
74. #‘./ClangCompleter‘,
75. #‘-isystem‘,
76. #‘./tests/gmock/gtest‘,
77. #‘-isystem‘,
78. #‘./tests/gmock/gtest/include‘,
79. #‘-isystem‘,
80. #‘./tests/gmock‘,
81. #‘-isystem‘,
82. #‘./tests/gmock/include‘,
83. ‘-isystem‘,
84. ‘/usr/include‘,
85. ‘-isystem‘,
86. ‘/usr/include/c++/5.4.0‘,
87. ‘-isystem‘,
88. ‘/usr/include‘,
89. ‘/usr/include/x86_64-linux-gnu/c++‘,
90. ]
93. # Set this to the absolute path to the folder (NOT the file!) containing the
94. # compile_commands.json file to use that instead of ‘flags‘. See here for
95. # more details: http://clang.llvm.org/docs/JSONCompilationDatabase.html
96. #
97. # You can get CMake to generate this file for you by adding:
98. # set( CMAKE_EXPORT_COMPILE_COMMANDS 1 )
99. # to your CMakeLists.txt file.
100. #
101. # Most projects will NOT need to set this to anything; you can just change the
102. # ‘flags‘ list of compilation flags. Notice that YCM itself uses that approach.
103. compilation_database_folder = ‘‘
105. if os.path.exists( compilation_database_folder ):
106. database = ycm_core.CompilationDatabase( compilation_database_folder )
107. else:
108. database = None
110. SOURCE_EXTENSIONS = [ ‘.cpp‘, ‘.cxx‘, ‘.cc‘, ‘.c‘, ‘.m‘, ‘.mm‘ ]
112. def DirectoryOfThisScript():
113. return os.path.dirname( os.path.abspath( __file__ ) )
116. def MakeRelativePathsInFlagsAbsolute( flags, working_directory ):
117. if not working_directory:
118. return list( flags )
119. new_flags = []
120. make_next_absolute = False
121. path_flags = [ ‘-isystem‘, ‘-I‘, ‘-iquote‘, ‘--sysroot=‘ ]
122. for flag in flags:
123. new_flag = flag
125. if make_next_absolute:
126. make_next_absolute = False
127. if not flag.startswith( ‘/‘ ):
128. new_flag = os.path.join( working_directory, flag )
130. for path_flag in path_flags:
131. if flag == path_flag:
132. make_next_absolute = True
133. break
135. if flag.startswith( path_flag ):
136. path = flag[ len( path_flag ): ]
137. new_flag = path_flag + os.path.join( working_directory, path )
138. break
140. if new_flag:
141. new_flags.append( new_flag )
142. return new_flags
145. def IsHeaderFile( filename ):
146. extension = os.path.splitext( filename )[ 1 ]
147. return extension in [ ‘.h‘, ‘.hxx‘, ‘.hpp‘, ‘.hh‘ ]
150. def GetCompilationInfoForFile( filename ):
151. # The compilation_commands.json file generated by CMake does not have entries
152. # for header files. So we do our best by asking the db for flags for a
153. # corresponding source file, if any. If one exists, the flags for that file
154. # should be good enough.
155. if IsHeaderFile( filename ):
156. basename = os.path.splitext( filename )[ 0 ]
157. for extension in SOURCE_EXTENSIONS:
158. replacement_file = basename + extension
159. if os.path.exists( replacement_file ):
160. compilation_info = database.GetCompilationInfoForFile(
161. replacement_file )
162. if compilation_info.compiler_flags_:
163. return compilation_info
164. return None
165. return database.GetCompilationInfoForFile( filename )
168. def FlagsForFile( filename, **kwargs ):
169. if database:
170. # Bear in mind that compilation_info.compiler_flags_ does NOT return a
171. # python list, but a "list-like" StringVec object
172. compilation_info = GetCompilationInfoForFile( filename )
173. if not compilation_info:
174. return None
176. final_flags = MakeRelativePathsInFlagsAbsolute(
177. compilation_info.compiler_flags_,
178. compilation_info.compiler_working_dir_ )
180. # NOTE: This is just for YouCompleteMe; it‘s highly likely that your project
181. # does NOT need to remove the stdlib flag. DO NOT USE THIS IN YOUR
182. # ycm_extra_conf IF YOU‘RE NOT 100% SURE YOU NEED IT.
183. try:
184. final_flags.remove( ‘-stdlib=libc++‘ )
185. except ValueError:
186. pass
187. else:
188. relative_to = DirectoryOfThisScript()
189. final_flags = MakeRelativePathsInFlagsAbsolute( flags, relative_to )
191. return { ‘flags‘: final_flags }

2.完全安裝

未完待續

結束

Vim-安裝 YouCompleteMe