== Project LeaderTODO ==* At the moment FUEL is manually added to the build (ssee below). It will be much easier if the build script did it for us :) ==

Name(== Project Details ==At the moment FUEL only works on Firefox3. This project is dedicated in back porting FUEL to make it work with Firefox2 == fuelApplication.js =='''fuelApplication.js''' is located in '''mozilla/browser/fuel/src''' and will be the main file that will undergo the changes.You can get the latest update of it [http://www.samerziadeh.com/mozilla/fuelApplication.js here]. It's) just a plain text file, it doesn't have the fancy change revision. Below are the list of primary people working the functions I tested with and what did and didn't work. <b><font style="font-size:120%">Working:</font></b>* Console<b><font style="font-size:120%">Not Working:</font></b>* Bookmarks == Build Instructions ==We need to create a directory to throw the mozilla source in.<pre>mkdir mozilla-1.8-branchcd mozilla-1.8-branch</pre> This will fetch the ''client.mk'' file from mozilla.''client.mk'' contains info on how to configure the build tree to configure any productthe ''-r MOZILLA_1_8_BRANCH'' specifies to the server that we want the ''client.mk'' file from the 1.8 branch<pre>cvs -d :pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot co -r MOZILLA_1_8_BRANCH mozilla/client.mk</pre>  Now we need to create the project''.mozconfig'' file.It contains parameters for ''client. If you want mk'' on how to join a project checkout and build.The last ''ac_add_options'' line is not needed for non Mac machines.<pre>cd mozillacat > .mozconfig << MOZCONFIG# Options for client.mk.mk_add_options MOZ_CO_PROJECT=browsermk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdirmk_add_options MOZ_MAKE_FLAGS="-s -j4" # Options for 'configure' (same as leader, discuss command-line options).ac_add_options --enable-application=browserac_add_options --enable-debugac_add_options --enable-testsac_add_options --with other leaders first-macos-sdk=/Developer/SDKs/MacOSX10. Include links to personal pages within wiki4u.sdkMOZCONFIG</pre> After creating the MozConfig file we can begin downloading the source. <small>(around 220mb)</small><pre>make -f client.mk checkout</pre>

Now that we have acquired the fuel source we need to modify the ''browser/Makefile.in'' to let the build know about the addition<pre>cd mozilla/browservi Makefile.in</pre>* Go to the line starting with DIRS* Append fuel to the end of it<pre>DIRS == Project Details ==base components locales extensions themes app fuel</pre> The build script doesn't generate the fuel part automatically, which is why fuel is fetched after the build is done.The following steps will force the generation of the makefiles manually, and then rebuild fuel and app<pre>cd ../objdir../build/autoconf/make-makefiles browser/fuelmake -C browser/fuelmake -C browser/app</pre>

== Project News Links ==

* [http://samermozilla.blogspot.com/ Samer's Blog]* [http://quality.mozilla.org/en/node/452 How To Build a Mozilla Tree]* [http://wiki.mozilla.org/FUEL FUEL]* [http://developer.mozilla.org/en/docs/FUEL FUEL docs]* [https://bugzilla.mozilla.org/show_bug.cgi?id=390335 bug #390335]* [http://mxr.mozilla.org/seamonkey/find?string=fuel%2Ftest%2Fbrowser_&tree=seamonkey FUEL JS Test Files]