1. 20 Jul, 2019 1 commit
    • Ben Wagner's avatar
      Add working directory to clang parser. · ad7ea392
      Ben Wagner authored
      This sets the working directory of the clang parser similarly to the way
      the build directory is passed to the builder. This allows the parser to
      correctly resolve any relative paths in the extra build arguments. This
      means relative paths are resolved relative to the build directory (as
      they would be resolved by a builder).
      Test Plan: In the current test setup it doesn't seem the TestProject allows a TestBuildSystemManager, so it seems like quite a bit of work to create a test for this. (As a result I assume IBuildSystemManager integration isn't well tested in general right now.) If this needs a test, let me know if adding a TestBuildSystemManager is the right way to go.
      Reviewers: #kdevelop, aaronpuchert
      Reviewed By: aaronpuchert
      Subscribers: aaronpuchert, kdevelop-devel
      Tags: #kdevelop
      Differential Revision: https://phabricator.kde.org/D22197
  2. 19 Jul, 2019 1 commit
  3. 16 Jul, 2019 1 commit
  4. 04 Jul, 2019 2 commits
  5. 03 Jul, 2019 1 commit
  6. 21 Jun, 2019 1 commit
  7. 17 Jun, 2019 1 commit
  8. 16 Jun, 2019 1 commit
  9. 29 May, 2019 1 commit
  10. 25 May, 2019 2 commits
  11. 20 May, 2019 2 commits
  12. 06 May, 2019 2 commits
  13. 01 May, 2019 1 commit
  14. 23 Apr, 2019 1 commit
  15. 14 Apr, 2019 4 commits
    • Milian Wolff's avatar
      Also find clang include path based on runtime libclang library path · bc13f955
      Milian Wolff authored
      My KDevelop was compiled against my system libclang v7.0.1, thus
      KDEV_CLANG_BUILTIN_DIR points to /usr/lib/clang/7.0.1/include. Now
      I compiled clang 8 from sources and put it in a different folder
      in my home path and adapted LD_LIBRARY_PATH to make KDevelop pick it
      up. This then fails to find the builtin include path, since it tries
      to find `/usr/lib/clang/8.0.1/include` which doesn't exit.
      This patch adds another fallback to fix the above scneario: We now
      lookup the path of libclang at runtime through dlfcn.h's dladdr,
      which we pass a libclang function address, here clang_getClangVersion.
      Then on success we deduce the include path by removing the library
      name and then instead appending `clang/$version/include`, which makes
      it use /home/milian/projects/compiled/other/lib/clang/8.0.1/include
      as required.
    • Milian Wolff's avatar
      clang: add new (partially failing) test file for lambdas · c88bf19b
      Milian Wolff authored
      We apparently fail to build uses for lambda captures using
      C++14 `identifier initializer` statements. Turns out that the
      init-capture isn't visited by libclang, see also:
    • Milian Wolff's avatar
      Simplify setting custom parser args for unit tests · d8119c13
      Milian Wolff authored
      Make it possible to add parser args from a background provider and
      share the test provider implementation.
    • Milian Wolff's avatar
      clang: fix functions.cpp test · bbb42a2f
      Milian Wolff authored
      Potentially this got fixed/changed by a newer clang version
  16. 10 Apr, 2019 1 commit
  17. 25 Mar, 2019 2 commits
  18. 19 Mar, 2019 1 commit
  19. 08 Mar, 2019 1 commit
  20. 15 Feb, 2019 3 commits
    • Milian Wolff's avatar
      tie DUContext::createNavigationWidget to AbstractNavigationWidget · d9b4c14c
      Milian Wolff authored
      We always return instances of this type anyways, so enforce it in
      the API and simplify the usage code accordingly.
    • Milian Wolff's avatar
      cleanup: remove html prefix/suffix feature from navigation widget · 12e3583f
      Milian Wolff authored
      This was *only* being used by the project file quickopen feature,
      and you only saw it when clicking into the quickopen list, or when
      pressing alt. I doubt anyone ever did that. And it was madness
      anyways: we decreased the font size in a hacky non-html compliant
      way which actually made it quite hard to read for me. So the only
      thing we lose is the project name... which is an acceptable
      tradeoff. This feature messed up the whole API considerably, removing
      it makes me very happy.
      We can bring back the project name in the future by introducing a
      generic wrapper-widget that supports the
    • Milian Wolff's avatar
      Remove dead code: AbstractNavigationContext::fontSize{Prefix,Suffix} · 518e7871
      Milian Wolff authored
      These functions never return any non-null string, so just remove them.
  21. 13 Feb, 2019 2 commits
  22. 10 Feb, 2019 1 commit
    • Thomas Schöps's avatar
      Clang CodeCompletion: No auto-completion for numbers · e86c5a72
      Thomas Schöps authored
      Summary: When typing a number, code-completion is undesirable in my opinion, since most likely no completion item applies and it only distracts, obstructs the view, or is triggered accidentally. Thus, this patch prevents code completion from automatically getting triggered for numbers. It does not cover all cases (code completion will still show something for floating-point numbers that start with a dot, such as .1f) but should cover the most common cases. Manual completion with Ctrl+Space is still possible.
      Test Plan: Tested manually.
      Reviewers: #kdevelop, mwolff
      Reviewed By: #kdevelop, mwolff
      Subscribers: mwolff, brauch, kdevelop-devel
      Tags: #kdevelop
      Differential Revision: https://phabricator.kde.org/D17915
  23. 07 Feb, 2019 1 commit
  24. 04 Feb, 2019 1 commit
  25. 02 Feb, 2019 1 commit
  26. 01 Feb, 2019 2 commits
  27. 26 Jan, 2019 2 commits