Packaging XULRunner for Songbird
Table of contents
- 1. Wrap Up
This page assumes you have followed the steps on the Build XULRunner for Songbird page and you now built XULRunner tree.
Songbird needs two items from the xulrunner directory:
- The compiled XULRunner binary, and
- the Mozilla SDK needed to compile Songbird code.
If you've built these successfully, in your SB_VENDOR_BUILD_ROOT directory, there will be a directory containing the platform string for your build.
On all non-Win32 platforms, these will be symlinks to packages you've not built, so the mozilla and xulrunner directories should not be symlinks; if they are, something has gone wrong. On Win32-platforms, these directories are copied.
To build a Songbird build against a custom-built xulrunner, point your dependencies/$platform directory to SB_VENDOR_BUILD_ROOT/$platform directory (either via a symlink on non-Win32 platforms, or with a full copy on Win32).
Wrap Up
You now have a full Songbird build from the ground up (besides the plugins and playback cores etc...). Go into your songbird/compiled/dist folder and let The Bird sing!!
Now that you have gotten this far, flutter over to Songbird's Bugzilla and find yourself a bug to start playing with. You can start by just verifying any unconfirmed bugs if you like, or dive right in and try hacking some code. See you in IRC ( #songbird at irc.mozilla.org )
make -f songbird.mk debug
some reason, the make file wants to look in the release directory when running a python script. cause release is not built or packaged yet, it doesn't exist; note: i'm going by example and building the debug version.
here's the error: /System/Library/Frameworks/Python.framework/Versions/2.5/Resources/Python.app/Contents/MacOS/Python: can't open file '/Users/lemon/tamago/dev/sbird/trunk/dependencies/macosx-i686/mozilla/release/scripts/printconfigsetting.py': [Errno 2] No such file or directory
i didn't copy all the error messages; they're all the same.
i checked out the dependencies to get the release, and i'm rebuilding it now, same command; so far, so good.
so...it's strannge the build would be dependent on a script in release? edited 19:53, 29 Jun 2008