<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:847910617;
mso-list-type:hybrid;
mso-list-template-ids:495083066 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Now we're gettingto the crux of the matter. The choice is not to<br>
support all versions of Qt simultaneously, but to have a single base<br>
version for each PR, and have this version on the NAND for speed<br>
reasons IIUC (plus integration issues as mentioned above) - and also<br>
to lower memory footprint, having GTK+ and Qt simultanously is<br>
stressful enough, having multiple versions of Qt in memory would make<br>
things even worse. So you won't have Qt4.5 on PR1.2, no Qt4.6 in the<br>
PR that will hopefully bring us Qt4.7, etc. The devel version is there<br>
just for, well, development and testing. As you can see this<br>
significantly lowers our <a href="http://maemo.org/" target="_blank">maemo.org</a>
maneuvering space, too...<br>
<br>
<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I guess I finally “got” your point.
Anything that you want to have end users actually using you should develop on the
“current stable” version. Anything you develop that uses a “newer/upcoming”
version it is just for you as a developer and you will have to jump some hoops in
order to test it. Once the new release is official you publish your application
again to be compiled against the latest official/stable libraries.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>The good news: I officially quit on trying
to push the “new qt” libraries to the device for “regular
users”. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>The bad news now I have more questions:<o:p></o:p></span></font></p>
<ol style='margin-top:0in' start=1 type=1>
<li class=MsoNormal style='color:navy;mso-list:l0 level1 lfo1'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial'>As
today what a developer needs to do to get an application that uses qt to
the end user? Is there a way to tell the autobuilder to compile against
the 4.5 qt and make the package only depend on it?<o:p></o:p></span></font></li>
<li class=MsoNormal style='color:navy;mso-list:l0 level1 lfo1'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial'>What
is the point of the (not so few) qt applications on the repository that
were compiled against the qt4-core (4.6)? Unless pr1.2 will have a qt that
is binary compatible to the libs on the autobuilder right now these packages
will be completely useless, right? I thought the point of committing
packages using qt4-core (4.6) now was to have them ready for day one when
pr 1.2. gets out.<o:p></o:p></span></font></li>
<li class=MsoNormal style='color:navy;mso-list:l0 level1 lfo1'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial'>The
qt applications not using qt4-maemo5 are “moved” to testing. How
are they being tested right now? They can’t be tested on the pr1.1, because
they are compiled against qt 4.6. Are they not being tested at all (everything
is at halt); or they are being tested by people that have “pre
release” pr1.2; or are they being tested using scratchbox
environment?<o:p></o:p></span></font></li>
</ol>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Thanks for taking the time to answer me.
It has been very interesting and “illuminating”<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Best Regards,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Felipe<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
</div>
</body>
</html>