[Interest] Creating Installer for custom Build of Qt

Michael Jackson imikejackson at gmail.com
Thu Apr 11 16:10:39 CEST 2013


On Apr 11, 2013, at 9:54 AM, Sergio Ahumada wrote:

> On 04/11/2013 03:48 PM, Sergio Ahumada wrote:
>> On 04/11/2013 03:32 PM, Michael Jackson wrote:
>>> Branching from the current discussion thread of "[Interest] Oops! Somebody's got a bad case of dependency bloat!" there is another way that I could solve a problem for all the custom builds that I need and that would be to be able to actually build the an installer from my custom build. So instead of downloading the prebuilts (which do not meet my needs), attempting to compile but cant because the tools can not be installed on my collaborators computers, why can I NOT create the installer?
>>> 
>>> Here is the scenario. I have a machine with lots of Windows Virtual Machines that I _do_ have control over. I can install Perl and what ever else is needed. I match my environment as closely as possible to my collaborators computers (VS Versions, Windows Versions, ect). I am perfectly willing to do all the builds that I need for our project for the various versions of VS we use. If I can do my builds and create the installer package I can simply hand that to my collaborators and say "Here install this. it works.".
>>> 
>>> But alas, the installer is some black magic proprietary solution that doesn't want to be given out. The main important thing about the installer is the ability to adjust the paths in the Qt Libraries during the installation.
>> 
>> It's all opensource and public, as far as I know.
>> 
>> https://qt.gitorious.org/qtsdk/qtsdk/trees/master/release-tools/
>> https://qt.gitorious.org/installer-framework/installer-framework/
>> 
>>> Is it possible to build the installer package from my own custom build?
>> 
>> http://qt-project.org/wiki/Building-Qt-Package
>> 
>> http://download.qt-project.org/official_releases/prebuilt/
>> 
>> Cheers,
>> 
> 
> this is Qt5 of course .. I saw you are using -no-qt3support so it might 
> not suit you at all
> 
> -- 
> Sergio Ahumada
> Release Engineer - Digia, Qt

I put in the -no-qt3support because our code base didn't start until Qt 4.6 and I figure that is just more stuff I can cut out of the compile. I usually cut out all the Sql plugins also as I do not need those either. At least not yet.

Thanks
---
Mike J.




More information about the Interest mailing list