Editing Documentation/Maemo 5 Developer Guide/Porting Software/Introduction

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Learn more about Contributing to the wiki.

The following code examples are used in this chapter:

* [https://vcs.maemo.org/svn/maemoexamples/tags/maemo_5.0/maemo-sliders/ maemo-sliders]
* [https://vcs.maemo.org/svn/maemoexamples/tags/maemo_5.0/maemopad/ MaemoPad]
* [https://vcs.maemo.org/svn/maemoexamples/tags/maemo_5.0/hildon-examples/ hildon-examples]

Much effort has been made in the design of Maemo platform to allow for easy porting of regular GNU/Linux desktop software to the mobile maemo environment. An earlier chapter in this guide explained the basic tools that ease cross-compilation and help coping with the GNU autotools. This chapter gives pointers to the relevant guides focusing on the differences in the application programming and user interfaces.

== Command Line Programs ==

In most cases, porting software with no user interface is trivial and straightforward. First, the source code of a program is unpacked to the home directory of a Scratchbox user. Second, inside the ARMEL target <code>configure</code> and <code>make</code> are run. Then the compiled program can be tested on the device. Finally the software needs to be packaged so it can be distributed.

== Programs with Graphical User Interface ==

Porting of applications which use GTK+ starts the same way as described above. In addition, the user interface needs to be re-factored to use Hildon instead of directly using GTK+, this process is often called "hildonization". If the application uses any components not available in the maemo SDK, these must be also ported by the developer. In short, the developer is responsible for all library dependencies needed that are not already in the SDK.

Section [[Documentation/Maemo 5 Developer Guide/Porting Software/Porting Existing GTK+ Application to Maemo 5 | Porting Existing GTK+ Application to Maemo 5]] goes into the necessary details of porting an existing GTK+ application to maemo environment.

[[Category:Development]]
[[Category:Documentation]]
[[Category:Fremantle]]

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Retrieved from "http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Porting_Software/Introduction"

Personal tools

Navigation

Views

Editing Documentation/Maemo 5 Developer Guide/Porting Software/Introduction

@@ Line 5: / Line 5: @@
 * [https://vcs.maemo.org/svn/maemoexamples/tags/maemo_5.0/hildon-examples/ hildon-examples]
-Much effort has been made in the design of Maemo platform to allow for easy porting of regular GNU/Linux desktop software to the mobile Maemo environment. An earlier chapter in this guide explained the basic tools that ease cross-compilation and help coping with the GNU autotools. This chapter gives pointers to the relevant guides focusing on the differences in the application programming and user interfaces.
+Much effort has been made in the design of Maemo platform to allow for easy porting of regular GNU/Linux desktop software to the mobile maemo environment. An earlier chapter in this guide explained the basic tools that ease cross-compilation and help coping with the GNU autotools. This chapter gives pointers to the relevant guides focusing on the differences in the application programming and user interfaces.
 == Command Line Programs ==
@@ Line 13: / Line 14: @@
 == Programs with Graphical User Interface ==
-Porting of applications which use GTK+ starts the same way as described above. In addition, the user interface needs to be re-factored to use Hildon instead of directly using GTK+, this process is often called "hildonization". If the application uses any components not available in the Maemo SDK, these must be also ported by the developer. In short, the developer is responsible for all library dependencies needed that are not already in the SDK.
+Porting of applications which use GTK+ starts the same way as described above. In addition, the user interface needs to be re-factored to use Hildon instead of directly using GTK+, this process is often called "hildonization". If the application uses any components not available in the maemo SDK, these must be also ported by the developer. In short, the developer is responsible for all library dependencies needed that are not already in the SDK.
-Section [[Documentation/Maemo 5 Developer Guide/Porting Software/Porting Existing GTK+ Application to Maemo 5|Porting Existing GTK+ Application to Maemo 5]] goes into the necessary details of porting an existing GTK+ application to maemo environment.
+Section [[Documentation/Maemo 5 Developer Guide/Porting Software/Porting Existing GTK+ Application to Maemo 5 | Porting Existing GTK+ Application to Maemo 5]] goes into the necessary details of porting an existing GTK+ application to maemo environment.
 [[Category:Development]]
 [[Category:Documentation]]
 [[Category:Fremantle]]