Bug 76277

Summary:	Problem with ui-generated classes
Product:	[Applications] kdevelop	Reporter:	Nexo <nexotap>
Component:	Build tools: Automake	Assignee:	KDevelop Developers <kdevelop-devel>
Status:	RESOLVED NOT A BUG
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	RedHat Enterprise Linux
OS:	Linux
Latest Commit:		Version Fixed In:

Description Nexo 2004-02-27 14:06:18 UTC

Version:           3.2 (using KDE KDE 3.2.0)
Installed from:    RedHat RPMs
Compiler:          gcc3.3.2 
OS:          Linux

Including headers in a subproject for a subclass of a ui-generated class doesn't work unless it's in the same directory if the builddir is not the same as the sourcedir.
Only way i got it to work is to manually specify the include path in the subproject eg. ( -i($top_builddir)/.... .h )
I dunno if it's normal to do this, but it looks strange to me.

Comment 1 Jens Dagerbo 2004-02-27 14:30:33 UTC

This is real. See this forum thread for background:
http://www.kdevelop.org/forum/read.php?f=2&i=11065&t=11065

Comment 2 Jens Dagerbo 2004-02-27 14:30:56 UTC

forgot component

Comment 3 Nexo 2004-02-27 19:57:29 UTC

I know this forum thread, since it was me who started it ;)
As you can read in the thread, teatime animated me to write this report.
So, is this a normal behaviour if kdevelop?

Comment 4 Jens Dagerbo 2004-02-28 01:52:35 UTC

I know this. I just thought it good to include the background in the bugreport. In six months that'll make it a whole lot easier to find. (I'm "teatime", btw..)

It's normal behaviour, but that doesn't mean it's correct. In my opinion, this is a bug. And a rather bad one.

Comment 5 greatbunzinni 2005-07-20 12:00:05 UTC

If you don't like this behaviour at all and if it is such a bad bug, why does this bug report doesn't have a single vote?

Please vote for the bugs you wish to be killed.

Comment 6 Andreas Pakulat 2007-01-15 00:51:57 UTC

Hi,

I talked to Jens on IRC today and we both think this is something that can't be fixed in KDevelop, thus I'm closing this as invalid. Unfortunately we can't "guess" what include directories might be needed for a specific header file.