Hi,
According the comments we had, this is the current proposal:
Installer gui (imagine the checkboxes before each <..> :).. )
<Qt>
| <5.0.0>
| | <qt-doc>
| | <src>
| | <win32-mingw>
| | | <Essentials>
| | | <Add-Ons>
| | <win32-msvc2010>
| | | <Essentials>
| | | <Add-Ons>
| | <win32-msvc2010>
| | | <Essentials>
| | | <Add-Ons>
| <5.x.x>
| | <qt-doc>
| | <src>
| | <win32-mingw>
| | | <Essentials>
| | | <Add-Ons>
| | <win32-msvc2010>
| | | <Essentials>
| | | <Add-Ons>
| | <win64-msvc2010>
| | | <Essentials>
| | | <Add-Ons>
| <tools>
| | <qt creator>
And corresponding installation directories:
Qt/5.0.0-beta2/win32-mingw/
Qt/5.0.0-beta2/win32-msvc2010/
Qt/5.0.0-beta2/win32-msvc2010/
Qt/5.x.x/win32-mingw/
Qt/5.x.x/win32-msvc2010/
Qt/5.x.x/win32-msvc2010/
If there is no objections we start implementing this asap, so that we have it
ready before beta 2.
The plan is to put this visible also in wiki, once I get my account activated..
Br,
Johanna
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
Kalinowski Maurice
Sent: 21. syyskuuta 2012 21:54
To: Thiago Macieira; [email protected]
Subject: Re: [Releasing] Qt5 SDK component install tree
Hi,
some comments from my side.
First of all, thanks to Johanna for taking that topic up. It is extremely
important to get the setup in shape to be able to scale and extend in the
future.
However, with the current scheduling I would suggest to take a very pragmatic
approach and then move on from there.
Pragmatic would mean to focus on the following items:
- Qt 5 Desktop build included
- Qt Creator included
- Documentation
- Examples
- Pure offline installers containing the package and no updates in the initial
version
- Packages for Windows (one package per compiler to reduce download size),
Linux and Mac
My assumption is that the timing to get those in shape will almost match the
final Qt 5.0 release.
In parallel we should talk about topics like:
- Updatability
- Providing multiple versions concurrently (5.1, 5.2,...)
- Providing multiple targets (Desktop, upcoming mobile targets, ...),
potentially from 3rd party providers as well?
- Additional tooling aspects (Qt Creator extensibility, standalone tools, ...)
But schedule actual work on those after 5.0.
> On sexta-feira, 21 de setembro de 2012 12.26.26, Äijälä Johanna wrote:
> > 1. Install tree in installer gui, where components are selected to be
> > installed: <src>
> > <qt>
> > <version>
> > <essentials>
> > <>
> > <>
>
> Essentials, by definition, cannot be subdivided. Make the installation
> unitary:
> all of them or none of them. Also, if possible, make the installation of any
> add-on
> trigger the Essentials installation.
Agreed, there should not be a differentiation as such. If such packages will be
available, they should be in the same location like on a local build.
> > The beta1 installer had only the following:
> > <qt version>
> > <src>
> > <desktop>
> > <compiler>
> >
> >
> > 2. And the other thing is the installation path on users computer,
> > beta1 installer has a long install paths, for example on windows:
> > c:\Qt5.0.0beta1\Desktop\Qt\5.0.0-beta1\msvc2010_64
> [examples\qtbase\....].
> > That could be changed to for example:
> >
> > c:\Qt5SDK\Desktop\5.0.0-Msvc64
> > c:\Qt5SDK\Desktop\5.0.0-Msvc32
> > c:\Qt5SDK\Desktop\5.0.0-MinGW
> > c:\Qt5SDK\Desktop\5.0.1-Msvc64
> > c:\Qt5SDK\Desktop\5.0.1-Msvc32
> > c:\Qt5SDK\Desktop\5.0.1-MinGW
> > c:\Qt5SDK\Desktop\5.0.2-Msvc64
> > c:\Qt5SDK\Desktop\5.0.2-Msvc32
> > c:\Qt5SDK\Desktop\5.0.2-MinGW
> >
> > or:
> > c:\Qt5SDK\Desktop\5.0.0\Msvc64
> > c:\Qt5SDK\Desktop\5.0.0\Msvc32
> > c:\Qt5SDK\Desktop\5.0.0\MinGW
> > c:\Qt5SDK\Desktop\5.0.1\Msvc64
> > c:\Qt5SDK\Desktop\5.0.1\Msvc32
> > c:\Qt5SDK\Desktop\5.0.1\MinGW
> > c:\Qt5SDK\Desktop\5.0.2\Msvc64
> > c:\Qt5SDK\Desktop\5.0.2\Msvc32
> > c:\Qt5SDK\Desktop\5.0.2\MinGW
>
> I prefer the first option, with the default dropping the 5. The QtSDK should
> be
> able to install Qt 4 too.
Actually my vote is to remove the term "SDK" as well. We should see the
offering as one holistic package, meaning by downloading "Qt" you get the full
thing.
Thiago and I had a chat about Qt 4 inclusion a couple of days ago. The basic
idea is to allow developers to migrate from Qt4 to Qt5 and hence the package
should be available. However, with the current setup we might not be able to
make that in time. And even if, only the desktop target will be available, not
any of the cross-compilation / mobile targets that the currently existing Qt
SDK has.
BR,
Maurice
_______________________________________________
Releasing mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/releasing
_______________________________________________
Releasing mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/releasing
