This repo should contain everything needed to build a BonjourFoxy release from scratch. If you redistribute BonjourFoxy please change all the identifiers in the to be unique. That includes but is no limited to the names and UUID's used by the binary components. If you do not want to rebuild the binary components then specify BonjourFoxy as a dependency in your extension (see 'Extension Dependencies' on the mozilla wiki for details).
ext- Chrome skeleton (component, content, etc)src- XPCOM component source codesrc/#.#- Component intermediary/output folderscratch- Staging foldersdk/archive- XULRunner SDK archivessdk/#.#- The active XULRunner SDK for a given release
You can populate sdk/archive using the get-xr.sh shell script which takes a XULRunner release as it sole argument. You will likely want to alter the script to point at your local Mozilla mirror unless you have good connectivity to Internode (in Australia). Example use:
- ./get-xr.sh 1.9.0.15
- ./get-xr.sh 1.9.1.4
- ./get-xr.sh 1.9.2b1
switch-xr.sh is used to activate an SDK for use with a given Firefox release. It takes a Firefox release and a XULRunner SDK release as it's arguments. Example use:
- ./switch-xr.sh 3.0 1.9.0.15
- ./switch-xr.sh 3.5 1.9.1.4
- ./switch-xr.sh 3.6 1.9.2b1
If you've installed the 'Developer Tools' and the 10.5 SDK (you can build against 10.6 only if you want, just update src/darwin.inc) you should be right to go.
- Visual Studio (I've used 2008, I assume it'd work with other releases)
- Cygwin install including Perl and GNU Make
- Bonjour SDK (in default directory, otherwise you'll need to update
src/cygwin.inc)
Make targets:
xpcom- build components for the current platformdir- copies the extension skeleton and any built XPCOM components into thescratchfolder and updates the install.rdfxpi- creates an XPI from the contents of thescratchdirectorynixdir- build nix source foldernixball- build nix source tarballall- build a full releaseclean- clean up
Variables:
FF_RELS- the releases to build againstBF_REL- the BonjourFoxy release being builtMIN_VER- the minimum supported Firefox release (used to update install.rdf)MAX_VER- the maximum supported Firefox release (used to update install.rdf)
Move to the src/ folder Run dpkg-buildpackage -rfakeroot (you may need to install several debian and firefox (xulrunner)-related development packages in order to successfulluy build the .deb package We the package is built, a new .deb file will be created in the src/ folder, you can either install it manually: dpkg -i firefox-libbonjourfoxy_0.8.0-1_i386.deb Or use gdebi for example to solve dependencies if needed: gdebi firefox-libbonjourfoxy_0.8.0-1_i386.deb
The .deb package will contain both the XPCOM libraries+the firefox extension, and will directly install bonjourfoxy for all users. The script in debian/adaptdistrib adapts dependencies for the correct xulrunner and iceweasel/firefox version used to build the XPCOM. It will also name the package according to the distribution (Iceweasel/Firefox for Debian/Ubuntu respectively) The debian build process will use the nix target and Makefile.nix to compile the XPCOM component The environment detected during compilation time is stored in a file located at nix/bonjourfoxy-*/build_ff_ver.inc
Create a file called '[email protected]' in your Firefox Profile's extension folder that contains the path to the scratch directory, eg: /Users/atj/Projects/bonjourfoxy/scratch or B:\scratch.
BonjourFoxy can be built against Avahi's Bonjour compatibility layer. At the moment this can be done by first building the nixdir target and then running make again from nixdir folder (as I'm only going to do source releases for nix it's convenient for me). The Makefile produced by nixdir is sourced from src/Makefile.nix and has only been briefly tested on Ubuntu, Debian and Fedora. If you'd like to package BonjourFoxy for a particular OS feel free to contact me.