Der Firefox OS desktop client, auch bekannt als B2G desktop client, bietet die Möglichkeit an Gaia and Web apps in einer Gecko-basierten Umgebung auf dem Desktop laufen zu lassen. Dabei wird die Geräte-Hardware jedoch nicht emuliert, sodass es zum Testen von Geräte-Api nicht taugt. Auch ist es kein Ersatz um auf einem Gerät zu testen. Dennoch, hat es einige aktivierte APIs, welche nicht im Firefox verfügbar sind, wie z.B. Kontakt- und Einstellungs-API. Es kann also durchaus nützlich sein, wenn man eine Anwendung entwickelt oder während man am Gaia-Inteface direkt arbeitet. Dieser Artikel behandelt das Downloaden bzw. zusammenbauen des Firefox OS Desktop Clients, jedoch auch wie man ihn benutzt.
Note: The easiest way to use the Firefox OS desktop client is to use the Firefox OS Simulator. It does not require you to build the desktop client yourself.
Note: Firefox OS version 1.0 is based on a branch of Gecko 18. There are also nightly builds based on
Just like Firefox Nightlies, the Firefox OS desktop client is built every day from the latest source code. The latest build is available from the Mozilla FTP server. Be sure to pick the latest version and the right archive for your operating system. This lets you bypass having to build it yourself. In addition, you don't have to download Gaia on your own either.
Be sure to install the application in a writeable location; the application needs to be able to update included the Gaia profile.
You can now skip ahead to Running the desktop client, unless you actually want to build it for yourself.
The first thing we need to do is set up a standard Mozilla build environment. Once we have that, we can pull down the code we'll need and configure to build the Firefox OS desktop client.
In a directory where we'd like the source code to go, let's clone the
mozilla-central repository that contains all of Gecko:
hg clone http://hg.mozilla.org/mozilla-central
When we do subsequent builds later, we'll want to make sure we have the latest code. Here's how to pull the latest changes:
cd mozilla-central hg pull -u
Next, we need to create a
mozconfig file in the
mozilla-central directory to configure the build system to build the Boot to Gecko client instead of Firefox:
. "$topsrcdir/b2g/config/mozconfigs/common" mk_add_options MOZ_OBJDIR=../build mk_add_options MOZ_MAKE_FLAGS="-j9 -s" ac_add_options --enable-application=b2g ac_add_options --disable-libjpeg-turbo # This option is required if you want to be able to run Gaia's tests ac_add_options --enable-tests # turn on mozTelephony/mozSms interfaces # Only turn this line on if you actually have a dev phone # you want to forward to. If you get crashes at startup, # make sure this line is commented. #ac_add_options --enable-b2g-ril
Now we're ready to build the desktop client with the following command issued from the
make -f client.mk
The built client will be placed in the
../build/dist directory (based on the value you specify for
MOZ_OBJDIR in the
By default the desktop client will show an empty screen because it doesn't know which Web app to load initially as the system app. The collection of system apps and default apps that come with Firefox OS is called Gaia.
To download Gaia for the first time, let's clone the source code repository on GitHub:
git clone https://github.com/mozilla-b2g/gaia cd gaia
To update an already existing clone of Gaia, we can pull in the latest changes from GitHub:
cd gaia git pull
Next we need to set up Gaia's apps for the desktop client. This includes packaging the Gaia apps in the same way like they would be installed on the device, as well as setting up the permissions for the privileged system apps. We do this by generating a profile. The following command (run in the
gaia directory) will take care of that:
This should create a
profile-debug directory below the
gaia directory. The new profile contains a customized extension and other configuration needed to make B2G run properly.
Once you've built the client and downloaded Gaia (or downloaded and installed the nightly desktop application), you're ready to fire up the Firefox OS desktop client.
To run the desktop client on Linux using the embedded Gaia profile, just run the
b2g executable. If you want to specify a different Gaia profile, you need to bypass the
b2g wrapper program and run the
b2g-bin binary. The binary is in the archive you downloaded earlier or in the
../build/dist/bin directory if you built the client yourself.
.../b2g-bin -profile gaia/profile-debug
You may experience annoying rendering problems. To avoid them, add the following line to your
If you downloaded the nightly build, you can simply launch it from the Finder as usual. Any console output is visible by running the standard Console utility program included with your Mac.
If you want to specify a different Gaia profile, you need to bypass the
b2g wrapper program and run the
b2g-bin binary. The command line is slightly more complicated due to the location of the
b2g-bin binary and the need for absolute paths when specifying the profile directory:
.../B2G.app/Contents/MacOS/b2g-bin -profile /full/path/to/gaia/profile-debug
Running the nightly build on Windows is as simple as launching
b2g.exe. If you want to customize the execution, you can do so by running the
b2g-bin.exe executable instead; this bypasses the wrapper program that automatically uses the bundled Gaia.
There are a number of command line options you can use to adjust the runtime experience while using the desktop client. You can get a list by using the
-help option. This section covers some of the particularly interesting ones.
You can specify the screen size of the device you want to simulate using the
Where <width>, <height>, and <dpi> are fairly self-explanatory parameters: the width and height of the device's screen in pixels and the device resolution in DPI. For example:
b2g --screen=320x480 b2g --screen=320x480@160
Optionally, you can specify certain devices by name to simulate their screen size and resolution:
-jsconsole flag. After building, just do:
.../b2g -jsconsole -profile /path/to/your/profile
If you've installed the nightly build on a Mac, you can do the following:
/Applications/B2G.app/Contents/MacOS/b2g-bin -jsconsole -profile /path/to/your/profile-debug
Note: On production builds of Firefox OS, console logging (such as by
console.log()) is disabled by default. In order to enable it, open the Settings app and navigate down through Device Information->More Information->Developer, then toggle on the "Console Enabled" preference.
You can now specify an application to be launched automatically when b2g starts up in the desktop client. This is done as soon as the rest of the system is done loading up. To do this, just use the
--runapp option, which takes as a parameter the name of the application to run. For example:
.../b2g-bin -profile /path/to/your/gaia/profile-debug --runapp email
Before looking for an app to launch, the specified name is normalized by converting it to all lower case and removing all dashes and spaces. This normalized name is then compared to similarly normalized names from the manifests of available apps' manifests.
For example, the name of the email app is currently "E-mail", but
--runapp email will work because of this normalization.
If you specify the
--runapp option without an argument, or with an empty argument, the b2g client will output to your terminal a list of the known applications as well as a brief usage message.
Note: Using the
--runapp option disables the lock screen as a side effect and does not re-enable it. It's assumed that you won't use this command on a profile on which you will be testing the lock screen, or you will turn it back on manually in Settings application. Feel free to contribute a patch to change this behavior if it's a problem.
This section provides a few helpful tips to using the B2G desktop client.
- ESC key performs the same function as the "back" button.
- Home key performs the same function as the "home" button; if you're on a Mac, Home key is available as Fn+← (Fn + Left Arrow).
- End key performs the same function as the "power" button; if you're on a Mac, End key is available as Fn+→ (Fn + Right Arrow).
- Page Up and Page Down keys perform the same function as "Volume Up" and "Volume Down" buttons respectively; if you're on a Mac, Page Up key is available as Fn+↑ (Fn + Up Arrow) and Page Down key is available as Fn+↓ (Fn + Down Arrow).
- Long press to Home key opens the "Card View"; if you're on Mac, Cmd+Fn+← (Cmd + Fn + Left Arrow) opens the "Card View".