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,
-- 
Sergio Ahumada
Release Engineer - Digia, Qt
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Reply via email to