@Peter-Smithson Oh - I found another page - https://doc.qt.io/qtinstallerframework/ifw-cli.html (well actually - I did --help, found an option and then googled it to find the page!)

The use-cases page isn't very clear. If you only want the components listed to install (with dependencies), you must add the --no-default-installations option.

Try it with just 'logo_o'

InstallerApplicationIcon: "Filename for a custom installer icon. The actual file is looked up by attaching a '.icns' (OS X), '.ico' (Windows). No functionality on Unix."

http://doc.qt.io/qtinstallerframework/ifw-globalconfig.html

@JKSH said in Using QTIFW with FTP:

Interesting; I didn't realize Qt IFW works with FTP! (I thought it uses QNetworkAccessManager internally, which doesn't support FTP)

QNetworkAccessManager can handle ip addresses starting with "ftp:". You can download files without problems. QNetworkAccessManager cannot handle the ftp commands for instance for folder navigation (cdup, etc.).

Actually the Installer framework I used was customised i.e. the source code of the QTIFW was modified to suit the need and then the required QTIFW binaries are rebuilt from the modified source.

@SamiN This seemed to be quite straight forward to solve. I created my shortcuts under user desktop area, but when running maintenance tool from service using qtservice it most probably didn't have that 'user' setup in place so trying to add shortcut to desktop failed. Changed location of the shortcut to c:\users\public\desktop seems to help on this one.

Br,
-sami

I wonder if you ever found an answer to this issue ?

I have a similar requirement, in that I want to create an online installer that works both ways. It needs to be able to be run in "download-only" mode (no installation, just download the repo). Then my client's IT dept can have a copy of the repo to put on their server, and their users (some of whom don't have internet access) can do a local installation from their local repo.

It seems that most of the functionality exists:

The offline installer will create a local repo if asked to (CreateLocalRepository in config.xml). This could then be relocated to their server. The online installer can be forced to act like an offline installer by pointing it the local repo.

What I can't seem to do is combine 1 and 2 in the same installer. I could create both an offline and an online installer (one for client's IT and one for their users), except that I cannot package all components into the offline installer because some are licensed, and the client should only have access to the components that they have a licence for.

Hi and welcome to devnet,

For discussing feature of QtIFW, I'd recommend posting your question on the interest mailing list . You'll find there QtIFW's developers/maintainers. This forum is more user oriented. You can also take a look a the bug report system to see if there's anything already fitting your description.

@mrjj It seems the /silent option doesn't exist in the pre-built binary. But I think I can create a controller script in order to control the gui installer by the script.

Thank you !

@Hertzy

This is quite an old post. Nevertheless in case someone encounters the same or similar issues.

In my case https://forum.qt.io/topic/93676/using-qtifw-with-ftp the syntax of ftp urls including user name and password helped.

Have a look at the Controlscript tutorial.

There, check if
installer.isUpdater()
and then
gui.clickButton(buttons.NextButton);
on the introduction page.

You might want to start the maintenancetool with --updater, so that the update functionality is preselected.

This should give you a starting point.

I agree with you. However, I haven't yet tested QtIF enough to determine if this could be considered a bug...

You can use "UNDOEXECUTE". For example: component.addOperation("Execute", "msiexec", "/i", "xxx.msi", "/quiet", "UNDOEXECUTE", "msiexec", "/x", "xxx.msi");

@SGaist

Yes, you are right. Was not really obvious to me.

Here is an updated version of the config.xml of the online example of installer framework

<?xml version="1.0" encoding="UTF-8"?> <Installer> <Name>Online Installer Example</Name> <Version>1.0.0</Version> <Title>Online Installer Example</Title> <Publisher>The Qt Company</Publisher> <!-- Directory name is used in component.xml --> <StartMenuDir>Qt IFW Examples</StartMenuDir> <TargetDir>@HomeDir@/IfwExamples/online</TargetDir> <!-- Change required to have English as startup language e.g. when you have an OS with German as standard language --> <Translations> <Translation>en.qm</Translation> </Translations> <!-- End of change for translation --> <RemoteRepositories> <Repository> <Url>http://localhost/repository</Url> </Repository> </RemoteRepositories> </Installer>

The installer starts then with all text in English. Tested on Windows 7 64bit with German as local language.