Commit 0ee53890 authored by Christian Kandeler's avatar Christian Kandeler Committed by hjk

Remove support for Madde-based platforms.

With Nokia's decision to stop support for Harmattan applications
in their app store, the last remains of a use case have disappeared.

Change-Id: Ia036112de01c8c3a866da3529b4a941db11c7358
Reviewed-by: default avatarEike Ziller <eike.ziller@digia.com>
parent 520bd9ad
......@@ -100,10 +100,6 @@
\li Windows/MSVC
\li Microsoft Visual C++ Compiler
\li Debugging Tools for Windows/CDB
\row
\li Maemo, MeeGo
\li GCC
\li GDB
\endtable
\section2 Supported GDB Versions
......
......@@ -127,7 +127,7 @@
So if the current project is set up as a C++ application using
the MinGW toolchain targeting desktop Windows, the GDB engine will
be started in Start Internal mode. If the current project is a
QML application using C++ plugins targeting Meego
QML application using C++ plugins,
a "mixed" QML/C++ engine will be started, with the C++ parts
being handled by GDB and GDB server remote debugging.
......
......@@ -21,7 +21,7 @@
\contentspage index.html
\previouspage creator-developing-generic-linux.html
\page creator-developing-ios.html
\nextpage creator-developing-maemo.html
\nextpage creator-developing-qnx.html
\title Connecting iOS Devices
......
......@@ -28,10 +28,10 @@
\page creator-deployment-maemo.html
\nextpage creator-deployment-qnx.html
\title Deploying Applications to Linux-Based Devices
\title Deploying Applications to Embedded Linux Devices
You can specify settings for deploying applications to Linux-based devices
(Embedded Linux, MeeGo Harmattan, and Maemo 5) in the project .pro file.
You can specify settings for deploying applications to generic Linux devices
in the project .pro file.
You can view the settings in the
\gui {Run Settings}.
......@@ -90,55 +90,4 @@
without SFTP support will crash when an SFTP upload is being attempted.
This is not a bug in \QC.
\section1 Deploying on MeeGo Harmattan and Maemo 5
You can use desktop files to display icons on the home screen of the
device. To add desktop files to the project file, select \gui {Add Desktop
File}. To specify the icon file to display, select \gui {Add Launcher
Icon}. To remove desktop files and icons, delete the definitions from
the project file.
If you develop your own libraries, \QC needs to be able to find them when
you compile projects depending on them. When you install MADDE, an instance
of the device file system, called sysroot, is installed to the development
PC. Libraries are copied to sysroot during the \gui {Install Debian package
to sysroot} step.
\section1 Creating Debian Installation Packages
When you run the application on the \gui{Maemo5} or \gui Harmattan device,
\QC generates a Debian installation package in the build directory by
default. You can deliver the installation package to users for installation
on devices that are of the same type and run the same firmware as the
connected device.
\image qtcreator-maemo-deb-package.png "Create installation package"
The name of the installation package is displayed in the \gui {Package name}
field in the \gui {Create Package} step. You can change the version number
in the \gui {Package version} field.
You can specify information that users see on a delivery channel, such as
Nokia Store or Maemo.org. You can specify a short description of the
application, package name, and application icon.
The Debian control file contains an application icon in encoded form. To add
the application icon to the file, select it in the \gui {Icon to be
displayed in Package Manager} field. For more information about icon files
and adding them manually, see
\l{ http://wiki.maemo.org/Packaging#Displaying_an_icon_in_the_Application_Manager_next_to_your_package}
{Displaying an icon in the Application Manager next to your package}.
\note \QC automates this process for you.
\QC provides templates for a set of files that must be included in Debian
packages. When you start using a \l{glossary-buildandrun-kit}{kit} with
\gui Maemo5 or \gui Harmattan device type
for a project, \QC asks whether packaging files are to be added to the project and
to version control. If you plan to edit the packaging files, add them to
version control.
To edit the files, select a file in \gui {Adapt Debian file} and click
\gui Edit. The file opens in the text editor.
*/
/****************************************************************************
**
** Copyright (c) 2013 Digia Plc and/or its subsidiary(-ies).
** Contact: http://www.qt-project.org/legal
**
** This file is part of Qt Creator
**
**
** GNU Free Documentation License
**
** Alternatively, this file may be used under the terms of the GNU Free
** Documentation License version 1.3 as published by the Free Software
** Foundation and appearing in the file included in the packaging of this
** file.
**
**
****************************************************************************/
// **********************************************************************
// NOTE: the sections are not ordered by their logical order to avoid
// reshuffling the file each time the index order changes (i.e., often).
// Run the fixnavi.pl script to adjust the links to the index order.
// **********************************************************************
/*!
\contentspage index.html
\previouspage creator-build-process-customizing.html
\page creator-maemo-emulator.html
\nextpage creator-testing.html
\title Using Maemo or MeeGo Harmattan Emulator
The Maemo 5 (Fremantle) and MeeGo Harmattan emulator are installed as part
of the Qt 4 SDK. After they are installed, you can start them from \QC.
The Maemo 5 emulator emulates the Nokia N900 device environment. You can
test applications in conditions practically identical to running the
application on a Nokia N900 device with software update release 1.3
(V20.2010.36-2).
The MeeGo Harmattan emulator emulates the Nokia N9 device environment.
With the emulators, you can test how your application reacts to hardware
controls, such as the power button, and to the touch screen.
To test the application UI, user interaction with the application, and
functionality that uses the mobility APIs, use \QS,
instead. For more information, see the
\l{http://doc.qt.digia.com/qtsimulator/index.html}{\QS Manual}.
The difference between \QS and the emulators is that when you
compile your application binary for \QS, it is compiled against a
host library. The binary run on the emulator is compiled for the actual
device, using the Maemo 5 or Harmattan tool chain.
\section1 Starting the Emulator
The \gui {Start MeeGo Emulator} button is visible if you have a project
open in \QC for which you have added a \l{glossary-buildandrun-kit}{kit}
with Maemo or MeeGo Harmattan device type.
It starts the Maemo or MeeGo Harmattan emulator, depending
on the selected kit.
To start the emulator, click
\inlineimage qtcreator-maemo-emulator-button.png "Start MeeGo Emulator button"
.
Test your application on the emulator as on a device. For a list of
keyboard shortcuts that you can use to emulate keys and functions, see
\l {Emulating Device Keys}.
\section1 Rendering Graphics
The emulators support OpenGL to improve graphics rendering. Hardware
acceleration produces better results than software rendering. By default,
\QC automatically detects, whether hardware acceleration is
supported on the development PC and tries to use it. However, sometimes
the results of the automatic detection are not reliable, and
hardware acceleration might be selected even if it is actually not
available on the development PC. This causes the emulator to crash.
If the emulator crashes, you are asked whether you want to try software
rendering, instead.
To specify the OpenGL mode, select \gui {Tools > Options > Linux Devices
> MeeGo Qemu Settings}.
\section1 Emulating Device Keys
The following table summarizes the keyboard shortcuts that you can use
to emulate device keys and functions.
\table
\header
\li Device Key
\li Keyboard Shortcut
\row
\li \list
\li Alphabet keys
\li Comma (,)
\li Period (.)
\li Space
\li Arrow keys
\li Enter
\li Backspace
\endlist
\li Respective keys on the development PC keyboard.
\row
\li Shift
\li Left Shift key (Maemo 5)
Shift (Harmattan)
\row
\li Ctrl
\li Left Ctrl key (Maemo 5)
Ctrl (Harmattan)
\row
\li Mode
\li Left Alt key (Maemo 5)
Alt (Harmattan)
\row
\li Power
\li Esc
\row
\li Keypad slider open and close
\li F1
\row
\li Keypad lock (Maemo 5 only)
\li F2
\row
\li Camera lens open and close (Maemo 5 only)
\li F3
\row
\li Camera focus
\li F4
\row
\li Camera take picture
\li F5
\note The actual camera functionality is not emulated.
\row
\li Stereo headphones connect and disconnect (Maemo 5 only)
\li F6
\row
\li Volume down
\li F7
\row
\li Volume up
\li F8
\row
\li Accelerometer x axis, negative
\li 1
\row
\li Accelerometer x axis, positive
\li 2
\row
\li Accelerometer z axis, negative
\li 4
\row
\li Accelerometer z axis, positive
\li 5
\row
\li Accelerometer y axis, negative
\li 7
\row
\li Accelerometer y axis, positive
\li 8
\endtable
\note Each press of the accelerometer key turns the acceleration by 50
percent.
\section1 Closing the Emulator
To close the emulator, click the X at the top right corner of the device
emulator view. The emulator interprets this as a press of the power button
and displays the text \e {Shutting down} in the emulator window title pane.
The emulator closes shortly after this.
You can also select the \gui {Start MeeGo Emulator} button to close the
emulator. This is a faster way to close the emulator, because it does not
wait for the operating system running on the emulated machine to shut down,
but this also means that it is less safe.
*/
\section1 Running on Maemo or MeeGo Harmattan
\list 1
\li Build and run the application for \l{Running on Qt Simulator}
{\QS}.
\li Build and run the application for
\l{Using Maemo or MeeGo Harmattan Emulator}
{the Maemo or MeeGo Harmattan emulator}.
\li Alternatively, you can build and run the application for a device:
\list 1
\li Configure the device and specify a connection to it. For more
information, see \l{Connecting Maemo Devices} and
\l{Connecting MeeGo Harmattan Devices}.
\li Connect the device to the development PC.
\li Click the \gui Run button.
\endlist
\endlist
\QC uses the compiler specified in the MADDE tool chain to build the
application.
\QC generates an installation package, installs it on the device, and
executes the selected application. The application views are displayed on
the device. Command-line output is visible in the \QC
\gui {Application Output} view.
Choose \gui {Projects > Maemo Run} to view the settings for deploying the
application to the connected device and creating the installation package.
For more information, see
\l{Specifying Run Settings for Linux-Based Devices}.
Debugging also works transparently.
\section2 Specifying Run Settings for Linux-Based Devices
To run and debug an application on a Linux-based device (embedded Linux,
MeeGo Harmattan, or Maemo), you must create connections from the development
To run and debug an application on a Linux-based device,
you must create connections from the development
host to the device and add the device configurations to
\l{glossary-buildandrun-kit}{kits}. Click \gui {Manage Kits} to add devices
to kits. For more information, see
\l{Configuring Connections to Maemo Devices},
\l{Configuring Connections to Harmattan Devices}, and
\l {Connecting Embedded Linux Devices}.
When you run the application, \QC copies the files to the connected device.
For MeeGo Harmattan and Maemo device types, \QC also generates an
installation package in the build directory by default. You can deliver the
installation package to users for installation
on devices that are of the same type and run the same firmware as the
connected device. For more information, see
\l{Deploying Applications to Linux-Based Devices}.
For generic embedded Linux devices, the run settings display the path to the
The run settings display the path to the
executable file on the development host and on the device. To specify that
another application launches your application, for example, enter the
command in the \gui {Alternate executable on device} field and select the
......
/****************************************************************************
**
** Copyright (c) 2013 Digia Plc and/or its subsidiary(-ies).
** Contact: http://www.qt-project.org/legal
**
** This file is part of Qt Creator
**
**
** GNU Free Documentation License
**
** Alternatively, this file may be used under the terms of the GNU Free
** Documentation License version 1.3 as published by the Free Software
** Foundation and appearing in the file included in the packaging of this
** file.
**
**
****************************************************************************/
// **********************************************************************
// NOTE: the sections are not ordered by their logical order to avoid
// reshuffling the file each time the index order changes (i.e., often).
// Run the fixnavi.pl script to adjust the links to the index order.
// **********************************************************************
/*!
\contentspage index.html
\previouspage creator-publish-ovi-meego.html
\page creator-publishing-to-maemo-extras.html
\nextpage creator-advanced.html
\title Publishing Maemo Applications to Extras-devel
Extras is the primary repository for Maemo applications where most
community software can be found. You can browse the applications available
in Extras at \l{http://maemo.org/downloads/Maemo5/}{Maemo Downloads}.
You can publish both free and commercial applications to Extras. Free
applications must be open source and pass through a QA process.
Commercial applications are usually closed, binary only, and the publisher
is responsible for assuring their quality and security.
You can upload free applications as Debian packages to
\l{http://wiki.maemo.org/Extras-devel}{Extras-devel} at Maemo.org to share
new updates to your application and to start the community QA process.
You need a \l{http://garage.maemo.org/}{Garage} account for the uploads,
but the package itself does not need to be hosted in the Garage.
You can use the \gui {Publish for Fremantle Extras-devel Free Repository}
wizard to create a source archive and, optionally, upload it to a build
server for compiling and packaging. The package is then moved to the
Extras-devel repository. From there on, you must follow the standard
Maemo processes to get the application published to Extras.
The wizard checks that the package contains all the information that is
required to publish applications on Extras: package description and
Package Manager icon. For more information about entering this information,
see \l{Creating Debian Installation Packages}.
To use the publishing wizard:
\list 1
\li Select the \l{glossary-buildandrun-kit}{kit} with \gui {Maemo5} device type
for your project.
\li Choose \gui {Build > Publish Project}.
\li Select \gui {Publish for Fremantle Extras-devel Free Repository},
and then select \gui {Start Wizard}.
\li Select the Qt version and device type to build against and click
\gui Next.
To create a source archive without uploading it to the build
server, select the \gui {Only create source package, do not upload}
check box.
\li In the \gui {Garage account name} field, enter your login name, or
select \gui {Get an account} to create a new account.
\image qtcreator-publish-maemo-extras.png "Upload Settings dialog"
You can also select \gui {Request upload rights} to use the Maemo
Extras Assistant to validate your Garage account.
\li Select \gui Commit to select the files to include in the source
package.
\li Select \gui OK to build the source package, and optionally, publish
the application.
\endlist
*/
/****************************************************************************
**
** Copyright (c) 2013 Digia Plc and/or its subsidiary(-ies).
** Contact: http://www.qt-project.org/legal
**
** This file is part of Qt Creator
**
**
** GNU Free Documentation License
**
** Alternatively, this file may be used under the terms of the GNU Free
** Documentation License version 1.3 as published by the Free Software
** Foundation and appearing in the file included in the packaging of this
** file.
**
**
****************************************************************************/
// **********************************************************************
// NOTE: the sections are not ordered by their logical order to avoid
// reshuffling the file each time the index order changes (i.e., often).
// Run the fixnavi.pl script to adjust the links to the index order.
// **********************************************************************
/*!
\contentspage index.html
\previouspage creator-publish-ovi.html
\page creator-publish-ovi-maemo.html
\nextpage creator-publish-ovi-meego.html
\title Publishing Qt Content for Maemo Devices
The applications that you publish on Nokia Store, must meet the testing
criteria listed in
\l{http://www.developer.nokia.com/info/sw.nokia.com/id/9cd1eb18-821b-4228-a0a3-36b049c5d608/Maemo_5_Application_OVI_Store_Entry_Requirements.pdf.html}
{Maemo 5 Applications: Nokia Store Entry Requirements}.
Make sure that your application passes the following most commonly
failed test cases:
\list
\li Package filename must include the application name and version
number using three digits. For example: myapplication_1_0_1.deb
\li Application files must be installed to the opt folder on the ext3
partition.
\li Debian packages must be given the category user/hidden.
\li Application cannot crash or hang during use.
\li The application must handle different memory situations correctly.
\endlist
You set the application name and installation folder in the
\gui {Run Settings} for the project. For more information, see
\l{Deploying Applications to Linux-Based Devices}. \QC
specifies the correct category settings by default when it creates the
Debian directory and the necessary files.
You can test the application on \QS and Maemo emulator to make
sure that it does not crash or hang and to check how it handles different
memory situations. Before you submit the application to Nokia Publish, you
must also fully test it on a Maemo device.
*/
/****************************************************************************
**
** Copyright (c) 2013 Digia Plc and/or its subsidiary(-ies).
** Contact: http://www.qt-project.org/legal
**
** This file is part of Qt Creator
**
**
** GNU Free Documentation License
**
** Alternatively, this file may be used under the terms of the GNU Free
** Documentation License version 1.3 as published by the Free Software
** Foundation and appearing in the file included in the packaging of this
** file.
**
**
****************************************************************************/
// **********************************************************************
// NOTE: the sections are not ordered by their logical order to avoid
// reshuffling the file each time the index order changes (i.e., often).
// Run the fixnavi.pl script to adjust the links to the index order.
// **********************************************************************
/*!
\contentspage index.html
\previouspage creator-publish-ovi-maemo.html
\page creator-publish-ovi-meego.html
\nextpage creator-publishing-to-maemo-extras.html
\title Publishing Qt Content for MeeGo Harmattan Devices
The applications that you publish to Nokia Store, must meet the
\l{http://www.developer.nokia.com/info/sw.nokia.com/id/44affcd1-ceba-4aca-8b65-670ce2cbbd1e/MeeGo_1_2_Harmattan_Applications_Ovi_Store_Entry_Requirements.html}
{MeeGo 1.2 Harmattan Applications: Nokia Store Entry Requirements}.
*/
......@@ -29,7 +29,7 @@
debug, and analyze applications on them from \QC.
If you have a tool chain for building applications for embedded Linux
devices (with no MADDE support) installed on the development PC, you can add
devices installed on the development PC, you can add
it to \QC. You can then select a \l{glossary-buildandrun-kit}{kit}
with \gui {Embedded Linux} device type to
build and run applications on embedded Linux devices.
......@@ -115,9 +115,10 @@
When you run the project, \QC deploys the application as specified by the
deploy steps. By default, \QC copies the application files to the device.
For more information, see \l{Deploying Applications to Linux-Based Devices}.
For more information, see \l{Deploying Applications to Embedded Linux Devices}.
\endlist
\include linux-mobile/linuxdev-keys.qdocinc