Difference between revisions of "User:Sardisson/Building with mozilla-central"

From Camino Wiki
Jump to navigation Jump to search
(update for core required toolkit bits that are apparently still defaulted off)
(updates from Kai)
Line 1: Line 1:
 
To start building Camino against Gecko 1.9.n, n>0, a number of basic build-config changes will be required.
 
To start building Camino against Gecko 1.9.n, n>0, a number of basic build-config changes will be required.
  
−
To get started, pull mozilla-central (or mozilla-1.9.x) from Hg and pull mozilla/camino from cvs into the Hg checkout. '''N.B.''' If you are building mozilla-central, you will need to adjust your .mozconfig to use gcc-4.2, Mac OS X 10.5 sdk, and a target of Mac OS X 10.5, the defaults on that branch.
+
==Checkout and mozconfig==
 +
 
 +
To get started, pull mozilla-central (or mozilla-1.9.x) from Hg and pull mozilla/camino from cvs into the Hg checkout. You also need to pull mozilla/extensions/typeaheadfind from cvs into the Hg checkout.
 +
 
 +
'''N.B.''' If you are building mozilla-central, you will need to adjust your .mozconfig to use gcc-4.2, Mac OS X 10.5 sdk, and a target of Mac OS X 10.5, the defaults on that branch.
 +
 
 +
==Build-config changes in mozilla/camino==
  
−
# In <code>camino/confvars.sh</code>, comment out the <code>MOZ_EXTENSIONS_DEFAULT=" typeaheadfind"</code> line.
 
−
#: This can probably be fixed by pulling extensions/typeaheadfind from cvs into the appropriate location; not having typeaheadfind will cause the Camino build to error at some point, probably before packaging.
 
−
#: XXXtodo: See if we can set the app name to Camino
 
−
#: XXXtodo: What other changes from [http://inspiral.s3.amazonaws.com/camino192/build-essential.txt hendy's confvars.sh] are required to get the right Gecko build (e.g., MOZ_PLACES and MOZ_MORKREADER)
 
 
# In <code>camino/build.mk</code>, remove "embedding/config" from the "tier_app_dirs" rule
 
# In <code>camino/build.mk</code>, remove "embedding/config" from the "tier_app_dirs" rule
 
# Add a new file, <code>camino/app-config.mk</code>, that looks like [http://mxr.mozilla.org/comm-central/source/suite/app-config.mk this], with <code>s/SUITE/MACBROWSER/g</code>
 
# Add a new file, <code>camino/app-config.mk</code>, that looks like [http://mxr.mozilla.org/comm-central/source/suite/app-config.mk this], with <code>s/SUITE/MACBROWSER/g</code>
Line 19: Line 21:
  
 
The above changes should allow you to make it into the xcodebuild phase of the Camino build; at this point, real errors should start appearing!
 
The above changes should allow you to make it into the xcodebuild phase of the Camino build; at this point, real errors should start appearing!
 +
 +
==To do==
 +
# In <code>camino/confvars.sh</code>
 +
#: XXXtodo: See if we can set the app name to Camino
 +
#: XXXtodo: What other changes from [http://inspiral.s3.amazonaws.com/camino192/build-essential.txt hendy's confvars.sh] are required to get the right Gecko build (e.g., MOZ_PLACES)
 +
# mozconfig - export MOZ_DEBUG_SYMBOLS for NSS ({{bug|468701}})

Revision as of 09:55, 11 October 2009

To start building Camino against Gecko 1.9.n, n>0, a number of basic build-config changes will be required.

Checkout and mozconfig

To get started, pull mozilla-central (or mozilla-1.9.x) from Hg and pull mozilla/camino from cvs into the Hg checkout. You also need to pull mozilla/extensions/typeaheadfind from cvs into the Hg checkout.

N.B. If you are building mozilla-central, you will need to adjust your .mozconfig to use gcc-4.2, Mac OS X 10.5 sdk, and a target of Mac OS X 10.5, the defaults on that branch.

Build-config changes in mozilla/camino

  1. In camino/build.mk, remove "embedding/config" from the "tier_app_dirs" rule
  2. Add a new file, camino/app-config.mk, that looks like this, with s/SUITE/MACBROWSER/g
  3. In camino/Makefile.in
    1. Remove "flashblock" and "pinstripe" from the "DIRS" variable.
      This disables flashblock, which will have to be disabled until it is made to use the new toolkit chrome manifests, and pinstripe, which will largely be obsolete but which will need to be adapted to do the new-style toolkit chrome override stuff for the app-license stuff.
    2. Remove the following lines from the "libs::" rule:
      $(RSYNC_ALL) $(srcdir)/embed-replacements/ embed-replacements.tmp
      cd embed-replacements.tmp && \
       $(ZIP) -r0DX ../../dist/Embed/chrome/embed.jar *
      This disables embed-replacements, which will have to be reworked for the new toolkit jar structure, or turned into new-style toolkit chrome overrides along with the app-license stuff in pinstripe.

The above changes should allow you to make it into the xcodebuild phase of the Camino build; at this point, real errors should start appearing!

To do

  1. In camino/confvars.sh
    XXXtodo: See if we can set the app name to Camino
    XXXtodo: What other changes from hendy's confvars.sh are required to get the right Gecko build (e.g., MOZ_PLACES)
  2. mozconfig - export MOZ_DEBUG_SYMBOLS for NSS (Bug 468701)
Retrieved from "http://wiki.caminobrowser.org/index.php?title=User:Sardisson/Building_with_mozilla-central&oldid=10406"