Rumbles continue as we finish rearranging the trunk for a more extensible and organized layout. What started rough has been polished the last few days and we're here at the point where just about everything is back to the point we left it at. Work continues on tweaking the new .csproj files which will do wonders for any VS.NET users who would like to check out the code. Chriss is separating the script generator we used for the test kernel so that it better fits with the capabilities/model of msbuild. Meanwhile me and Bruce have been keeping the nant files tidied up, and he's also been adding nant rules for FXCop, "nant fxcop" from trunk/Kernel/Core. I've gone and added some rules for AOTing the mainline kernel from the buildfile "nant aot" or "nant aot-image". You can provide extra AOT options with `nant aot -D:aot-options="-text-dump"' or so.
We split the dual-project SharpOS.AOT directory into AOT/Core and AOT/Main. We moved all the binary reference DLLs into trunk/References. Various other layout changes to better suit moving forward. So here's the layout of trunk/ as of this writing (r309): AOT - Core - Core.Tests - Kernel.Tests - Main Data - KeyMaps Kernel - Core - korlib References - Mono.GetOptions.dll - Mono.Cecil.dll Tools - KernelTestsWrapperGen - KeyCompiler We also plan to store the SharpOS userspace at trunk/Userspace. What do you think about this layout? Was the old one better? -- fury long name: William Lahti handle :: fury freenode :: xfury blog :: http://xfurious.blogspot.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ SharpOS-Developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sharpos-developers
