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.51
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 .. 42 43 44 45 46 47 48 49 50 51 52 53 Next › Last »

axper commented on 2014-06-13 07:07 (UTC)

@mikezackles Done, thanks!

mikezackles commented on 2014-06-12 22:23 (UTC)

So (I think) the CMake find_library stuff for ycmd_core somehow ends up searching PATH to find libclang.so before it looks in more appropriate places. This is a problem for people who have android-sdk installed from AUR, which adds the build_tools directory to PATH, which also contains libclang.so. This seems like an upstream issue, but for now an easy workaround is to just specify the path to libclang.so explicitly as done in the updated PKGBUILD here: https://gist.github.com/mikezackles/e8af75a1cc69aa3390ea Apologies if I'm somehow mistaken, and thanks for maintaining!

axper commented on 2014-05-21 14:35 (UTC)

@z33ky I think the best approach would be to split into several packages rather than variablies. This one (vim-youcompleteme-git) will have all the completion engines. You can create new packages like vim-youcompleteme-clang-jedi-git which will have only clang and jedi, etc.

z33ky commented on 2014-05-21 10:38 (UTC)

http://pastebin.com/0GZCthyj This includes the clang completer and the OmniSharp completer with the YCM package, but they are optional and you can toggle them with the first two variables in the PKGBUILD. It also cuts some of the sources in favor of simple dependencies - python-frozendict is an exception, because no such package exists yet, so it is also included in the YCM package. I tested the omni (not OmniSharp) completer, the clang completer and the jedi completer (now also an optional dependency). Also the LTO build (with gcc 4.9) is corrupt, so build without LTO. I also didn't increase the pkgrel yet, so if you upload this PKGBUILD as-is you should probably do that.

z33ky commented on 2014-05-19 20:04 (UTC)

I'll try in the next few days and see what I can accomplish. I could take over the maintenance of this package, but I only use the non-semantic and clang completion engines. Perhaps this package should be split into entirely different packages for the completion engines, if it is possible to build, install and maintain them separately. If I succeed I shall test with YCM and the clang-completion engine, perhaps someone will step up and test with jedi and OmniSharp.

axper commented on 2014-05-19 13:48 (UTC)

@z33ky Write a pkgbuild with your proposals and I'll merge it. Alternatively I can disown the package and you can do it yourself.

z33ky commented on 2014-05-18 21:49 (UTC)

I think there are still some unnecessary files in this version of the package. I've put up a list of files in my previous package, before the split into YouComleteMe & ycmd, up here for reference: http://pastebin.com/4UK4Z9iF Some things I am spotting: test directories - I presume these are not actually useful at run-time libclang.so - aren't we explicitly linking against system clang? (And semantic completion indeed still works on my system when I remove /usr/share/vim/vimfiles/third_party/ycmd/libclang.so.) Partially these are also just new dependencies, such as waitress (I believe). There are also some dependencies, such as jedi, that could be optdepends instead. Perhaps it's more prone to breakage if the YCM submodules get out of sync with the system packages. A split-package with vim-youcompleteme-$COMPLETIONENGINE-git might work. Otherwise, having a few variables at the top of the PKGBUILD to easily toggle their installation would be pleasant. You might not even need to checkout the submodules that you don't want to install if they're not actually part of the YCM build but are just checked out for installing/packaging.

axper commented on 2014-05-18 20:50 (UTC)

@z33ky Thanks for report. I removed the cpp directory and bunch of files/dirs from OmniSharp. The .pkg.tar.xz file now on my system is 6.8M.

z33ky commented on 2014-05-18 13:49 (UTC)

I'm pretty sure the package() function copies too many files. For one, the whole source code of ycmd gets packaged, but even after taking out these ~28MB the package gets ~19MB larger than before.

axper commented on 2014-05-17 20:29 (UTC)

Updated, thank you all!

« First ‹ Previous 1 .. 42 43 44 45 46 47 48 49 50 51 52 53 Next › Last »