On 6/13/13, Matthew Allen <fret@xxxxxxxxxxxx> wrote: > Most of my IDE now works. The bugs are getting less and less severe. I might > be able to self-host the build system shortly, which would mean better > makefiles. The current code base generates much better dependencies than the > hand written makefiles I've been using to date. Having the minimum re-build > set is a big win when the compile/link cycles are so slow. Cool! > I'm keen to try a > non-debug kernel with a non-indexed 2nd partition for maximum compile > performance but I wouldn't know where to start settings that up. I'm > assuming I'd have to configure and then build the kernel and then install > it? As far as the kernel goes, the steps are as follows, assuming you have a haiku source checkout already: - if it doesn't already exist, create the subfolder build/user_config_headers/ - copy build/config_headers/kernel_debug_config.h into the above folder. - open that file, and at the top you will find the line: #define KDEBUG_LEVEL 2 Change that to 0, then clean and jam -qj4 kernel The resulting kernel binary will end up in generated/objects/haiku/x86/release/system/kernel/kernel_x86, and can subsequently be installed to /system. As far as the unindexed partition goes, simply go into DriveSetup, and choose to format the corresponding partition with BFS. The corresponding dialog will have a checkbox that reads "Enable query support", which needs to be unchecked to disable indexing. Note that a few caveats apply to such a partition, most notably, as the above checkbox indicates, it won't be able to participate in BFS queries. This also means that things like the registrar won't be able to locate apps by signature from it. Consequently, if you want an app to handle e.g. particular file types, it should be located on a query-enabled partition, since otherwise actions like automatically launching said application when double clicking a corresponding file type may fail. Hope that helps, Rene