Removing some functionality from custommakefile support

[Alexander Neundorf]

On Sunday 05 August 2007 17:23, Alexander Neundorf wrote:
> On Sunday 05 August 2007 03:38, Andreas Pakulat wrote:
> > On 04.08.07 22:24:28, Alexander Neundorf wrote:
> > > On Tuesday 24 July 2007 15:02, Andreas Pakulat wrote:
> > > > On 23.07.07 08:38:19, Kris Wong wrote:
> > > > > Could we also remove the functionality that asks to add new files
> > > > > to the project when it is being opened?  This is uber annoying. ;)
> > > >
> > > > No, sorry won't happen. Also I don't quite understand why this is
> > > > uber annoying unless you add tons of files each time before you open
> > > > the project. If there's just one part of the project whose files you
> > > > don't want to add anyway just add the directory to the blacklist
> > > > under Project Options->Custom Make MAnager (or similar).
> > >
> > > My dir layout is like follows:
> > > src/MyProj/ -> has the sources
> > > src/MyProj/build/ -> build dir
> >
> > Where does the kdevelop file sit? The blacklist works relative to the
> > project directory...
>
> Ah, relative paths, I'll try again.

Yes, it works, except some bugs.

The code which loads the blacklist doesn't check whether a directory is a 
relative or an absolute path and treats all paths as relative, i.e. absolute 
paths don't work.

If the KURL dialog is used to select a blacklist directory, it inserts the 
absolute path, so this doesn't work.

It would be nice if I could put the project root dir in the blacklist, but I 
didn't get this working: not using the absolute path (see above), not 
using ".", or "/" or "./" or an empty entry.

The blacklist widget has neither What's this help nor tooltips.

Bye
Alex