[kdevelop] [Bug 373973] Kdevelop clang parser has many issues

2017-01-01 Thread Ted
https://bugs.kde.org/show_bug.cgi?id=373973

--- Comment #7 from Ted  ---
I would like to add a comment that may help others stumbling across this issue.

If there are any RED issues reported in Problems for include files, the parser
will not work.  You must resolve these problems in order for the parser to work
again.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 373973] Kdevelop clang parser has many issues

2016-12-30 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=373973

Kevin Funk  changed:

   What|Removed |Added

 Resolution|FIXED   |WORKSFORME

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 373973] Kdevelop clang parser has many issues

2016-12-30 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=373973

--- Comment #6 from Kevin Funk  ---
Thanks, glad you figured out how to solve the problems!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 373973] Kdevelop clang parser has many issues

2016-12-29 Thread Ted
https://bugs.kde.org/show_bug.cgi?id=373973

--- Comment #5 from Ted  ---
I must say that with my issues resolved, the Background parser is working very
well.  I am very impressed with Kdevelop 5.x.x.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 373973] Kdevelop clang parser has many issues

2016-12-29 Thread Ted
https://bugs.kde.org/show_bug.cgi?id=373973

Ted  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Ted  ---
The whole problem was relying on the Makefile to supply the include paths.
Apparently KDevelop does not parse pkg-config entires in the Makefile.
I added the needed include files paths in Kdevelop and resolved the problem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 373973] Kdevelop clang parser has many issues

2016-12-20 Thread Ted
https://bugs.kde.org/show_bug.cgi?id=373973

--- Comment #3 from Ted  ---
Looks like this has boiled down to the lack of pkg-config support.
I am using glib and in my Makefile I use `pkg-config  glib-2.0 --cflags`
As you may know, this will provide the paths:
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include
It appears that the clang parser will not be able to parse if these paths are
not present and hence the strange behavior with the STL includes.

Is there a way to add the pkg-config support into the parser?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 373973] Kdevelop clang parser has many issues

2016-12-20 Thread Ted
https://bugs.kde.org/show_bug.cgi?id=373973

--- Comment #2 from Ted  ---
Further strangeness:

I have found while initially reparsing my project with the only change in 
project->Open Configuration...->Language Support
_GLIBCXX_USE_CXX11_ABI 0

std::string
Show correctly
typedef basic_string< char, std< char >, std< char > > string
Container: std Kind: Typedef 
Decl.: stringfwd.h :74 Show uses

But somewhere during the reparsing back to this:

typedef int string
Container: std Kind: Typedef 
Decl.: stringfwd.h :74 Show uses

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 373973] Kdevelop clang parser has many issues

2016-12-20 Thread Ted
https://bugs.kde.org/show_bug.cgi?id=373973

--- Comment #1 from Ted  ---
The settings I am referring to are under 
project->Open Configuration...->Language Support

Maybe this is an issue with c++11 v.s. older ABI
When I pulled up a project that had c++11 for the language version then I do
see std::string interpreted correctly:

typedef basic_string< char, std< char >, std< char > > string
Container: __cxx11 Kind: Typedef 
Decl.: stringfwd.h :74 Show uses

If I try to use 03 it reverts to this:
typedef int string
Container: __cxx11 Kind: Typedef 
Decl.: stringfwd.h :74 Show uses

If I include the define for _GLIBCXX_USE_CXX11_ABI 0 then back to this:
(Using 03 or 11, doesn't matter).
typedef int string
Container: std Kind: Typedef 
Decl.: stringfwd.h :74 Show uses

-- 
You are receiving this mail because:
You are watching all bug changes.