On Tue, Aug 4, 2009 at 1:33 PM, nathan binkert<[email protected]> wrote: >> Now that the other GEM5 issues are mostly resolved (thanks everyone!), I >> wanted to discuss the protocol directory issue in more detail. I'm >> completely fine with recompiling all files when changing protocols. I would >> just like the ability to have two different M5 binaries, using different >> protocols, co-exist in the same M5 tree. A solution similar to the current >> ALPHA_SE and ALPHA_FS binaries would be great. > > This can be done right now by using a different build directory for > each protocol. You're used to having a scons target of > "build/ALPHA_FS/...", you can however do something like > build/<protocol>/build/ALPHA_FS and that will cause things to be built > in a different directory. You can even specify a full path that is > not a subdirectory of the m5 dir.
I don't think even this is necessary... if you say something like scons default=ALPHA_FS build/ALPHA_FS_P1/m5.opt PROTOCOL=P1 scons default=ALPHA_FS build/ALPHA_FS_P2/m5.opt PROTOCOL=P2 ... that should set up ALPHA_FS_P1 and ALPHA_FS_P2 to do just what you want (without needing the extra args after the first time, i.e., just say "scons build/ALPHA_FS_P1/m5.opt"). This is all off the top of my head, so the syntax may be slightly off (esp. the protocol specification part), but the basic idea is supported. There's a litte more detail on this page; look for the bullet that starts "You can define your own configurations": http://m5sim.org/wiki/index.php/SCons_build_system Steve _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
