Packaging Qt Creator Apps for Maemo Extras - Revision history

imported_>tetris11: /* Using the Wizard */

2011-07-10T04:05:34Z

Using the Wizard

← Older revision		Revision as of 04:05, 10 July 2011
Line 6:		Line 6:

	===Using the Wizard===		===Using the Wizard===
	With QtSDK 1.1, all you need to do is go to Build-> Publish Project... --> Start Wizard.		With QtSDK 1.1, all you need to do is go to Build-> Publish Project... --> Start Wizard. As shown [http://doc.qt.nokia.com/qtcreator-2.2/creator-publishing-to-maemo-extras.html here].

	You can then choose to upload your app directly to the repository using your [https://garage.maemo.org/ maemo garage] account, or you can do the more straightforward approach of choosing not to upload through QtSDK (make sure that the "do not upload" box is ticked) and instead uploading the generated files using [https://garage.maemo.org/extras-assistant/index.php Maemo Extras Assistant] (check your /tmp/qtc_packing_appname/ folder for the .changes, .tar.gz and .dsc files).		You can then choose to upload your app directly to the repository using your [https://garage.maemo.org/ maemo garage] account, or you can do the more straightforward approach of choosing not to upload through QtSDK (make sure that the "do not upload" box is ticked) and instead uploading the generated files using [https://garage.maemo.org/extras-assistant/index.php Maemo Extras Assistant] (check your /tmp/qtc_packing_appname/ folder for the .changes, .tar.gz and .dsc files).

imported_>tetris11: /* Issues */

2011-06-21T06:36:37Z

Issues

← Older revision		Revision as of 06:36, 21 June 2011
Line 11:		Line 11:

	====Issues====		====Issues====
	Some developers have encountered problems with the debian/rules file using this method, in which case it should be noted that one working solution is to uncomment the "qmake PREFIX=/usr" and "dh_shlibdeps" lines in the rules file (as suggested by notation in the actual file itself). Another common solution is to check that each line of the rules file is indented with TABS not spaces.		Some developers have encountered problems with the debian/rules file using this method, in which case it should be noted that one working solution is to uncomment the "qmake PREFIX=/usr" and "dh_shlibdeps" lines in the rules file (as suggested by notation in the actual file itself). Another common solution is to check that each line of the rules file is indented with TABS and not spaces.

	===Using Custom Build Steps===		===Using Custom Build Steps===

imported_>tetris11: /* Using Custom Processes */

2011-06-21T06:35:55Z

Using Custom Processes

← Older revision		Revision as of 06:35, 21 June 2011
Line 13:		Line 13:
	Some developers have encountered problems with the debian/rules file using this method, in which case it should be noted that one working solution is to uncomment the "qmake PREFIX=/usr" and "dh_shlibdeps" lines in the rules file (as suggested by notation in the actual file itself). Another common solution is to check that each line of the rules file is indented with TABS not spaces.		Some developers have encountered problems with the debian/rules file using this method, in which case it should be noted that one working solution is to uncomment the "qmake PREFIX=/usr" and "dh_shlibdeps" lines in the rules file (as suggested by notation in the actual file itself). Another common solution is to check that each line of the rules file is indented with TABS not spaces.

	===Using Custom ~~Processes~~===		===Using Custom Build Steps===
	Another way to generate the .changes, .tar.gz and .dsc files is to add a custom step to the build configuration . This is outlined [http://qt-funk.blogspot.com/2011/02/generating-maemoorg-compatible-source.html here] and [http://raeda.blog.com/2011/02/19/upload-qt-apps-to-extras-devel-from-windows/ here]		Another way to generate the .changes, .tar.gz and .dsc files is to add a custom step to the build configuration . This is also a fairly straightforward process and is outlined [http://qt-funk.blogspot.com/2011/02/generating-maemoorg-compatible-source.html here] and [http://raeda.blog.com/2011/02/19/upload-qt-apps-to-extras-devel-from-windows/ here]

	== Qt Creator Notes ==		== Qt Creator Notes ==

imported_>tetris11: /* Is there a simple(r) way ? */

2011-06-21T06:33:28Z

Is there a simple(r) way ?

← Older revision		Revision as of 06:33, 21 June 2011
Line 12:		Line 12:
	====Issues====		====Issues====
	Some developers have encountered problems with the debian/rules file using this method, in which case it should be noted that one working solution is to uncomment the "qmake PREFIX=/usr" and "dh_shlibdeps" lines in the rules file (as suggested by notation in the actual file itself). Another common solution is to check that each line of the rules file is indented with TABS not spaces.		Some developers have encountered problems with the debian/rules file using this method, in which case it should be noted that one working solution is to uncomment the "qmake PREFIX=/usr" and "dh_shlibdeps" lines in the rules file (as suggested by notation in the actual file itself). Another common solution is to check that each line of the rules file is indented with TABS not spaces.


	===Using Custom Processes===		===Using Custom Processes===

imported_>tetris11: /* Is there a simple(r) way ? */

2011-06-21T06:32:36Z

Is there a simple(r) way ?

@@ Line 3: / Line 3: @@
 == Is there a simple(r) way ? ==
-Note that the instructions on this page apply to QtSDK 1.0.x and QtCreator 2.0.x. The use of the [http://labs.qt.nokia.com/2011/03/01/qt-sdk-1-1-beta-released/ QtSDK 1.1] is strongly encouraged, as it has incorporated/automated most of the steps outlined below. With QtSDK 1.1, all you need to do is outlined [http://qt-funk.blogspot.com/2011/02/generating-maemoorg-compatible-source.html here] and [http://raeda.blog.com/2011/02/19/upload-qt-apps-to-extras-devel-from-windows/ here]
+Note that the instructions on this page apply to QtSDK 1.0.x and QtCreator 2.0.x. The use of the [http://labs.qt.nokia.com/2011/03/01/qt-sdk-1-1-beta-released/ QtSDK 1.1] is strongly encouraged, as it has incorporated/automated most of the steps outlined below.
 == Qt Creator Notes ==

82.43.67.196: /* Is there a simple(r) way ? */

2011-03-16T19:26:45Z

Is there a simple(r) way ?

← Older revision		Revision as of 19:26, 16 March 2011
Line 3:		Line 3:
	== Is there a simple(r) way ? ==		== Is there a simple(r) way ? ==

	Note that the instructions on this page apply to QtSDK 1.0.x and QtCreator 2.0.x. The use of the [http://labs.qt.nokia.com/2011/03/01/qt-sdk-1-1-beta-released/ QtSDK 1.1] is strongly encouraged, as it has incorporated/automated most of the steps outlined below. With QtSDK 1.1, all you need to do is outlined [http://qt-funk.blogspot.com/2011/02/generating-maemoorg-compatible-source.html here]		Note that the instructions on this page apply to QtSDK 1.0.x and QtCreator 2.0.x. The use of the [http://labs.qt.nokia.com/2011/03/01/qt-sdk-1-1-beta-released/ QtSDK 1.1] is strongly encouraged, as it has incorporated/automated most of the steps outlined below. With QtSDK 1.1, all you need to do is outlined [http://qt-funk.blogspot.com/2011/02/generating-maemoorg-compatible-source.html here] and [http://raeda.blog.com/2011/02/19/upload-qt-apps-to-extras-devel-from-windows/ here]

	== Qt Creator Notes ==		== Qt Creator Notes ==

imported_>achipa: /* There must be a simpler way */

2011-03-07T09:03:48Z

There must be a simpler way

← Older revision		Revision as of 09:03, 7 March 2011
Line 1:		Line 1:
	While there are a few pages relating to packaging Maemo and Qt apps, this document is designed to provide step-by-step instructions for taking a working app in Qt Creator and publishing it to the Maemo [[extras]] development repository for all to enjoy. The methods here have been tested with basic Qt apps in an Ubuntu Linux environment. Hopefully additional feedback and edits will provide information about working on the lesser platforms available, for example Windows and Mac.		While there are a few pages relating to packaging Maemo and Qt apps, this document is designed to provide step-by-step instructions for taking a working app in Qt Creator and publishing it to the Maemo [[extras]] development repository for all to enjoy. The methods here have been tested with basic Qt apps in an Ubuntu Linux environment. Hopefully additional feedback and edits will provide information about working on the lesser platforms available, for example Windows and Mac.

	== ~~There must be~~ a ~~simpler~~ way ==		== Is there a simple(r) way ? ==

	Note that the instructions on this page apply to QtSDK 1.0.x and QtCreator 2.0.x. The use of the [http://labs.qt.nokia.com/2011/03/01/qt-sdk-1-1-beta-released/ QtSDK 1.1] is strongly encouraged, as it has incorporated/automated most of the steps outlined below. With QtSDK 1.1, all you need to do is outlined [http://qt-funk.blogspot.com/2011/02/generating-maemoorg-compatible-source.html here]		Note that the instructions on this page apply to QtSDK 1.0.x and QtCreator 2.0.x. The use of the [http://labs.qt.nokia.com/2011/03/01/qt-sdk-1-1-beta-released/ QtSDK 1.1] is strongly encouraged, as it has incorporated/automated most of the steps outlined below. With QtSDK 1.1, all you need to do is outlined [http://qt-funk.blogspot.com/2011/02/generating-maemoorg-compatible-source.html here]

imported_>achipa: /* There must be a simpler way */

2011-03-07T09:03:27Z

There must be a simpler way

← Older revision		Revision as of 09:03, 7 March 2011
Line 3:		Line 3:
	== There must be a simpler way ==		== There must be a simpler way ==

	~~Foreword: These~~ instructions apply ~~you~~ QtSDK 1.0.x and QtCreator 2.0.x. The use of the [http://labs.qt.nokia.com/2011/03/01/qt-sdk-1-1-beta-released/ QtSDK 1.1] is strongly encouraged, as it has incorporated/automated most of the steps outlined below. With QtSDK 1.1, all you need to do is outlined [http://qt-funk.blogspot.com/2011/02/generating-maemoorg-compatible-source.html here]		Note that the instructions on this page apply to QtSDK 1.0.x and QtCreator 2.0.x. The use of the [http://labs.qt.nokia.com/2011/03/01/qt-sdk-1-1-beta-released/ QtSDK 1.1] is strongly encouraged, as it has incorporated/automated most of the steps outlined below. With QtSDK 1.1, all you need to do is outlined [http://qt-funk.blogspot.com/2011/02/generating-maemoorg-compatible-source.html here]

	== Qt Creator Notes ==		== Qt Creator Notes ==

imported_>achipa: /* Qt Creator Notes */

2011-03-07T09:02:39Z

Qt Creator Notes

← Older revision		Revision as of 09:02, 7 March 2011
Line 1:		Line 1:
	While there are a few pages relating to packaging Maemo and Qt apps, this document is designed to provide step-by-step instructions for taking a working app in Qt Creator and publishing it to the Maemo [[extras]] development repository for all to enjoy. The methods here have been tested with basic Qt apps in an Ubuntu Linux environment. Hopefully additional feedback and edits will provide information about working on the lesser platforms available, for example Windows and Mac.		While there are a few pages relating to packaging Maemo and Qt apps, this document is designed to provide step-by-step instructions for taking a working app in Qt Creator and publishing it to the Maemo [[extras]] development repository for all to enjoy. The methods here have been tested with basic Qt apps in an Ubuntu Linux environment. Hopefully additional feedback and edits will provide information about working on the lesser platforms available, for example Windows and Mac.

			== There must be a simpler way ==

			Foreword: These instructions apply you QtSDK 1.0.x and QtCreator 2.0.x. The use of the [http://labs.qt.nokia.com/2011/03/01/qt-sdk-1-1-beta-released/ QtSDK 1.1] is strongly encouraged, as it has incorporated/automated most of the steps outlined below. With QtSDK 1.1, all you need to do is outlined [http://qt-funk.blogspot.com/2011/02/generating-maemoorg-compatible-source.html here]

	== Qt Creator Notes ==		== Qt Creator Notes ==

imported_>rmerren: /* Packaging */

2010-11-02T13:31:03Z

Packaging

← Older revision		Revision as of 13:31, 2 November 2010
Line 21:		Line 21:
	</li>		</li>
	<li>		<li>
	the <code>appname.desktop</code> file. This tells the system how to present the app in the menus and where to find the executable. It will end up in <code>/usr/share/applications/hildon</code> in the final package. For more information on what goes in this file, see the article on the [[desktop file format]].		the <code>appname.desktop</code> file. This tells the system how to present the app in the menus and where to find the executable. It will end up in <code>/usr/share/applications/hildon</code> in the final package. For more information on what goes in this file, see the article on the [[desktop file format]]. Also, note that the .pro changes below will write the app into /usr/bin/appname/appname, so make sure you have the desktop file match this.
	</li>		</li>
	</ul>		</ul>