Package Details: vim-youcompleteme-git r3216.0d855962-1

Git Clone URL: https://aur.archlinux.org/vim-youcompleteme-git.git (read-only, click to copy)
Package Base: vim-youcompleteme-git
Description: A code-completion engine for Vim
Upstream URL: https://ycm-core.github.io/YouCompleteMe/
Keywords: completion engine neovim vim ycm
Licenses: GPL3
Groups: vim-plugins
Submitter: thestinger
Maintainer: artafinde
Last Packager: artafinde
Votes: 170
Popularity: 0.46
First Submitted: 2013-02-05 21:32 (UTC)
Last Updated: 2024-08-19 15:53 (UTC)

Dependencies (19)

Required by (0)

Sources (2)

Pinned Comments

artafinde commented on 2021-04-10 13:03 (UTC)

If you want to use system's abseil set the _use_system_abseil to ON - default is to download from internet during build.

Latest Comments

« First ‹ Previous 1 .. 34 35 36 37 38 39 40 41 42 43 44 .. 53 Next › Last »

eberan commented on 2015-11-23 01:41 (UTC)

Fixed; 'requests' submodule was removed upstream because it was (already) in the 'ycmd' submodule.

eberan commented on 2015-11-19 01:40 (UTC)

@zsrkmyn it looks like that submodule has been removed, so the PKGBUILD needs updating. Unfortunately I am unable to change/test/upload a new script because of travel, anyone willing to do the changes feel free to post them here. Moving forward, I'm happy to add maintainers to this project to avoid delayed fixes like this, just let me know.

zsrkmyn commented on 2015-11-18 09:52 (UTC)

Sorry but it seems that I cannot build the package with this PKGBUILD. There may be something wrong there. ==> Starting package()... cp: cannot stat '/build/vim-youcompleteme-git/src/YouCompleteMe/third_party/requests': No such file or directory

eberan commented on 2015-11-09 02:01 (UTC)

Quick update to fix a typo in the packaging step; it missed pulling in clang_includes and libclang.

eberan commented on 2015-11-08 06:03 (UTC)

PKGBUILD has been updated. As the upstream maintainer signature has been added to the source list for verification, you will need to add his key. As @atweiden said: "Check http://llvm.org/releases/download.html#3.7.0 for the PGP sig (Hans Wennborg <hans@chromium.org> 0x0FC3042E345AD05D)." After verifying the correct key fingerprint, you can do something like this: gpg --recv-keys 0fc3042e345ad05d Also updated is the OmniSharp server, now being built as Release rather than Debug. Chime in if you have any issues!

atweiden commented on 2015-10-15 00:04 (UTC)

Yep. My vim packages are custom installed to the user's $HOME, so you should only use the parts that work. For starters: http://ix.io/lqp

eberan commented on 2015-10-14 01:43 (UTC)

@atweiden that looks pretty interesting! I think much of that code can be copied over, however I'm a little unsure about the packaging script. Am I right in understanding this is a user-specific package/installer (I guess that's how plugged works...)?

atweiden commented on 2015-10-12 01:33 (UTC)

To override YCM's own clang binary download on x86_64 with Pacman checking the sha256sums and PGP sigs, reverting to system libclang on non-x86_64 architectures, see: https://github.com/atweiden/pkgbuilds-plugged/blob/master/vim-youcompleteme-plugged-git/PKGBUILD Clang download vars were taken from: https://github.com/Valloric/ycmd/blob/master/cpp/ycm/CMakeLists.txt Check http://llvm.org/releases/download.html#3.7.0 for the PGP sig (Hans Wennborg <hans@chromium.org> 0x0FC3042E345AD05D).

eberan commented on 2015-10-07 18:39 (UTC)

@nivata Great! Thanks for the patch. I wonder if we should also include libclang.so as that is what is linked into the clang completer. We might get some more traction when asking for support upstream as well.

nivata commented on 2015-10-04 21:42 (UTC)

Well, so it seems that using the bundled version of clang works. For the record here is the modified PKGBUILD I used: https://gist.github.com/anonymous/5140dedc94896456c3fb Too bad it doesn't seem to work with the system clang library though. Maybe you can update the PKGBUILD to reflect this? This has been discussed before (bundled version of libclang.so vs using the system one), but since apparently using the system version doesn't work currently, this PKGBUILD should use the other option.