<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title></title><meta http-equiv="Content-type" content="text/html; charset=UTF-8" /><style type="text/css">p { margin:0px; padding:0px; }</style></head><body style='background-color:rgb(255, 255, 255);background-image:none;background-repeat:repeat;background-position:0% 0%;font-family:Verdana,Geneva,Arial,Helvetica,sans-serif;font-size:12px;margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;padding-top:5px;padding-bottom:5px;padding-left:5px;padding-right:5px;'><p style="font-family:Verdana;"><font size="3">would building QT4.6 apps by linking with libqt4-maemo5* still work ?</font><span></span></p><p id="__paragraph__1269882309000" style="font-family:Verdana;"><font size="3"><span>AFAIK , these libqt4-maemo5* are still being kept for QT4.7 development.</span></font><span></span></p><p id="__paragraph__1269882334000" style="font-family:Verdana;"><br /><font size="3"><span></span></font></p><p id="__paragraph__1269882334000" style="font-family:Verdana;"><font size="3"><span>Now if that is true, atleast for the QT4.6 apps still in extras-devel we can still upload to the repository and it will work on the device as well.</span></font><span></span></p><p id="__paragraph__1269882400000" style="font-family:Verdana;">Im aware they cant be promoted to extras-testing due to the bloack but atleast users and developers using the app from extras-devel will be able to use it this way.<span></span></p><p id="__paragraph__1269882479000" style="font-family:Verdana;">Once PR1.2 is on the device we can link these back to libqt4-* as they will be version 4.6 then on the device.<br /></p><p id="__paragraph__1269882479000" style="font-family:Verdana;"><br /></p><p id="__paragraph__1269882479000" style="font-family:Verdana;">Anybody tried it yet or is this not possible ?<span></span></p><p id="__paragraph__1269882490000" style="font-family:Verdana;"><br /></p><p id="__paragraph__1269882490000" style="font-family:Verdana;"><br /></p><p style="font-family:Verdana;"><font size="3"><p> </p><p></p><blockquote type="cite" face="Verdana" class="quote" style="font-size:12px;"><p>----- Original Message -----</p><p>From: ianaré sévi</p><p>Sent: 03/29/10 05:58 PM</p><p>To: Dave Neary</p><p>Subject: Re: Dependency problems after PR 1.2 update to extras builder</p><p> </p><div><div><pre>OK got it to work, I simply set the Qt dependencies to 4.5 (instead of<br />4.6) manually instead on relying on the builder scripts ...<br /><br />- ianaré sévi<br /><br /><br /><br />2010/3/29 Dave Neary <dneary@maemo.org>:<br />> Hi,<br />><br />> Marcin Juszkiewicz wrote:<br />>> No, I am not kidding. It was discussed here on mailing list and announced that<br />>> Extras autobuilder will be updated to PR 1.2 compatible SDK and that resulting<br />>> packages will be installable only on devices owned by Nokia employed people<br />>> (and some from cooperating companies). Other users (and developers) have to<br />>> wait for next firmware drop (which does not have release date as usual so it<br />>> can be tomorrow or in next year).<br />><br />> Now now Marcin, that's not what was said.<br />><br />> what was said was that software built with the PR 1.2 SDK would probably<br />> only install on devices with PR 1.2 installed. That's not the same thing.<br />><br />> ianaré, normally all you have to do is upgrade the firmware on your N900<br />> to PR 1.2, as I understand it.<br />><br />> Cheers,<br />> Dave.<br />><br />> --<br />> maemo.org docsmaster<br />> Email: dneary@maemo.org<br />> Jabber: bolsh@jabber.org<br />><br />> _______________________________________________<br />> maemo-developers mailing list<br />> maemo-developers@maemo.org<br />> https://lists.maemo.org/mailman/listinfo/maemo-developers<br />><br />_______________________________________________<br />maemo-developers mailing list<br />maemo-developers@maemo.org<br />https://lists.maemo.org/mailman/listinfo/maemo-developers</pre></div></div></blockquote></font></p><p><font size="3"> </font></p><font size="3"></font><p></p><p> </p><div id="editor_signature"><p size="3" style="font-family:Verdana;"> </p></div></body></html>