"Is there any ETA on when the build documentation will be available. I'm looking forward to working with this browser and maybe contribute some code"
I have the docs completed for building both mozilla and k-meleon, including the necassary tools you will need as well as step by step instructions.
I can build a CVS k-meleon and use it with kmeleon .7 without a hitch, i.e., replace the v 0.7 k-meleon.exe with a newly built k-meleon.exe. The same goes for all of the kplugins, i.e., layers.dll, bookmarks.dll, etc..., etc...
However, I have been unable to get a new build of k-meleon to work with a new build of mozilla. The only information that I have on how to do this amounts to nothing more than a single paragraph of sorely outdated text.
I've dicked around with it trial and error but still no go. Obviously, I am unable to document/instruct the merging of a cvs build of kmeleon with that of a cvs build of gecko until I can do it myself.
You can however still work on core kmeleon stuff (especially plugins) without having to merge with a newly built gecko. Just plop new builds of k-meleon.exe (or any of its plugins) into your binary release folder for k-meleon v0.7.
If anyone is interested I can post what I have so far so you can get going on stuff. I also have a new set of VC++ project/workspace files, as well as a few source changes, so everything will build error, warning, and hassle free. (The source release of k-meleon 0.7 is broken and some stuff on cvs needed repair, too)