On Fri, 28 Jan 2011 17:18:16 -0600, Rob Browning wrote:
> I think the use of GNU make VPATH is fairly common. For example, I
> believe the autotools build a tree that matches the srcdir structure and
> add Makefiles that contain something like this:
>
> VPATH = ../../wherever/notmuch/thisdir
>
On Fri, 28 Jan 2011 17:18:16 -0600, Rob Browning
wrote:
> I think the use of GNU make VPATH is fairly common. For example, I
> believe the autotools build a tree that matches the srcdir structure and
> add Makefiles that contain something like this:
>
> VPATH = ../../wherever/notmuch/thisdir
Hallo!
On Sat, 29 Jan 2011 06:58:59 +1000, Carl Worth wrote:
> Rather than documenting a limitation here, why don't we do what people
> actually want.
Well, not a big deal for me -- I'm just used to building projects
containing a configure file outside of the source tree, and the notmuch
build m
Hallo!
On Sat, 29 Jan 2011 06:58:59 +1000, Carl Worth wrote:
> Rather than documenting a limitation here, why don't we do what people
> actually want.
Well, not a big deal for me -- I'm just used to building projects
containing a configure file outside of the source tree, and the notmuch
build m
> +if ! { : < configure; } 2> /dev/null; then
> +cat < +*** Error: You have to configure and build in the source directory.
> +
> +EOF
> +exit 1
> +fi
Rather than documenting a limitation here, why don't we do what people
actually want.
What do other build systems generally do when runnin
Carl Worth writes:
> What do other build systems generally do when running configure from
> some other directory? Copy/link the Makefiles and then construct them
> carefully such that they can find all the source files?
I think the use of GNU make VPATH is fairly common. For example, I
believe
Carl Worth writes:
> What do other build systems generally do when running configure from
> some other directory? Copy/link the Makefiles and then construct them
> carefully such that they can find all the source files?
I think the use of GNU make VPATH is fairly common. For example, I
believe
> +if ! { : < configure; } 2> /dev/null; then
> +cat < +*** Error: You have to configure and build in the source directory.
> +
> +EOF
> +exit 1
> +fi
Rather than documenting a limitation here, why don't we do what people
actually want.
What do other build systems generally do when runnin
On Tue, 11 Jan 2011, Thomas Schwinge wrote:
> From: Thomas Schwinge
>
> Signed-off-by: Thomas Schwinge
>
> ---
> configure | 11 +++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/configure b/configure
> index c58dd0f..b5e446c 100755
> --- a/configure
> +++ b/c
On Tue, 11 Jan 2011, Thomas Schwinge wrote:
> From: Thomas Schwinge
>
> Signed-off-by: Thomas Schwinge
>
> ---
> configure | 11 +++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/configure b/configure
> index c58dd0f..b5e446c 100755
> --- a/configure
> +++ b/c
From: Thomas Schwinge
Signed-off-by: Thomas Schwinge
---
configure | 11 +++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/configure b/configure
index c58dd0f..b5e446c 100755
--- a/configure
+++ b/configure
@@ -188,6 +188,17 @@ developers. Then, please email those d
From: Thomas Schwinge
Signed-off-by: Thomas Schwinge
---
configure | 11 +++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/configure b/configure
index c58dd0f..b5e446c 100755
--- a/configure
+++ b/configure
@@ -188,6 +188,17 @@ developers. Then, please email those d
12 matches
Mail list logo