Re: [Development] New reference platforms in the CI for Qt5.2
On Sun, Aug 11, 2013 at 1:06 AM, Charley Bay charleyb...@gmail.com wrote: Tony sayeth: snip, We'd like to change the reference platforms a bit. We have new platforms coming in and old ones are just that.old. snip, These changes would be targeted for Qt 5.2 and the current proposition can be seen here: http://qt-project.org/wiki/CI_Configurations (That web page has been badly out of date, but I'm automating the update process of it currently. I will also keep the Qt argument list up to date so that you can see what the differences are between the configurations.) snip, This is a helpful page -- thanks! QUESTION: I see MSVC2012 start to show up for Win8 (only), and Win7 mostly stays with MSVC2010. Because Microsoft is pushing updates for their MSVC2012 (they are no longer updating MSVC2010, and it misses much C++11), our impression is that MSVC2010 is like Vista, where it's just easier to move-along to the next version. However, we will be Win7 for the foreseeable future (we have no current efforts investigating Win8). Thus, our (Windows) reference platforms are MSVC2008 and MSVC2012 (we have no interest in 2010). Are other people doing this too? Is there interest in moving to MSVC2012 at the expense of MSVC2010? A few months ago, we moved from 2008 to 2010 because we were using Qt4 for that project, and there were no official 2012 packages. I do not work anymore in that project, but the plan was to move to 2012 once the Qt 4 to 5 migration would take place. My impression is, and experience for that matter, a 2010 to 2012 change is a common ongoing practice for Qt 5 customers. I have not seen many people using 2008 with Qt 5. -- Laszlo --charley ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] New reference platforms in the CI for Qt5.2
for X64, msvc2012 is fine, but it seems that for XP 32, msvc 2012 is not possible If I have correctly understand. 2013/8/11 Laszlo Papp lp...@kde.org On Sun, Aug 11, 2013 at 1:06 AM, Charley Bay charleyb...@gmail.comwrote: Tony sayeth: snip, We'd like to change the reference platforms a bit. We have new platforms coming in and old ones are just that.old. snip, These changes would be targeted for Qt 5.2 and the current proposition can be seen here: http://qt-project.org/wiki/CI_Configurations (That web page has been badly out of date, but I'm automating the update process of it currently. I will also keep the Qt argument list up to date so that you can see what the differences are between the configurations.) snip, This is a helpful page -- thanks! QUESTION: I see MSVC2012 start to show up for Win8 (only), and Win7 mostly stays with MSVC2010. Because Microsoft is pushing updates for their MSVC2012 (they are no longer updating MSVC2010, and it misses much C++11), our impression is that MSVC2010 is like Vista, where it's just easier to move-along to the next version. However, we will be Win7 for the foreseeable future (we have no current efforts investigating Win8). Thus, our (Windows) reference platforms are MSVC2008 and MSVC2012 (we have no interest in 2010). Are other people doing this too? Is there interest in moving to MSVC2012 at the expense of MSVC2010? A few months ago, we moved from 2008 to 2010 because we were using Qt4 for that project, and there were no official 2012 packages. I do not work anymore in that project, but the plan was to move to 2012 once the Qt 4 to 5 migration would take place. My impression is, and experience for that matter, a 2010 to 2012 change is a common ongoing practice for Qt 5 customers. I have not seen many people using 2008 with Qt 5. -- Laszlo --charley ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Puzzled by desktop development priorities, Mac OS specifically [Warning: Rant]
It works for me for a Quick2 application, but I have tried the same for a Widget Opengl QT5 application and When I launch macdeployqt I have the following error : ERROR: no file at /Library/Frameworks/QtScript.framework/Versions/4/QtScript ERROR: no file at /Library/Frameworks/QtCore.framework/Versions/4/QtCore ERROR: no file at /Library/Frameworks/QtSvg.framework/Versions/4/QtSvg ERROR: no file at /Library/Frameworks/QtGui.framework/Versions/4/QtGui ERROR: no file at /Library/Frameworks/QtXml.framework/Versions/4/QtXml ERROR: no file at /Library/Frameworks/QtNetwork.framework/Versions/4/QtNetwork I don't use QT4 at all, I don't use qtscript and I when I launch the apps, it crash trying to find the QT4 script framework ? 2013/8/8 Jake Thomas Petroules jake.petrou...@petroules.com What we really need is to complete the Relocatable Qt project and use @rpath in the install names of Qt frameworks. Then macdeployqt would not need to exist, or would consist merely of a bunch of copy commands. -- *Jake Petroules* Chief Technology Officer Petroules Corporation · www.petroules.com Email: jake.petrou...@petroules.com On Aug 8, 2013, at 5:37 AM, Rutledge Shawn shawn.rutle...@digia.com wrote: On 8 Aug 2013, at 11:34 AM, qtnext wrote: if I use the script to patch the //, macdeployqt from qt5.1., then script postmacdeployqt ... it works fine :) ... Thanks a lot :) But we need to fix macdeployqt so you don't need so many steps. Maybe in the future qbs could do everything. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] New reference platforms in the CI for Qt5.2
Tony sayeth: snip, We'd like to change the reference platforms a bit. We have new platforms coming in and old ones are just that.old. snip, These changes would be targeted for Qt 5.2 and the current proposition can be seen here: http://qt-project.org/wiki/CI_Configurations (That web page has been badly out of date, but I'm automating the update process of it currently. I will also keep the Qt argument list up to date so that you can see what the differences are between the configurations.) snip, charley: This is a helpful page -- thanks! QUESTION: I see MSVC2012 start to show up for Win8 (only), and Win7 mostly stays with MSVC2010. Because Microsoft is pushing updates for their MSVC2012 (they are no longer updating MSVC2010, and it misses much C++11), our impression is that MSVC2010 is like Vista, where it's just easier to move-along to the next version. However, we will be Win7 for the foreseeable future (we have no current efforts investigating Win8). Thus, our (Windows) reference platforms are MSVC2008 and MSVC2012 (we have no interest in 2010). Are other people doing this too? Is there interest in moving to MSVC2012 at the expense of MSVC2010? Laszlo: A few months ago, we moved from 2008 to 2010 because we were using Qt4 for that project, and there were no official 2012 packages. I do not work anymore in that project, but the plan was to move to 2012 once the Qt 4 to 5 migration would take place. My impression is, and experience for that matter, a 2010 to 2012 change is a common ongoing practice for Qt 5 customers. I have not seen many people using 2008 with Qt 5. Agreed -- we looked at building Qt5 with MSVC2008, and I've seen reports on the web that people have done it, but I don't know that it buys you much. I should have been more clear for our (Windows) reference platforms: *- Qt4 + MSVC2008 (sustaining development only) *- Qt5 + MSVC2012 (existing and new development) ...where we have no interest in MSVC2010 (Microsoft seems to call it done with no more updates). Further, we will probably move quickly from 2012=2013, as it looks like a pretty good (stable) compiler with the current active love and attention by Microsoft. qtnext wrote: for X64, msvc2012 is fine, but it seems that for XP 32, msvc 2012 is not possible If I have correctly understand. Yes, we've been following the drama there as we have XP-embedded (32-bit) with Qt4. (Funny stories all-around there.) For the casual reader, the original MS solution was to use the 2010 compiler for XP, which you could launch from within the 2012 IDE. However, after community uproar, there have been several patches/updates by Microsoft to reverse the decision, and it now looks like 2012 officially targets XP: http://stackoverflow.com/questions/13130713/how-to-compile-for-win-xp-with-visual-studio-2012 http://stackoverflow.com/questions/14349793/c-program-written-in-vs2012-works-w-win7-8-2008r2-2012-but-not-2003-xp-32bit (In other news, porting from 2010 to 2012 is a little more work for legacy MFC users, as there was some shuffling in the AfxWin.h and Windows.h headers; however, the 2012=2013 port seems to be rather trivial, and the C++ improvements appear to be significant, which is partly why we want it as soon as we are able.) For the Qt community, though, my suggestion for reference platforms would be something like: FOR TODAY: *- Qt4 + MSVC2008 (sustaining development only) ...I see no real advantage for Qt4+MSVC2010, nobody is sustaining fielded releases with this combination, I'm not sure they should bother... *- Qt5 + MSVC2012 (existing and new development) ...I see no real advantage for Qt5+MSVC2010, nobody is sustaining fielded releases with this combination, I'm not sure they should bother... FOR SOON (AFTER STABLE MSVC2013): *- Qt5 + MSVC2013 (existing and new development) ...Could also provide Qt5+MSVC2012 for the transition, should be easy/cheap because the headers are similar (identical?), but I'd expect most people would move over to 2013 for new development, perhaps keeping 2012 for sustaining... --charley ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] New reference platforms in the CI for Qt5.2
On Sun, Aug 11, 2013 at 5:56 PM, Charley Bay charleyb...@gmail.com wrote: Tony sayeth: snip, We'd like to change the reference platforms a bit. We have new platforms coming in and old ones are just that.old. snip, These changes would be targeted for Qt 5.2 and the current proposition can be seen here: http://qt-project.org/wiki/CI_Configurations (That web page has been badly out of date, but I'm automating the update process of it currently. I will also keep the Qt argument list up to date so that you can see what the differences are between the configurations.) snip, charley: This is a helpful page -- thanks! QUESTION: I see MSVC2012 start to show up for Win8 (only), and Win7 mostly stays with MSVC2010. Because Microsoft is pushing updates for their MSVC2012 (they are no longer updating MSVC2010, and it misses much C++11), our impression is that MSVC2010 is like Vista, where it's just easier to move-along to the next version. However, we will be Win7 for the foreseeable future (we have no current efforts investigating Win8). Thus, our (Windows) reference platforms are MSVC2008 and MSVC2012 (we have no interest in 2010). Are other people doing this too? Is there interest in moving to MSVC2012 at the expense of MSVC2010? Laszlo: A few months ago, we moved from 2008 to 2010 because we were using Qt4 for that project, and there were no official 2012 packages. I do not work anymore in that project, but the plan was to move to 2012 once the Qt 4 to 5 migration would take place. My impression is, and experience for that matter, a 2010 to 2012 change is a common ongoing practice for Qt 5 customers. I have not seen many people using 2008 with Qt 5. Agreed -- we looked at building Qt5 with MSVC2008, and I've seen reports on the web that people have done it, but I don't know that it buys you much. I should have been more clear for our (Windows) reference platforms: *- Qt4 + MSVC2008 (sustaining development only) *- Qt5 + MSVC2012 (existing and new development) ...where we have no interest in MSVC2010 (Microsoft seems to call it done with no more updates). Further, we will probably move quickly from 2012=2013, as it looks like a pretty good (stable) compiler with the current active love and attention by Microsoft. qtnext wrote: for X64, msvc2012 is fine, but it seems that for XP 32, msvc 2012 is not possible If I have correctly understand. Yes, we've been following the drama there as we have XP-embedded (32-bit) with Qt4. (Funny stories all-around there.) For the casual reader, the original MS solution was to use the 2010 compiler for XP, which you could launch from within the 2012 IDE. However, after community uproar, there have been several patches/updates by Microsoft to reverse the decision, and it now looks like 2012 officially targets XP: http://stackoverflow.com/questions/13130713/how-to-compile-for-win-xp-with-visual-studio-2012 http://stackoverflow.com/questions/14349793/c-program-written-in-vs2012-works-w-win7-8-2008r2-2012-but-not-2003-xp-32bit (In other news, porting from 2010 to 2012 is a little more work for legacy MFC users, as there was some shuffling in the AfxWin.h and Windows.h headers; however, the 2012=2013 port seems to be rather trivial, and the C++ improvements appear to be significant, which is partly why we want it as soon as we are able.) For the Qt community, though, my suggestion for reference platforms would be something like: FOR TODAY: *- Qt4 + MSVC2008 (sustaining development only) ...I see no real advantage for Qt4+MSVC2010, nobody is sustaining fielded releases with this combination, I'm not sure they should bother... *- Qt5 + MSVC2012 (existing and new development) ...I see no real advantage for Qt5+MSVC2010, nobody is sustaining fielded releases with this combination, I'm not sure they should bother... IMHO, as of now, that is too big a gap when it comes to porting your relatively complex software to Qt 5. You might have several issues with the Qt bits themselves, albeit it is getting smoother. On top of that, you would need to have to deal with several years of difference between MSVC variants when porting. This would make the port a relatively intrusive effort because you would need to deal with more than one significant factor. This could be probably and potentially improved a bit by providing proper 2012 Qt 4.8.X binaries off-hand, so that you could decouple the porting factors in different stages. Overall, it is hard to make such improvements in certain industry sectors like automotive where you would need to switch to latest technologies (i.e. more than one) in one step. -- Laszlo ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Bug status update
Done. On Sun, Aug 11, 2013 at 7:52 PM, Samuel Gaist samuel.ga...@edeltech.chwrote: Hi, Is there a way (without necessarily bugging the default assignee) to update a bug resolution for a self reported/solved bug ? i.e. https://bugreports.qt-project.org/browse/QTBUG-32674 ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Bug status update
You would need to either get rights for that on Jira, or ask others having those, provided you have not had such rights just yet. On Sun, Aug 11, 2013 at 8:59 PM, Samuel Gaist samuel.ga...@edeltech.chwrote: Thank you very much ! I am currently working on several other things that are in review and some of my other work have already been merged, what would be the best way to help with these updates ? On 11 août 2013, at 21:43, Laszlo Papp wrote: Done. On Sun, Aug 11, 2013 at 7:52 PM, Samuel Gaist samuel.ga...@edeltech.ch wrote: Hi, Is there a way (without necessarily bugging the default assignee) to update a bug resolution for a self reported/solved bug ? i.e. https://bugreports.qt-project.org/browse/QTBUG-32674 ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Bug status update
Approvers can deal with those: https://codereview.qt-project.org/#admin,group,12 There are also a few other non-approvers (like me) who can do this, but it is perhaps best to ask the default assignee, and if no reaction takes place, give a polite ping to that person or someone else from the approvers. Also, these things work out on IRC (#qt-labs@freenode) fairly quickly though if you expect frequent queries like that. On Sun, Aug 11, 2013 at 9:26 PM, Samuel Gaist samuel.ga...@edeltech.chwrote: As far as I can tell, I don't have any special rights currently (also I might be a bit of a young contributor to get more) Is there someone or a group dedicated that can be contacted for these matters ? On 11 août 2013, at 22:01, Laszlo Papp wrote: You would need to either get rights for that on Jira, or ask others having those, provided you have not had such rights just yet. On Sun, Aug 11, 2013 at 8:59 PM, Samuel Gaist samuel.ga...@edeltech.ch wrote: Thank you very much ! I am currently working on several other things that are in review and some of my other work have already been merged, what would be the best way to help with these updates ? On 11 août 2013, at 21:43, Laszlo Papp wrote: Done. On Sun, Aug 11, 2013 at 7:52 PM, Samuel Gaist samuel.ga...@edeltech.ch wrote: Hi, Is there a way (without necessarily bugging the default assignee) to update a bug resolution for a self reported/solved bug ? i.e. https://bugreports.qt-project.org/browse/QTBUG-32674 ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Bug status update
On domingo, 11 de agosto de 2013 20:52:39, Samuel Gaist wrote: Hi, Is there a way (without necessarily bugging the default assignee) to update a bug resolution for a self reported/solved bug ? i.e. https://bugreports.qt-project.org/browse/QTBUG-32674 You have to get it assigned to you, which I've now done. You should be able to close the issue. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Bug status update
On Sun, Aug 11, 2013 at 10:16 PM, Samuel Gaist samuesamuel.ga...@edeltech.ch out of curiosity I have checked what I could do but I didn't saw a difference in the web interface. You cannot do much without the appropriate rights AFAIK. Is there a quick reference guide somewhere about that ? I tried to ask the same before: http://lists.qt-project.org/pipermail/development/2013-July/011958.html ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Bug status update
On domingo, 11 de agosto de 2013 23:16:36, Samuel Gaist wrote: out of curiosity I have checked what I could do but I didn't saw a difference in the web interface. Is there a quick reference guide somewhere about that ? You had to look at it before Laszlo closed the task. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
