MozillaWiki

Firefox/Tegra/Build Notes: Difference between revisions

Page Discussion

Firefox/Tegra/Build Notes (view source)

Revision as of 00:22, 13 October 2009

284 bytes added ,  13 October 2009
→‎Initial Setup
 
(41 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This is a work in progress, based largely on the [[Mobile/Build/Windows_Mobile_Build_Instructions|Windows Mobile Build Instructions]].
This is a work in progress; pieces of the [[Mobile/Build/Windows_Mobile_Build_Instructions|Windows Mobile Build Instructions]] might also be relevant and/or informative.  However, they are targeted towards building Fennec/XULRunner for Windows Mobile.


= Initial Setup =
= Initial Setup =
Line 7: Line 7:
** Visual Studio 2008 (2005 ought to work, but this guide has been written with 2008 in mind), with Smart Device support
** Visual Studio 2008 (2005 ought to work, but this guide has been written with 2008 in mind), with Smart Device support


* To reduce pain, grab an updated Mercurial from http://mercurial.berkwood.com/ -- install it in C:\mozilla-build\hg (overwriting the hg install that's there).
* Install the [http://www.microsoft.com/DownLoads/details.aspx?familyid=FA1A3D66-3F61-4DDC-9510-AE450E2318C3&displaylang=en Windows CE 5.00 Standard SDK].  If you have a SDK provided by a Windows CE 6 device manufacturer, it ought to work as well; this has only been tested with the CE 5.00 SDK.


* Install the [http://www.microsoft.com/DownLoads/details.aspx?familyid=FA1A3D66-3F61-4DDC-9510-AE450E2318C3&displaylang=en Windows CE 5.00 Standard SDK].  If you have a SDK provided by a Windows CE 6 device manufacturer, it ought to work as well; this has only been tested with the CE 5.00 SDK.
* The DirectDraw backend for Windows CEneeds the ddraw.h and ddraw.lib in the CE5 SDK replaced with those from the Windows Mobile 6 SDK (you'll get an error saying "Cairo was not compiled with support for the directdraw backend" if you skip this step).  This will require installing the WM6 SDK, and then, assuming the SDKs are installed in the default locations, copying:
** '''/c/Program Files/Windows Mobile 6 SDK/PocketPC/Include/Armv4i/ddraw.h''' to '''/c/Program Files/Windows CE Tools/wce500/STANDARDSDK_500/Include/Armv4i'''
** '''/c/Program Files/Windows Mobile 6 SDK/PocketPC/Lib/Armv4i/ddraw.lib''' to '''/c/Program Files/Windows CE Tools/wce500/STANDARDSDK_500/Lib/Armv4i'''


= Downloading the Source =
= Downloading the Source =


I tend to use 'c:\proj' as the root for most of my work; replace that path as appropriate for your usage.  I would suggest a path without spaces, though.
The process for creating a source tree and  build is basically the same as for building Firefox for Windows XP/Vista. See [https://developer.mozilla.org/En/Simple_build this simplified guide] for the general process.
 
Mozilla uses the Mercurial version control system. For more detailed information, see [https://developer.mozilla.org/en/Mozilla_Source_Code_%28Mercurial%29 this page].
 
In 'C:\mozilla-build', there will be a few batch files -- fire up '''start-msvc9.bat''' to obtain a console window with paths set up for building.  All commands are assumed to be executed within such a window.


Note: the MSYS environment that drives the build uses Unix-style forward slashes for path separators.  Drive letters are also treated as directories, so "C:\proj" becomes "/c/proj". Note that MSYS will automatically translate "/c/proj" into "C:\proj" from the command line; this sometimes causes problems when trying ot pass arguments that start with "/" to programs. To get around this, use "//" -- for example, "dumpbin //exports".  Or, use the - form of arguments if supported.
In 'C:\mozilla-build', there will be a few batch files -- fire up '''start-msvc9.bat''' to obtain a console window with paths set up for building.  All commands are assumed to be executed within the new window. Note that one Windows Vista/7 you may need to right-click the .bat and Run As Administrator, or else the build quickly fails with an "nsinstall: bad file number" error.


* First, create some directories:
# '''mkdir /c/proj''' (or any path without spaces!)
** '''mkdir /c/proj'''
# '''cd /c/proj'''
** '''cd /c/proj'''
# '''<nowiki>hg clone http://hg.mozilla.org/mozilla-central</nowiki>'''


* Then check out the current source tree; this will grab a copy of the source in a directory called mozilla-central in /c/proj:
Mozilla uses the Mercurial version control system. The "hg clone" command will create a mozilla-central directory in /c/proj containing the Mozilla source.  For more detailed information, see [https://developer.mozilla.org/en/Mercurial this page].  For creating your own patches and/or maintaining local changes, I'd suggest using the [https://developer.mozilla.org/en/Mercurial_Queues Mercurial Queues] extension.
** '''hg clone http://hg.mozilla.org/mozilla-central'''


* To update to the latest source, from the mozilla-central directory:
'''NOTE''': the MSYS environment that drives the build uses Unix-style forward slashes for path separators. Drive letters are also treated as directories, so "C:\proj" becomes "/c/proj". Note that MSYS will automatically translate "/c/proj" into "C:\proj" from the command line; this sometimes causes problems when trying ot pass arguments that start with "/" to programs.  To get around this, use "//" -- for example, "dumpbin //exports".  Or, use the - form of arguments if supported.
** '''hg pull'''
** '''hg update'''
 
= Run autoconf to generate the configure scripts =
 
You'll need to repeat this step if configure.in or js/src/configure.in change; it doesn't hurt to do it too often, so I usually do this whenever I update the source tree.
 
* From /c/proj/mozilla-central:
** '''autoconf2.13'''
** '''cd js/src; autoconf2.13'''


= Set up a mozconfig =
= Set up a mozconfig =


The mozilla build system uses a mozconfig file to avoid having to pass many options to configure on the command line. Here's a sample mozconfig that I use for building:
The mozilla build system uses a "mozconfig" file to store various build-time options. Here's a sample mozconfig for Windows CE builds. Copy & paste the below into a file named "mozconfig" inside your mozilla-central directory.


mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-ff
mk_add_options MOZ_MAKE_FLAGS="-s"
  ac_add_options --enable-application=browser
  ac_add_options --enable-application=browser
   
   
Line 54: Line 43:
  ac_add_options --enable-debugger-info-modules
  ac_add_options --enable-debugger-info-modules
   
   
# Have to do libxul builds, or else the linker complains (it's buggy?)
  ac_add_options --enable-libxul
  ac_add_options --enable-libxul
ac_add_options --enable-jemalloc
ac_add_options --enable-splashscreen
ac_add_options --enable-faststripe
# buggy for ARM at the moment
ac_add_options --disable-ogg
# for ActiveX shim
export MOZ_FLASH_ACTIVEX_PATCH=1
ac_add_options --enable-activex
ac_add_options --enable-activex-scripting
ac_add_options --enable-xpconnect-idispatch
ac_add_options --disable-windows-mobile-components
   
   
  # Note that you need to give both CFLAGS and CXXFLAGS
  # Note that you need to give both CFLAGS and CXXFLAGS
  CFLAGS="-QRarch6 -QRfpe-"
  export CFLAGS="-QRarch6 -QRfpe-"
  CXXFLAGS="-QRarch6 -QRfpe-"
  export CXXFLAGS="-QRarch6 -QRfpe-"
   
   
  # No need to build the tests for now
  # No need to build the tests for now
Line 69: Line 74:
  ac_add_options --disable-printing
  ac_add_options --disable-printing
  ac_add_options --disable-oji
  ac_add_options --disable-oji
ac_add_options --disable-plugins
  ac_add_options --disable-vista-sdk-requirements
  ac_add_options --disable-vista-sdk-requirements
ac_add_options --disable-updater
  ac_add_options --disable-installer
  ac_add_options --disable-installer
ac_add_options --disable-xpinstall
ac_add_options --enable-image-decoders="png gif jpeg"
  ac_add_options --disable-dbm
  ac_add_options --disable-dbm
 
ac_add_options --disable-spellcheck
ac_add_options --disable-windows-mobile-components
  CROSS_COMPILE=1
  CROSS_COMPILE=1
  MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 9/VC/ce/bin/x86_arm/midl.exe
  MIDL=/c/Program\ Files/Microsoft\ Visual\ Studio\ 9/VC/ce/bin/x86_arm/midl.exe
Line 86: Line 83:
  ac_add_options --target=arm-wince
  ac_add_options --target=arm-wince
  ac_add_options --enable-win32-target=WINCE
  ac_add_options --enable-win32-target=WINCE
ac_add_options --enable-default-toolkit=cairo-windows
   
   
  ac_add_options --with-wince-sdk="c:/program files/windows ce tools/wce500/standardsdk_500"
  ac_add_options --with-wince-sdk="c:/program files/windows ce tools/wce500/standardsdk_500"
Copy & paste the above into a file in /c/proj, I'll call mine "mc-firefox-wince-opt".


= Start a Build =
= Start a Build =


* First, create a directory to hold the build tree.  From /c/proj:
In the location where you cloned mozilla-central, just run "make -f client.mk build". If all goes well, you should have a complete build/install dir in "dist/bin" inside your obj-ff dir.
** '''mkdir firefox-wince-opt'''
 
* Enter that directory, and run configure (note: you must specify the absolute path to the configure script; a relative path should work, but doesn't currently):
** '''cd firefox-wince-opt'''
** '''MOZCONFIG=../mc-firefox-wince-opt /c/mozilla-central/configure'''
 
* Fire off the build (the -s prevents a whole bunch of unnecessary spew from make)
** '''make -s'''
 
* If all goes well, you should have a complete build/install dir in "dist/bin" inside your firefox-wince-opt dir.


= Running the Build =
= Running the Build =


Simply copy the entire bin directory to the device, and run firefox.exe.
Copy the entire bin directory to the device, and run firefox.exe.
 
'''NOTE:''' there's a bug currently with component registration; in the bin directory, delete the file called ".autoreg" to speed up startup.
Dolske
canmove, Confirmed users
432

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/128589...175107"