https://bugs.kde.org/show_bug.cgi?id=381506
--- Comment #3 from Christos Gourdoupis <xri...@otenet.gr> --- Hmmm... ok I don't know how cmake works, never used it. But I just found out that if `make` runs with --no-print-directory option, kdevelop gets confused as to where gcc is based when it runs. However if `make` prints lines like: make[2]: Entering directory '<some directory>' etc... then kdevelop finds and opens the relevant source file properly. -- You are receiving this mail because: You are watching all bug changes.
