Package Details: cquery v20180718-8

Git Clone URL: https://aur.archlinux.org/cquery.git (read-only)
Package Base: cquery
Description: cquery is a highly-scalable, low-latency language server for C/C++/Objective-C.
Upstream URL: https://github.com/cquery-project/cquery/
Keywords: c c++ language-server lsp
Licenses: MIT
Conflicts: cquery-git
Submitter: SilverRainZ
Maintainer: SilverRainZ (MaskRay, lilac)
Last Packager: lilac
Votes: 10
Popularity: 0.403882
First Submitted: 2018-01-28 05:06
Last Updated: 2019-01-03 17:28

Latest Comments

1 2 Next › Last »

matzy commented on 2018-10-10 19:51

Got it - thanks. Sorry for the dumb question, new to this

Morganamilo commented on 2018-10-10 19:37

Links are made at build time. All you have to do is rebuild the package yourself.

matzy commented on 2018-10-10 19:35

So this package is looking for libclang.so.6, but the official repos upgraded to clang v7, so the library is now libclang.so.7. Is an update available from cquery that points to the new clang lib file, or is there a way to fix it in the meantime? (new to arch and this whole process or I would offer to fix it myself, sorry)

lucc commented on 2018-10-01 05:15

Maybe I was not clear. I know that you use the tar ball. I know that the git submodules are not in the tar ball. I suggest to use packages from the arch repos instead of some of the sources from the PKGBUILD. More specifically I suggest something like this diff:

diff --git a/PKGBUILD b/PKGBUILD
index a17aa73..e4b2f2b 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,25 +3,21 @@
 pkgname=cquery
 pkgver=v20180718
 __pkgver=${pkgver:1}
-pkgrel=6
+pkgrel=7
 pkgdesc='cquery is a highly-scalable, low-latency language server for C/C++/Objective-C.'
 arch=('x86_64')
 url='https://github.com/cquery-project/cquery/'
 license=('MIT')
-depends=('clang>=6.0.0')
+depends=('clang>=6.0.0' rapidjson msgpack-c)
 makedepends=('git' 'cmake>=3.1')
 conflicts=('cquery-git')
 source=("https://github.com/cquery-project/$pkgname/archive/$pkgver.tar.gz"
-        'git+https://github.com/miloyip/rapidjson#commit=daabb88'
         'git+https://github.com/onqtam/doctest#commit=b40b7e7'
         'git+https://github.com/greg7mdp/sparsepp#commit=1ca7189'
         'git+https://github.com/emilk/loguru#commit=6bf94c5'
-        'git+https://github.com/msgpack/msgpack-c#commit=208595b'
         'git+https://github.com/zeux/pugixml#commit=24a7064'
         )
 sha256sums=('72361e5e6f7a4a6b5ae27d555354efb4b012d20798b50ddd19cfd81bdf56cc1c'
-            'SKIP'
-            'SKIP'
             'SKIP'
             'SKIP'
             'SKIP'
@@ -29,11 +25,9 @@ sha256sums=('72361e5e6f7a4a6b5ae27d555354efb4b012d20798b50ddd19cfd81bdf56cc1c'

 prepare() {
     cd $pkgname-$__pkgver
-    cp -r -u $srcdir/rapidjson third_party
     cp -r -u $srcdir/doctest third_party
     cp -r -u $srcdir/sparsepp third_party
     cp -r -u $srcdir/loguru third_party
-    cp -r -u $srcdir/msgpack-c third_party
     cp -r -u $srcdir/pugixml third_party
 }
 build() {

I can build and install that and even run the executable afterwards. I did not test this with an editor yet as I am not working on any C project recently.

SilverRainZ commented on 2018-09-29 14:45

@lucc, I had said about this here.

Source of this package is a tarball of cquery release, there are not third_party code in it because these code are referenced as git submodudle -- and the tarball does not contains a git repo.

lucc commented on 2018-09-29 13:51

Is there a reason why you do not use the packages rapidjson, msgpack-c or pugixml from the repos?

I was able to build cquery with the rapidjson and msgpack-c from the repo instead of the custom download from the PKGBUILD. I only started the cquery executable on the command line and did no extensive testing but that worked. My first attempt to build with pugixml from the repo failed but maybe I missed something that I had to change in the PKGBUILD.

SilverRainZ commented on 2018-09-08 13:01

@Morganamilo Yes indeed, thank you for pointing out.

Morganamilo commented on 2018-09-08 01:05

Fragments are meant to be preceded with # not ?. The ? is actually for something totally different. This means that this package always pulls from master, not a specific commit.

SilverRainZ commented on 2018-09-01 16:00

@sum01, sorry for so late and thanks for your patch. it will be updated via @lilac immediately.

sum01 commented on 2018-08-24 21:58

So is this going to be moved to using Cmake soon? I'm sure I'm not the only one with a failing build process.