custom make, builddir != srcdir

[Vladimir Prus]

On Saturday 14 February 2009 13:34:42 Andreas Pakulat wrote:
> On 14.02.09 10:51:17, David nolden wrote:
> > Am Samstag 14 Februar 2009 10:31:38 schrieb Andreas Pakulat:
> > > On 14.02.09 11:57:40, Vladimir Prus wrote:
> > > > On Friday 13 February 2009 23:19:53 Andreas Pakulat wrote:
> > > > > On 13.02.09 22:28:36, Vladimir Prus wrote:
> > > > > > It appears KDevelop4 at present does not support custom make projects
> > > > > > where builddir is not the same as source dir. Does anybody knows
> > > > > > what it would take to implement such support, and what would be the
> > > > > > major steps, codewise?
> > > > >
> > > > > Provide a setting in the custom-make-config dialog for the builddir,
> > > > > write code which calculates the relative path of a given folder/dir
> > > > > compared to the projects source root and adds the builddir before that
> > > > > (for buildDirectory()).
> > > >
> > > > I am somewhat confused. Say, I open a project given the Makefile (in
> > > > build dir). Say I've also added option to specify where source tree is.
> > > > OK, but what do you mean by:
> > >
> > > Thats not supported at the moment at all in the custom make support, so
> > > you'd probably have to add quite a bunch of code. Its probably easier to
> > > select the source-dir and then choose "Custom Make" from the drop-down
> > > box in the open-project wizard.
> > 
> > But it would be good if it could work that way, because the out-of-source 
> > build-directories usually contain some pointer back to the source-directory. 
> > That could be used, and then the user has to specify only a single directory.
> 
> Thats true for cmake, but for example not for autotools-builddirs,
> unless you actually parse the Makefile and the gcc-calls in there.

Depends on what you call 'parse'. Here's what I have:


# -------------------------------
# Standard Autoconf-set variables
# -------------------------------
VPATH=/home/ghost/Work/CodeSourcery/Projects/egdb/gdb-fresh

- Volodya