Packaging Requirements
Application Packaging Requirements Guide
Before packaging your application for submission, be sure you have reviewed the Validation Guidelines. Intel AppUp Developer program validators do not complete regression test on your application. But a validator will check for the requirements defined in the Validation Process , and will check that the installation package meets the following minimum requirements.
Windows Packaging Requirements
- Submit MSI package – submit a standard Windows Installation package in the form of .MSI file. The MSI must include all required collaterals associated with your application. The MSI must be signed before submitting. Please refer article http://appdeveloper.intel.com/en-us/article/signing-msi-files for signing MSI files
- Silent installation – Your application must install without any required input from the user.
- Single executable – Any and all shortcuts must target only one executable. Your installation can automatically add desktop, quick launch, Start menu, and other shortcuts, but they all must target the same executable.
- Shortcut Target field – The Target entry of the Shortcut table must be a valid feature name/foreign key (Identifier data type) in the Feature table. We support only this data type in the Target field. Do Not use square brackets ([ ]) to indicate a formatted string.
- Avoid arguments in links – Formatted string translation is not supported; therefore, any argument will be interpreted as a plain string.
- Check for C++ runtime - If your application requires C++ runtime then inside MSI installer you should check if C++ runtime is installed.
- Java Packaging Requirements- Submit a single JAR file that includes the optional Intel AppUp(TM) SDK library jar file, application jar file(s), and an application manifest file. The Intel AppUp(TM) Software Packaging Utility can help creating these Java runnable jar packages.
MeeGo Packaging Requirements
- Include RPM –RPM formats are required for submission. The application must successfully install on MeeGo(RPM).
- Include all required dependencies – If your installation requires dependent packages not provided with MeeGo, your installation package must include them.
- Follow MeeGo packaging guidance – Follow the packaging information on MeeGo . These MeeGo articles cover the target directory structure where files must be installed, provide a packaging tool, and cover other topics.
- Include source packages – If you are distributing under an open source license, you must include a single source package for each of the RPM.
| Hardware/OS/Matrix | ||
| OS Type | Package | Hardware |
| MeeGo | RPM | 32-bit |
| Windows 7 | MSI, JAR | 32-bit, 64-bit |
Codecs Packaging Requirements
- If a codec is available in the distro it should be included as part of the app install / packaging.
- If a codec is freely available, it should be included with the app install / packaging.
- If a codec is included in an OEM build (e.g. fluendo in Asus) it does not need to be included for that build.
- If a codec needs to be purchased / licensed then the developer should provide a link and instructions in their product description for the store.
In addition, for validation, Developers will need to supply us with a codec if it is required.
Related Information
- Troubleshooting Application Validation failures
- Packaging MSI with Visual Studio
- Beta Testing Your Application
(12 votes)
Comments
This is for Windows.
How should multiple-language installations be handled? It is possible to automatically select a language transform based on the UI selection or separate MSI files can be used.
Which is the preferred method?
@Aditya,
1. Which target should I select (Windows, MeeGo..etc) ?
- If you want to create an application using QtCreator, as of now you can only target MeeGo.
2. Depending on the target, what should I choose to install in the installation checklist?
- to create a MeeGo app you need to use MeeGo SDK, MeeGo SDK comes with QtCreator that will compile the application and build an RPM. RPM is what you need to upload for a MeeGo app
Here are a bunch of articles that will help you build your app for MeeGo http://appdeveloper.intel.com/en-us/article/meego-articles
Dear Sir, I am using Qt Creator to create my app. Please help me on following lines:
1. Which target should I select (Windows, MeeGo..etc) ?
2. Depending on the target, what should I choose to install in the installation checklist?
As I am a newbie in this technology, kindly help me
Thanks
Hello Sweet Ashok,
Please see http://appdeveloper.intel.com/en-us/article/dot-net-example and http://appdeveloper.intel.com/en-us/blog/2010/10/12/net-appup-developers...
Regards
Hal G.
Technical Support Team
Intel AppUp(SM) Developer Program
Intel AppUp(SM) Center
I am need example with .net for understand about this tech.
Have a questions regarding this requirements:
# Single executable – Any and all shortcuts must target only one executable. Your installation can automatically add desktop, quick launch, Start menu, and other shortcuts, but they all must target the same executable.
What if I our game requires more than just a one shortcut in Start Menu -> Programs?
For example, one shortcut for the game itself, another for launching the game in special mode, shortcut for ReadMe, shortcut for documentation folder, shortcut for helper program. Well, I can make the game to do all the above mentioned tasks, when launching single game executable, but with a different command line. Is it ok? How should I specify the main/default shortcut, which AppUp client can use for launching the game. Should I call IsAuthorised() when the game is launched with /readme or /manual command line arguments?
# Shortcut Target field – The Target entry of the Shortcut table must be a valid feature name/foreign key (Identifier data type) in the Feature table. We support only this data type in the Target field. Do Not use square brackets ([ ]) to indicate a formatted string.
I can't understand this at all. How this is related to creating installer packages with Visual Studio?
Hi Dan,
The application may display the installation screen, however it should not require any input or interaction from the user. In general, while installing most applications, the user will see the installation progress, but as it is a silent installation, there should not be any interaction from the user.
However there is an exception. Application that triggers the UAC will require user interaction else the application installation will fail. So at the moment the only interaction during installation is the UAC. Any other message appearing that require user interaction(input) will cause the application to fail validation.
You can download some free applications on the AppUp(SM) Client Store to see how actually the silent installation is done via the store. You can download the AppUp(SM) Client of this link: http://www.appup.com/applications/index
If you have any other queries, please do not hesitate to contact us.
Regards
Rooven
Intel Technical Support
Intel® Atom™ Developer Program
Intel AppUp(SM) Center
I have a question about the Windows Packaging Requirements - Silent installation – Your application must install without any required input from the user.
Does this mean that the user would see no screens at all, not even a start screen, UAC, screen, etc?
Hi,
I am developing a С++ application based on MFC. Do I need to include MFC into a package or I need to check for C++ runtime in MSI? Can I link my application with static MFC library on build and deploy it without any c++ runtime checks?
Thanks I will be taking a close look at the packaging requirements and use them as long as they support incremental updates which I suspect it does. If they do not then I will not submit. Brian already pointed to a tool for creating the MSI.
Also, I am curious how Intel supports the security certificate requirements for java or does the deployment method you use not require security certificates? The reason I ask is I think that the site you deploy from has to be the one you got the certificate for so my security certificate references my site not Intel's. Apple supplies the security certificate for thier app store for the developers (from what I heard) to use does Intel supply the certificate?
Thanks,
Tony Anecito
Founder,
MyUniPortal (Rich Java Gui Client)
http://www.myuniportal.com
Hello Tony Anecito,
It is important to follow the requirements written in this article. Unsupported steps may be rejected as stated by DG Rooven. Please use the beta testing feature within your dashboard to test your application before submitting it. This should help you understand the flaws in your application.
Best Regards
Cemal C.
Intel Customer Support
Intel® Atom™ Developer Program
Intel AppUp(SM) Beta Center
I use java and java web start to install the app and shortcuts. I am thinking to add a browser link to my web start jnlp file to launch web start in the MSI file. I am not sure what version of java is installed on the netbooks typically but web start will install the required version of java based on the jnlp file settings.
Will this be okay with the packaging group?
Also, my app has built in help system instead of a pdf will that be okay?
Thanks,
Tony Anecito
Founder
MyUniPortal
http://www.myuniportal.com
Hi Eugene,
Thank you for your query.
Currently only C++ and C languages are supported on the Intel® Atom™ Developer Program. Support for more languages and runtimes will come in the future. Please keep an eye on the following link for updates:
http://appdeveloper.intel.com/en-us/develop
If you are using unsupported runtimes, you application validation will fail.
Regards
Rooven
Intel® Atom™ Developer Program
Intel® AppUp(SM) Beta Center
How can I submit my JavaFX application?
I've submitted msi that contained url to WebStart file (jnlp) and made shortcut to it, so when user clicks this shortcut, application gets runned (installed)...
But such solution didn't pass validation:
"ILU01 - Application install
Additional Comments: Windows XP: Application does not download or install from AppUp. The most common issue observed in this area has to do with properly advertised shortcuts within the .msi."
Is there a way to ensure JavaFX runtime is installed?
Thanks in advance for any help.
Hi,
Concerning the UAC disabling, at this stage there is no feature from the Intel® AppUp(SM) Beta client to disable the UAC of windows 7 so that applications will not trigger it.
Regards
Rooven
Intel® Atom™ Developer Program Team
Butler,
For more information of creating silent installer and MSI installer please see these links below:
http://appdeveloper.intel.com/en-us/node/979
http://appdeveloper.intel.com/en-us/blog/2009/12/28/msi-silent-install-p...
Regards
Rooven
Intel® Atom™ Developer Program Team
Windows Packaging Requirements:
Silent installation – Your application must install without any required input from the user.
Does UAC prompt need to be disabled? Is it possible to disable UAC prompt when packaging Windows applications?
I' sorry repeat my comment.
I Can't find delete button.
My mistake is final sentence.
my correted Question is "I want to know how to make only one .msi file included .NET Framework 2.0 (by Silent installation)".
I have a question about "*Submit MSI package ".
Have to submit only one .msi file?
I can't build(make) only one .mis file included .NET Framework restributable package by using VS 2005 Setup and Deploy Project
I used the Prerequisites page of the application in mouse right button clicked in project.
after building, several files exist there.
Setup.msi
setup.exe
DotNetFX(Folder)
I know how to make only one .msi file included .NET Framework. (by Silent installation)
I have a question about "*Submit MSI package ".
Have to submit only one .msi file?
I can't build(make) only one .mis file included .NET Framework restributable package by using VS 2005 Setup and Deploy Project
I used the Prerequisites page of the application in mouse right button clicked in project.
after building, several files exist there.
Setup.msi
setup.exe
DotNetFX(Folder)
I know how to make only one .msi file included .NET Framework. (by Silent installation)
Hi,
Just to bring a little clarification.
Both RPM and DEB packages are required for moblin applications as this is a main requirements for passing the validations. This is so because some OEMs (netbook manufacturers) support either RPM or DEB and some both on their products having moblin platform.
Regards
Rooven
Intel® Atom™ Developer Program Team.
Apparently alien omits dependencies when converting from deb to rpm. Unless I miss something.
So there is the question. My application depends on Qt libraries, and it is enough to include those libraries, I mean list them, into deb package. apt-get resolves them during installation. The required Qt libraries are in moblin repositories, and it would not be smart at all to include them into my rpm.
BTW, latest GUI version of moblin-package-creator does not work on netbook, the dialog is bigger than 600 pixels hence buttons are not accessible.
Boris.
>> Why do we have to submit both RPM and DEB? Isn't just one of them enough?
you can easily convert a rpm to deb using the comment: '% sudo alien -k xxxx.i386.rpm'
>> Does this exclude confirmation clicks; i.e. OK, Continue, Yes, etc...?
These must not exist in your installer. If you are using a Visual Studio 2008 Package and Deployment project, simply open the User Interface settings and remove all dialogues. Best of luck!
Windows Packaging Requirements:
Silent installation – Your application must install without any required input from the user.
Does this exclude confirmation clicks; i.e. OK, Continue, Yes, etc...?
>> Why do we have to submit both RPM and DEB? Isn't just one of them enough?
you can easily convert a rpm to deb using the comment: '% sudo alien -k xxxx.i386.rpm'
>> Follow Moblin packaging guidance
does someone have an exact link to this? after searching through moblin.org - i wasn't able to find a good reference for this. might be good to update the article with an exact link to prevent people from chasing around trying to find information as critical as this.
// Aaron Ardiri
Mobile 1UP
http://www.mobile1up.com/
Hello,
in order to pass validation you need to provide two packages: RPM + DEB.
Best Regards,
Andre B.
Intel® Atom™ Developer Program
Very good post, thanks a lot.
Sorry to repeat Phoenix Lee's question. Why do we have to submit both RPM and DEB? Isn't just one of them enough?
Hi,
The use of scripts is not allowed
Regards
Rooven
hi!
I 'd like to know more detail criteria about packaging.
May I have one script (.sh) with my RPM since it would be easier for user to run .sh rather than typing something like 'rpm -Uvh xxxxxxxxxx'
And also a script for un-installation.
May I submit the document(a quick start shows how to run .sh for installation and how to use this application), .sh file with my RPM?
Thanks a lot!
Hello Phoenix,
Moblin supports both package formats:
http://moblin.org/documentation/moblin-sdk/getting-ready-moblin-development
Best Regards,
Andre B.
Intel® Atom™ Developer Program
If Moblin is the only Linux supported, why requests developers to submit application in both RPM and DEB packages? Is it not true that Moblin 2.1 only supports RPM package?
Thanks,
Phoenix
tgprakash,
MSI can deploy the app is any location you like. There is no specific directory requirement. Although, in future the app will be automatically installed in a specific directory for the store client to be able to launch and uninstall the app. No change on your side for this to happen.
Ajay Mungara
Hi,
Can we configure the msi to deploy our exe's and dll's to any directory we like or any specific location need to be followed.
Hi,
Thank you for your comment.
Currently for 'Linux' operating system only Moblin OS versions is supported. We do not have any other package guidelines for other versions of linux at the moment.
Drafted list of supported OS:
- Windows XP
- Windows 7
- Moblin v2.1
- Ubuntu Moblin Remix
- SUSE® edition of Moblin for Netbooks
- Xandros Moblin v2-compliant desktop
- Linpus Linux Lite 1.2
You may also wish to visit the Moblin community for further information: http://moblin.org/community
Kind Regards,
Rooven
Intel® Atom™ Developer Program Team
Are there any packaging guidelines for debian binary or do we use the rpm guidelines? Also, is it just enough if deb package is tested with ubuntu 9.0.4?