We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

How do we make "Qt on Mer" the solution of choice for device vendors?

Formal Metadata

Title
How do we make "Qt on Mer" the solution of choice for device vendors?
Title of Series
Number of Parts
90
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Covering Mer's birth, the MeeGo years and how we now work in a truly collaborative and open project to make Mer productizable. Mer supports organizational collaboration; our vendor focus drove the design from the project structure through the architecture, the deliverables and the processes. We continuously ask "How will this decision affect vendors using our solution to make a product?" Mer delivers a world-class platform for building products: after all, it's an ultra-modern Linux stack with a strong upstream focus that partners with a world-class graphical framework; it rocks! I'll explain why "code is not enough"; what else we deliver and how we ensure that the code, policies and processes you tell your customers to use are up to the job. Then the details of Mer and QtCreator; how the cross-compilation and emulation works in the Mer SDK. Finally some future goals for Mer and our collaborators and a demonstration of some technology that is guaranteed to be of interest to people looking to build Qt products now, on hardware shipping today.