On 2003-03-02, Muli Ben-Yehuda wrote:
On Sat, Mar 01, 2003 at 11:02:33PM +0200, Beni Cherniavsky wrote:
OK. Then have a relative path to the top in every makefile and let
`make dist' in the top directory fix these pathes in all makefiles in
subdirs, before creating the archives.
No. As
On 2003-02-28, Muli Ben-Yehuda wrote:
On Fri, Feb 28, 2003 at 12:43:02PM +0200, guy keren wrote:
Now that I think of it, another way would be to change the build
structure from recursive builds to a centralized build - all
directories are built from the top level directory. Let's say
On Sat, Mar 01, 2003 at 11:02:33PM +0200, Beni Cherniavsky wrote:
OK. Then have a relative path to the top in every makefile and let
`make dist' in the top directory fix these pathes in all makefiles in
subdirs, before creating the archives.
No. As mentioned previously, having a relative
On Wed, 26 Feb 2003, Muli Ben-Yehuda wrote:
Let's say that I have a complex project, using many Makefiles. In some
of them, I'd like to refer to other directories of the project. So
far, I've been using various combinations on ../, ../../, etc, but
that's awfully brittle when you start
On Wed, 26 Feb 2003 08:27:56 +0200
Muli Ben-Yehuda [EMAIL PROTECTED] wrote:
Is there a way, which does NOT
involve setting an environment variable, to refer to the top level
project directory?
Of course automake generated Makefiles (Makefile.in to be exact)
are built to define $(topdir)
Muli Ben-Yehuda [EMAIL PROTECTED] writes:
Let's say that I have a complex project, using many Makefiles. In some
of them, I'd like to refer to other directories of the project. So
far, I've been using various combinations on ../, ../../, etc, but
that's awfully brittle when you start moving
