iBet uBet web content aggregator. Adding the entire web to your favor.

Link to original content: https://web.archive.org/web/20140809131711/http://doc.qt.digia.com/4.6/deployment-symbian.html

2 captures

09 Aug 2014 - 03 Mar 2016

Jul	AUG	Mar
	09
2013	2014	2016

success

fail

About this capture

COLLECTED BY

Organization: Archive Team

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.

The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.

This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.

Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.

The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.

Collection: ArchiveBot: The Archive Team Crowdsourced Crawler

ArchiveBot is an IRC bot designed to automate the archival of smaller websites (e.g. up to a few hundred thousand URLs). You give it a URL to start at, and it grabs all content under that URL, records it in a WARC, and then uploads that WARC to ArchiveTeam servers for eventual injection into the Internet Archive (or other archive sites).

To use ArchiveBot, drop by #archivebot on EFNet. To interact with ArchiveBot, you issue commands by typing it into the channel. Note you will need channel operator permissions in order to issue archiving jobs. The dashboard shows the sites being downloaded currently.

There is a dashboard running for the archivebot process at http://www.archivebot.com.

ArchiveBot's source code can be found at https://github.com/ArchiveTeam/ArchiveBot.

TIMESTAMPS

Home · All Classes · All Functions · Overviews

[Deploying Qt Applications]

Deploying an Application on the Symbian platform

Applications are deployed to Symbian devices in signed .sis package files. The .sis file content is controlled with .pkg files. The .pkg file contains a set of instructions used by tools to produce a .sis file. qmake generates a default .pkg file for your project. The .pkg file generated by qmake is typically fully functional for testing purposes but when planning to deliver your application to end-users some changes are needed. This document describes what changes are typically needed and how to implement them.

Static Linking

Qt for the Symbian platform does currently not support static linking of Qt libraries.

Shared Libraries

When deploying the application using the shared libraries approach we must ensure that the Qt runtime is correctly redistributed along with the application executable, and also that all Qt dependencies are redistributed along with the application.

We will demonstrate these procedures in terms of deploying the Wiggly application that is provided in Qt's examples directory.

Building Qt as a Shared Library

We assume that you already have installed Qt as a shared library, in the C:\path\to\Qt directory which is the default when installing Qt for Symbian. For more information on how to build Qt, see the Installation documentation.

Shared Libraries

After ensuring that Qt is built as a shared library, we can build the Wiggly application. First, we must go into the directory that contains the application:

 cd examples\widgets\wiggly

To prepare the application for deployment we must ensure that the .pkg file generated by qmake contains the relevant vendor information and embeds the necessary dependencies to the application deployment file (.sis). The content of the generated .pkg file can be controlled with the Symbian specific qmake DEPLOYMENT keyword extensions.

First, we will change the vendor statement to something more meaningful. The application vendor is visible to end-user during the installation.

 vendorinfo = \
     "%{\"Example Localized Vendor\"}" \
     ":\"Example Vendor\""

 my_deployment.pkg_prerules = vendorinfo
 DEPLOYMENT += my_deployment

Second we will tell the Symbian application installer that this application supports only S60 5.0 based devices:

 supported_platforms = \
     "; This demo only supports S60 5.0" \
     "[0x1028315F],0,0,0,{\"S60ProductID\"}"

 default_deployment.pkg_prerules -= pkg_platform_dependencies
 my_deployment.pkg_prerules += supported_platforms
 DEPLOYMENT += my_deployment

You can find a list of platform and device indentification codes from Forum Nokia Wiki. By default .pkg file generated by qmake adds support for all S60 3rd edition FP1, S60 3rd edition FP2 and S60 5th edition devices.

Now we are ready to compile the application and create the application deployment file. Run qmake to create Symbian specific makefiles, resources (.rss) and deployment packaging files (.pkg). And do build to create the application binaries and resources.

 qmake
 make release-gcce

If everything compiled and linked without any errors, we are now ready to create an application installation package (wiggly_installer.sis).

If you haven't done so already, download the latest release of the Smart Installer from http://get.qt.nokia.com/nokiasmartinstaller/, and install it on top of the Qt package

Then use this command to create the installer sis package:

 make installer_sis

If all binaries and dependencies were found, you should now have a self signed wiggly_installer.sis ready to be installed on a device. The smart installer contained in the in the installer package will download the necessary dependencies such as Qt libraries to the device.

Note: If you want to have your application properly Symbian Signed for distribution, you will have to properly sign both the application and the application installer packages. Please see Symbian Signed wiki for more information about Symbian Signed.

For more information about creating a .sis file and installing it to device see also here.

[Deploying Qt Applications]