- 29 Sep, 2017 2 commits
-
-
Kevin Funk authored
Summary: Use kdevelop.plugins.$PLUGINNAME Reviewers: mwolff, brauch Reviewed By: mwolff, brauch Subscribers: brauch, kdevelop-devel Differential Revision: https://phabricator.kde.org/D8045
-
Friedrich W. H. Kossebau authored
Reviewers: #kdevelop, mwolff Reviewed By: #kdevelop, mwolff Subscribers: mwolff, kdevelop-devel Differential Revision: https://phabricator.kde.org/D8041
-
- 28 Sep, 2017 9 commits
-
-
Kevin Funk authored
In the form $MAJOR.$MINOR -- this needs to be bumped each minor version bump, where we allow ABI breaks
-
René J.V. Bertin authored
This adds a failsafe and generates a warning for a situation that should never happen. A spin-off of patch review D7995 on phabricator.
-
Kevin Funk authored
-
Kevin Funk authored
-
Kevin Funk authored
Use seconds instead of minutes as unit. Make sure we fetch news only once per day instead of every 24 minutes...
-
Kevin Funk authored
-
Kevin Funk authored
That thing is keeping only thing busy: my CPU I don't really understand what's causing it, but kdevelop/kwin_x11 are constantly using 10-15% CPU each even if the busy indicator is not shown here. Prerequisites that exhibit the issue: - Welcome page is visible - Busy indicator was shown at least once - Have an Intel GPU(?) This all looks very similar to this bug here: https://bugreports.qt.io/browse/QTBUG-50700 Perf shows lots of time spent in QPlatformBackingStore::composeAndFlush()
-
Friedrich W. H. Kossebau authored
Summary: For more consistent look and saving a few vertical pixels with common styles Also: * drop IDEAL_LAYOUT_MARGIN and use 0 directly as elsewhere, no use for keeping this a separate #define * for bottom button bar with right corner widget, use normal style spacing between corner widget and buttons Reviewers: #kdevelop, apol Reviewed By: #kdevelop, apol Subscribers: apol, kdevelop-devel Differential Revision: https://phabricator.kde.org/D8035
-
Sven Brauch authored
BUG:385110
-
- 25 Sep, 2017 3 commits
-
-
Friedrich W. H. Kossebau authored
-
Document how to determine which optional dependencies are used (e.g. QtWebKit instead of QtWebEngine Summary: As long as QtWebKit remains a supported option for documentation rendering users might want an option to build KDevelop against that library even if QWE is present on their system. KDevelop uses enough resources of its own, so an option to avoid using the additional resource-hungry QWE is very welcome (after all, many will probably already have a chrome-based browser running). This patch is the simplest possible implementation, and doesn't advertise itself by creating an option variable in the toplevel CMake file. I'd be happy to add that possibility though. Test Plan: It would be nice if CMake's summary printed a list of optional dependencies that were disabled explicitly. Reviewers: #kdevelop, apol, kfunk Reviewed By: #kdevelop, kfunk Subscribers: kfunk, apol, kdevelop-devel Tags: #kdevelop Differential Revision: https://phabricator.kde.org/D7950
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-
- 24 Sep, 2017 3 commits
-
-
Summary: - context menu was owned by widget that is to be deleted BUG: 384828, 384977 Test Plan: - close dock widget by context menu from widget title -> no longer crashes Reviewers: #kdevelop, apol Reviewed By: #kdevelop, apol Subscribers: kdevelop-devel Differential Revision: https://phabricator.kde.org/D7947 (cherry picked from commit 16abb2d7)
-
Summary: - raise of output view is suppressed for jobs from history - only search parameters are displayed, actual search can be redone with "Refresh" - population of list is still deferred until all projects are loaded to ensure correct display of search description BUG: 384899 Test Plan: - on restart no search is performed, but can be triggered by "Refresh" - output view stays closed on startup Reviewers: #kdevelop, brauch Reviewed By: #kdevelop, brauch Subscribers: brauch, kdevelop-devel Differential Revision: https://phabricator.kde.org/D7945 (cherry picked from commit b9904391)
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-
- 23 Sep, 2017 2 commits
-
-
Pino Toscano authored
GIT_SILENT
-
Sven Brauch authored
-
- 21 Sep, 2017 4 commits
-
-
Francis Herne authored
Fixes compilation after f149bed1
-
GCC reports the following two defines as built-in: There are no definitions of __has_include{,_next}__ available in clang though, leading to parse errors like: 2 problems encountered: "Function-like macro '__has_include__' is not defined" "" [ (1, 12) -> (1, 25) ] "Broken c++11 setup (__has_include)" "" [ (4, 9) -> (4, 14) ] This then propagates to all kinds of issues, most notably when parsing Qt headers. There, we suddenly fail to realize that the compiler is C++11 capable (__has_include(<atomic>) errors out), and more. Overall, the language parser is suddenly completely broken. We now catch these two function macros and skip them, to ensure they never override the builtin functionality of clang. This fixes the new unit test and also makes KDevelop behave properly again with newer Clang when parsing Qt 5 code bases. The question now is: Why do we use GCC by default to find the built-in defines? I thought we'd default to Clang since a long time by now... (cherry picked from commit ea3cb5a8)
-
We need to jump through some hoops here, since it's not easy to rewind the temporary file itself to have it output its contents. So instead, close the file and reopen it separate to read the contents. (cherry picked from commit bbc57107)
-
Commit 65106bec introduced this regression: The code used to return early when a compiler was found. The new loop to cache the result always iterates over all compilers. Essentially, this reverts the whole logic within the IDM: Instead of prefering, say, Clang over GCC, it actually does the opposite and will prefer GCC over Clang. This patch adds the missing break to restore the old behavior. This ensures we will once again use Clang instead of GCC by default for includes and built-in defines. As exemplified by the recent breakage (__has_include) when using GCC, and the history of the shaky GCC integration, this is important for a good default impression of KDevelop. (cherry picked from commit f6e3d8b9)
-
- 20 Sep, 2017 5 commits
-
-
René J.V. Bertin authored
-
Aleix Pol Gonzalez authored
We ended up with two approaches to the same problem.
-
-
Summary: The expression intended for catching CMakeMultiline errors e.g.: CMake Error: Error in cmake code at /some/path with spaces/to/a/project/CMakeLists.txt:10: Where the regex would hit on the second line. Now it also hits on lines such as this: CMake Error at SecondSubDir/CMakeLists.txt:1: Which means that the filename is extracted wrong and the user will be sent to a new file instead of the file with the error. Changed the regex in question and added a unittest that catches this scenario. Reviewed By: kfunk Subscribers: volden, kfunk, kdevelop-devel Differential Revision: https://phabricator.kde.org/D7554
-
Summary: Arguments from project option were not applied or applied incorrectly since D7752. This patch fixes sime problem when setting custom arguments to the parser. Also, since we take arguments from the build system, warning as error became effective on the parser. I added Wno-error at the end of the default parser arguments. Reviewers: #kdevelop, kfunk, apol Reviewed By: #kdevelop, kfunk Subscribers: mwolff, brauch, kdevelop-devel Differential Revision: https://phabricator.kde.org/D7876
-
- 19 Sep, 2017 1 commit
-
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-
- 18 Sep, 2017 6 commits
-
-
René J.V. Bertin authored
This reverts the functionality dropped by b9a74648 while maintaining the kdevelop-wide cmake executable selection introduced by that commit. The per-project setting is stored using the preferred "CMake Executable" key, with support for the old key for backwards compatibility. Differential Revision: https://phabricator.kde.org/D7865
-
(cherry picked from commit 0ed5d401)
-
"unsafe mix of type 'const bool' and type 'int' in operation" (cherry picked from commit e3600594)
-
Undefined reference to "bool SetNodeDataRequest::equals(const SetNodeData* item) const;" (cherry picked from commit fdaf9758)
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-
Francis Herne authored
Read status from the cmakeserver progress output. This avoids a spam of "unhandled message" warnings to the terminal. Not using setProgressAmount, because 'progressMaximum' seems to always be 1000 and none of the KJob::Unit options make sense. Differential Revision: https://phabricator.kde.org/D7866
-
- 15 Sep, 2017 2 commits
-
-
Sven Brauch authored
The old code pretends to filter some prefixes out, but ends up adding in everything (even multiple times) CCMAIL:aleixpol@kde.org
-
Sven Brauch authored
-
- 14 Sep, 2017 3 commits
-
-
Friedrich W. H. Kossebau authored
-
Summary: Since Clang 3.8, libclang began exposing an `CXCursor_TypeAliasTemplateDecl` cursor as a result of work done by a KDevelop developer. Ironically, this feature was never actually integrated into KDevelop's clang support, and because of how cursors are dispatched in clang's DUChain builder, the default action is to recurse into any cursor enumeration not explicitly listed. This, in turn, recurses into `CXCursor_TypeAliasTemplateDecl`, and while that does eventually pick up a child `CXCursor_TypeAliasDecl` cursor, ensuring that the declaration is added to the DUChain, the foremost descendants of `CXCursor_TypeAliasTemplateDecl` tend to be template parameters, effectively leaking these parameters into the surrounding context. Moreover, since the addition of `CXCursorTypeAliasTemplateDecl`, references from `CXCursor_TemplateRef` point directly to these cursors which, unfortunately, have a spelling range which covers the `using` keyword that introduces the name which will refer to this alias, but not the name itself. Additionally, unlike `typedef` cursors or `CXCursor_TypeAliasDecl`, `CXCursor_TypeAliasTemplateDecl` yields no useful information about the type it is aliasing; interestingly, `CXCursor_TypeAliasDecl` provides this information without fault, even if it refers to templates with template parameters. Ultimately, this means that the actual `CXCursor_TypeAliasTemplateDecl` cursor, for the moment, is good for little more than signalling the beginning of a new context to capture template parameters and possibly new types, and the actual, declarative unit is still a `CXCursor_TypeAliasDecl` cursor. Sadly, this means the procedure for building uses from cursors needs to be tweaked so lookups will make the correct association (they presently do not). Ultimately, the real fix should be in investigating the upstream implementation of `CXCursor_TypeAliasTemplateDecl` to see if it can be made to function more like a traditional declaration cursor. BUG: 384580 FIXED-IN: 5.2 Test Plan: Modified extant testTypeAliasTemplate test in test_duchain-clang to verify this patch works as expected, namely, that it doesn't leak template parameters into the surrounding context, and that uses of the type alias template are correctly tracked in the DUChain. If you simply apply the changes to test_duchain.cpp on their own, the breakage of the current code model becomes apparent. Reviewers: #kdevelop, mwolff, kfunk Reviewed By: #kdevelop, mwolff Subscribers: apol, kdevelop-devel Tags: #kdevelop Differential Revision: https://phabricator.kde.org/D7799
-
Aleix Pol Gonzalez authored
Summary: So far it was limited to defines and includes, but there's more to life than that. This implements it for cmake where I tested it most, also for qmake where I'm not sure how to yet it won't be worse than ignoring the variables. Reviewers: #kdevelop, kfunk Subscribers: kdevelop-devel Differential Revision: https://phabricator.kde.org/D7752
-