Re: target variable expansion with included make files

"Brad Kemp" <[EMAIL PROTECTED]> writes: > What I am trying to do is to build a project out of many sub projects. > As each sub project is updated, I want the final target pathname to reflect > the new revision level without having to change the main makefile. > This allows me to build multiple ver

target variable expansion with included make files

I don't know if this is a bug or this is the way make works I have appended three makefiles to this email. The main makefile includes two small makefiles. Each make file defines variables used in the targets of the other makefile. The target names are immediatly expanded which causes the first make

make.texi - Documentation Wording

Hello, I would like to submit to you that the word 'unmolested' be changed to a more carefully chosen word such as unchanged or unaltered or unaffected. The use of this word in the documentation seems ill chosen. Thanks, Richard _ Se

Re: target variable expansion with included make files

"Brad Kemp" <[EMAIL PROTECTED]> writes: > The main makefile includes two small makefiles. > Each make file defines variables used in the targets of the other makefile. > The target names are immediatly expanded which causes the first makefile > not to use the variables defined in the second makefi

Re: target variable expansion with included make files

>-- Original Message -- >To: [EMAIL PROTECTED] >From: Boris Kolpackov <[EMAIL PROTECTED]> >Date: Thu, 5 Aug 2004 14:49:06 + (UTC) >Subject: Re: target variable expansion with included make files > > >"Brad Kemp" <[EMAIL PROTECTED]> writes: > >> The main makefile includes two small makefiles. >