MOBLIN ZONE

 Write once, run anywhere – no, this isn’t an article about Java. Our topic is the Moblin Compliance Project, which seeks to define a standard set of libraries for Moblin v2. To be compliant, OSVs (operating system vendors) must include all of those libraries and their interfaces – in the correct versions – in their distributions and on their devices.

OSV-library check: It has the extended Linux Standard Base tools that evaluate existence of correct libraries, versions and function signatures. OSV-feature check: It checks for browser features, media features, boot time, suspend-to-RAM time, battery usage, and other quality metrics.

1. Currently, Moblin AppChecker includes the following of the Linux AppChecker features: Static analysis of applications using underlying command line moblinappchk. The AppChecker allows visually customizing all the options that the tests provide. That is:
   • Moblin version to test against (only 2.0 is supported currently).
     
   • Additional shared libraries that the application depends on. moblinappchk in this case will check only external functions that cannot be resolved by any of the application's components. Visual interface for specifying the target application as a set of executable files, libraries or whole directories (similar to the usual "Browse..." dialog). Also TAR.GZ, TAR.BZ2, RPM, DEB packages as well as installed RPM or DEB packages can be selected.
2. High level command line interface (useful e.g. for automated nightly test runs).
3. Test execution and generating a human-readable report in HTML format. The report contains the list of problems encountered during testing.
4. Results history management:
   • viewing the list of all test runs on this system;
   • viewing the particular reports of any previous test run;
   • removing old reports that are no longer needed. 
5. Saving/Loading the configured options in user profiles for quick test runs in the future.

For more about how to use the tool, read the Linux App Checker Getting Started page, since there isn’t one for the Moblin App Checker yet.

Using the Tools

Once you have the tools, says Spencer, the process is straight-forward. OSVs should just run the tools against their Moblin distributions, and add or correct missing libraries.

For ISVs, the process varies, depending on whether you’re writing a new application, or if you’re porting an existing one.

If you are porting an existing Linux application, run the Moblin App Checker against it. You don’t even need to be running Moblin anywhere – the app checker is a standard Linux app. The app checker will tell you which parts of your application are not compliant.

If you’re a new developer, go grab the Moblin SDK, and set up a Moblin development environment. (Or you can simply add a few extra libraries, like glade and clutter, to your existing Linux environment. Try to get your development to be as close to Moblin as possible, and use the compliance tools to see where you need to make fixes.)

The compliance tools, Spencer explains, gives you a red light if there’s a problem, telling you which libraries, you’re missing – or if you’re using the wrong versions. ISVs are required to use the lowest version of the library. For example, python 2.6 is required by the Moblin Compliance specs. If python 2.8 comes out, you'll still have to use python 2.6 in order to maintain compliance, because you can’t assume that the devices you’re targeting will have python 2.8.

Do-It-Yourself Certification

At the present time, there is no third-party certification process for Moblin OSVs or ISVs. Run the tools yourself, fix problems that occur and pat yourself on the back if you pass. Don’t look for a “Certified Moblin v2 Compliant” logo, though, for your hardware or software. “We’re still defining the process for official certification and whether a third-party certification process could help,” says Spencer.

The Future of Certification

You may have noticed that the version number of the Compliance Project is low – 0.6, as of early June 2009. That implies that there’s going to be more work going on over the next few months – and there is.

“We’re shooting for a nearly complete spec by early August,” says Spencer. However, until there’s a final version, using the tools will help you develop your application and platforms – but you can’t claim compatibility with Moblin in your marketing. With final versions of the draft spec and tools expected by early Fall, he says, “you can claim you're compliant with the spec.”

Until then, use the tools, monitor the Moblin newsgroups, and keep an eye on the Moblin Compliance Project page. {link to http://moblin.org/compliance}

* All names and brands are the property of their respective owners.