> [...] > Probably, yes. Is exactly what you're testing with available in a repo > somewhere?
Of course, the orbuild system is here: https://github.com/rdiez/orbuild It might be a little rough yet, give me a shout if you encounter any problems. You'll find a README file at root level, and there's also a blog article here: http://www.rte.se/blog/blogg-modesty-corex/using-orbuild Run "./orbuild" once in its default configuration to see if everything is OK on your platform. Then edit this file: https://github.com/rdiez/orbuild/blob/master/Scripts/Projects/OpenRISC/Makefile Change variable ENABLE_OPEN_RISC_TEST_SUITE to 1 and run "./orbuild --resume" to run the tests. Don't write any spaces or comments after the '1'. This is a common shortcoming in makefiles, I'll see what I can do about it in the future. The ORPSoC repository should be in <top level>/Repositories/ORPSOCV2 , you can apply any patches there. In order to rebuild and rerun the tests against ORPSoC without rebuilding everything else, delete the following files and then run "./orbuild --resume" again: Builds/LatestBuildDir/OrbuildSentinels/Autoconf/ORTS_EXES.AutogenSentinel Builds/LatestBuildDir/temp/ORTS_ORPSOC_IVERILOG/SubprojectSentinels/* Cheers, rdiez _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
