> A mechanism where I can say binary foo needs file bar, and then when I tell > it to build foo it build's it with bar, and bar doesn't get mixed in to > other things. I think you're new widget that was like mercurial patch guards > would help with that, right? You could have a guard for each extra target. Ah, I see. I personally wouldn't use any of that. Don't use Source or PySource or that sort of thing. Just set up normal looking SConscript files with their own targets and such. The Source/PySource/etc. stuff is really about building the m5 binary and dealing with all of the variations that we have.
> I'm not sure how SLICC is structured, but it might be hard to get out file > information without running the whole description, depending on how the > multi-file output thing is implemented. In SLICC, we parse the entire file using the ply grammar and generate the AST in both phases. In one phase, you walk the AST simply to figure out which files will be generated. In the other, you actually do the generation. I'm suggesting that you do that as well, the files aren't that long and I bet that parsing the ISA desc files and generating the AST takes a second or so. Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
