7 messages in com.perforce.jamming[jamming] Multiple Jambase files| From | Sent On | Attachments |
|---|---|---|
| Darrin Smart | 21 Dec 2001 22:19 | |
| Darrin Smart | 21 Dec 2001 22:52 | |
| Matt Armstrong | 24 Dec 2001 20:10 | |
| Darrin Smart | 29 Dec 2001 19:53 | |
| Toon Knapen | 31 Dec 2001 00:14 | |
| Toon Knapen | 31 Dec 2001 00:25 | |
| Diane Holt | 01 Jan 2002 13:32 |
| Subject: | [jamming] Multiple Jambase files |
|---|---|
| From: | Darrin Smart (dar...@suresoftware.com) |
| Date: | 12/29/2001 07:53:49 PM |
| List: | com.perforce.jamming |
On Tuesday, December 25, 2001, at 03:10 PM, Matt Armstrong wrote:
Yes, for any rule named X there is one and only one "actions X" that will work. In this case, you're probably calling the rule Cc for both the gcc and xcc trees. Call them different names and you can use them both in the same Jam run. Then the problem becomes getting the built in Objects rule to call xcc_Cc when appropriate. I don't have any direct experience getting Jam to build with two different compilers in the same run, so I won't be much help.
Thanks for the reply Matt.
It seems like a bit of a shortcoming in Jam, particularly for very large and complex projects.
One solution might be to make the file name matching be based on regular expressions instead of file suffixes. Then I could override the Object rule to select CC or xcc_Cc as you said.
Another example of the same problem I encountered is that some of our .y files only work with yacc and some only work with bison (I know, thats not good, but the point of the exercise is to replace make, not fix up all the code!)
- Darrin