Version: (using Devel) OS: Linux Installed from: Compiled sources KDevelop4 doesn't seem to be smart at finding build-time generated headers. For instance, KDE has a cmake macro to generate a dbus adaptor from a class or whatever, it doesn't find the header when it is included (even though gcc does.. obviously).
Of course gcc finds the file, because when you build it'll be generated. However until the first build KDevelop cannot possibly find that file as it doesn't exist.
Well yeah, naturally, I was just saying.. the file exists :P Anyways, you end up specifying the build directory anyways, so.. it would be nice if this would happen, mostly because I love the "mousing over to see where it is, and instantly being able to view the code within it" feature. Obviously it can't find it until the first build, but it should *try* to find it, since it could gather it from the include line, and if it doesn't exist, you didn't build it, if it does, it can find it... I don't see how this was marked as invalid, since I am not requesting to do the impossible, it would be better if you would merely say that it is a difficult feature to implement, or something of the like.. since I didn't say to find the autogenerated header, before it is generated :)
Sorry but I don't follow you at all. Can you please describe in clear words what the problem with the autogenerated file is that you have?
PS: Your initial description sounds as if your problem is that an autogenerated file is marked as an error if you haven't build the project (and the file is being generated). Thats why I closed this as invalid, because thats not a bug. The file doesn't exist, so the the marking is correct.
Okay, sorry about that. Basically, exactly what you said in the latest comment, except this was after I have compiled the project. Also, I don't build with KDev4 (I just use a Konsole session). The auto-generated header files, that are indeed existent in my build folder (because I compiled the project), are being marked (underlined) in red, because KDevelop does not know what the #include <> line is pointing to. Normally, it will find normal header files (user-created ones) perfectly, but ones that are generated.. i.e. by Qt, are not found, even though they *do* exist in the build folder. Let me know if this clears things up.
ok, so this sounds as if KDevelop doesn't get the proper include dirs. I assume you did configure a builddirectory inside KDevelop and this is a cmake project? One way to find out a bit more would be to activate the cmake debug channels in kdebugdialog and then run kdevelop and redirect all output to a file and let kdevelop open the project. Then attach the file to this bugreport.
waiting for more information, its unclear which project type was used and wether a proper builddir was configured.
bugzilla screwed up the resolution, re-opening.
really marking as waiting for info.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!