A fast processor (recommended, but not required - I’ve compiled on a PII 450MHz computer before).Lots of RAM (1 GB recommended, should work with less).A decently-sized hard drive with free space (I recommend at least 10 GB free space).Windows XP (Windows 2000 may or may not work, but lower versions will not).Debugging the build may be limited, if only because no GUI debugger exists (I don’t debug, so I don’t know how limited).This may no longer be true because of a recently fixed bug, but I haven’t tested. With an objdir build (the generally recommended way to build), you’ll have to manually tweak some path creation for browser/app/profile/extensions/, because the build process creates the directories without the curly braces.You can’t build the IE migrator, and you have to apply a patch to the source to keep from trying to build it.You can’t build ActiveX (exact reasons unknown, but the build doesn’t complete).Huge download size - almost certainly not for dialup.You need a newish version of Windows - possibly Windows XP.Binary compatibility with nightly builds, so 3rd-party plug-ins work.Build your own – don’t wait for the nightlies!.Also, these directions only apply to trunk builds you may have to do other bits of hackery or use older versions of some tools in order to build older code. Hopefully I’ll have time to make the directions more generic, but I don’t know when that’ll be. Also, note that your mozconfig file will need to be at least somewhat different if you intend to build an application other than Firefox. However, I’ve only tested Firefox and Thunderbird so far. This probably works for other Mozilla-based applications, like Sunbird, the Mozilla Suite, and others. This document describes how a complete, optimized build environment can be created from nothing but a Windows command line. The free compiler can also be used to build Mozilla applications. Compiled code created with it is binary-compatible with code used in downloadable plug-ins like Java, Flash, Shockwave, and others (something which can’t be said for builds created using MinGW and gcc on Windows). This free version is (interestingly enough) fully functional. Microsoft recently released a free version of the Visual Studio C++ compiler. ![]() Note: I’ve moved comments over to a separate page to de-clutter this page and make it easier to use. Additionally, I expect the non-Cairo code to be removed from the tree fairly soon after Cairo is enabled.) (Yes, compiling without Cairo should still work as long as the non-Cairo code remains in the tree, but Cairo’s the future, and there are a good number of bugs which will only ever be fixed in Cairo-based builds. The plan is for the new graphics backend based around Cairo to land really soon now (it was scheduled for the end of January), and given that I had problems compiling a Cairo-based build, I’m waiting until that backend’s been switched on and all the build bugs have been worked out before attempting to update these instructions. □ I’d hoped to update it over January, but it didn’t happen. Last updated: not recently enough for me to consider giving it a good last edited date.
0 Comments
Leave a Reply. |