Bug 65364

Summary:	Remove Subproject not working in Automake Manager
Product:	[Applications] kdevelop	Reporter:	Ian Wadham <iandw.au>
Component:	Build tools: Automake	Assignee:	KDevelop Developers <kdevelop-devel>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version:	3.0.0a7
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Ian Wadham 2003-10-02 11:08:17 UTC

Version:           3.0.0a7 (using KDE 3.1.1)
Compiler:          gcc version 3.3 20030226 (prerelease) (SuSE Linux)
OS:          Linux (i686) release 2.4.20-4GB

If you use Remove on a Subproject, it fails with an error message saying that the subproject is not in the SUBDIRS list.  That list contains either $(TOPSRCDIRS) or $(AUTODIRS), but should not those symbols be evaluated before checking for
an error?

Comment 1 Jens Dagerbo 2003-12-17 01:46:14 UTC

I have no idea about the autotools.. but is this related to bug #60682 ?

Comment 2 Ian Wadham 2003-12-17 06:25:04 UTC

Subject: Re:  Remove Subproject not working in Automake Manager         

Well, it's a sort of inverse of #60682.  That bug said you shouldn't put
"new_subproject" in the Makefile.am again if it is already part of the
evaluation of $(TOPSRCDIRS).  My #65364 said you should be
allowed to remove "old_subproject" if it occurs in the evaluation
of $(TOPSRCDIRS) or $(AUTODIRS): not be told "old_subproject"
does not exist.

In other words Automake Manager should evaluate its symbols
before trying either to add or delete a subproject.  If it does that
now, the same fix might have zapped both bugs :-)  maybe?  Did
the #60682 fix also evaluate $(AUTODIRS)?

> I have no idea about the autotools.. but is this related to bug #60682 ?

Comment 3 Megan Webb 2006-12-05 12:09:50 UTC

Testing this on 3.4 branch revision r610450 I am not able to reproduce this bug.
automake manager has had a lot of bug fixes in the 3.4 tree.

Please reopen if you can reproduce on the latest from svn on 3.4 branch.