5 messages in com.perforce.jammingunbound targets...| From | Sent On | Attachments |
|---|---|---|
| Dave...@vignette.com | 22 Feb 1999 13:44 | |
| Laur...@perforce.com | 22 Feb 1999 14:18 | |
| Iain...@mcclatchie.com | 22 Feb 1999 14:39 | |
| Dave...@vignette.com | 22 Feb 1999 15:00 | |
| Iain...@mcclatchie.com | 22 Feb 1999 15:49 |
| Subject: | unbound targets... |
|---|---|
| From: | Iain...@mcclatchie.com (Iain...@mcclatchie.com) |
| Date: | 02/22/1999 03:49:40 PM |
| List: | com.perforce.jamming |
along this line, I started looking at rule Main, and one thing it does is say
NOTFILE $(<) ;
so if the exe (unsuffixed) name and a directory name are the same, it seems this rule will make jam think it can not be a directory, and probably not be able to bind it to a file, and perhaps not be able to discern that the file already exists?
does it seem reasonable to grist that target before saying NOTFILE? This should make it distinct, I would think.
Hmmm.
1) Does my MkDir rule fix your problem, or not?
2) I'm not sure about the effects of NOTFILE, but I suspect you won't hit the problem if you use my MkDir. I wasn't kidding when I sent it to you -- please try to see if it works.
Build management, in my opinion, is successful when I don't have to think about it. I'm pleased to say that I use Jam for all build management, and I find myself generally rusty and unfamiliar with most issues in Jam. It's pretty easy for me to cut and paste my solutions if they're for your exact problem. You're asking much more if you want me to actually THINK about a problem that isn't going to stop me now or at some point in the future.
- -Iain