Dave Lewis | 1 Apr 2000 01:56
Favicon

Re: foo.exe depends on itself

  > X-Lotus-FromDomain: DSSI
  > From: "Michael Graff" <michael.graff <at> diversifiedsoftware.com>
  > Date: Fri, 31 Mar 2000 14:44:57 -0800
  > Mime-Version: 1.0
  > Content-type: text/plain; charset=us-ascii
  > Sender: jamming-admin <at> perforce.com
  > Errors-To: jamming-admin <at> perforce.com
  > X-Mailman-Version: 1.0rc3
  > Precedence: bulk
  > List-Id: Discuss the build tool Jam/MR with other users <jamming.perforce.com>
  > X-BeenThere: jamming <at> perforce.com
  > 
  > I ran into what seems to be a quirk:
  > 
  > If I try to build an executable called "foo" in a directory also called
  > "foo" I get:
  > 
  > warning: foo.exe depends on itself
  > 
  > Looking at a d3 trace, I see something like the first trace below.
  > 
  > I believe what's happening is jam is can't distinguish between the
  > directory "foo" and the pseudotarget "foo" that gets created by the
  > MainFromObjects rule.
  > 
  > If I use a different directory name (like bar), I get the second trace.
  > 
  > Is there a way to help jam distinguish a directory name from a
  > pseudotarget?

(Continue reading)


Gmane