On 25/10/13 11:11, Thiago Macieira wrote:
> On sexta-feira, 25 de outubro de 2013 08:43:49, Christian Gagneraud wrote:
>> I guess I'm not the first one to ask, are you guys considering to
>> provide a qt-linux-opensource-*-mingw-* ? That is a Qt for windows that
>> can be used to cross-compile on L
On 25/10/13 11:23, Mark Brand wrote:
> On Friday 25 October 2013 08:43:49 Christian Gagneraud wrote:
>>
>> I guess I'm not the first one to ask, are you guys considering to
>> provide a qt-linux-opensource-*-mingw-* ? That is a Qt for windows that
>> can be used to cross-compile on Linux.
>
> You m
Qt 5.2 Beta, Could I customize thesize of apk?
When create a QT Quick2 "hello world" on android,the apk size up to
10.6M, so
Could I customize the libs? or all libs is /required/for QT Quick2?
? 2013?10?23? 18:16, List for announcements regarding Qt releases and
development ??:
Hi,
the Qt
On Friday 25 October 2013 08:43:49 Christian Gagneraud wrote:
>
> I guess I'm not the first one to ask, are you guys considering to
> provide a qt-linux-opensource-*-mingw-* ? That is a Qt for windows that
> can be used to cross-compile on Linux.
You might want to look at mxe.cc.
Mark
_
On sexta-feira, 25 de outubro de 2013 08:43:49, Christian Gagneraud wrote:
> I guess I'm not the first one to ask, are you guys considering to
> provide a qt-linux-opensource-*-mingw-* ? That is a Qt for windows that
> can be used to cross-compile on Linux.
Hello Christian
We have not considere
On quinta-feira, 24 de outubro de 2013 20:51:46, Robin Burchell wrote:
> +1
>
> On Thu, Oct 24, 2013 at 8:50 PM, Frederik Gladhorn
>
> wrote:
> > Hi,
> >
> > I'd like to nominate Gatis as approver. He has been with us in the Digia
> > Oslo office for quite some time now. Gatis fixed many input/
On quinta-feira, 24 de outubro de 2013 22:59:37, André Pönitz wrote:
> And half of the problem is unsolved. From a Qt user's perspective there's
> quite some difference between "Tier 2 - happens to work now, but is left to
> rot and die" and "Tier 2 - intended to be Tier 1, but fumbled at the
> lat
Actually having thought a bit about this, and written the change more or
less, my personal opinion is that it would be better to get distribution
packages (via OBS or any other kind) correctly in the future...
udev, and probably other libraries might not guarantee binary compatibility
for releases
On Wed, Oct 23, 2013 at 11:40:16PM +0100, Thiago Macieira wrote:
> On quarta-feira, 23 de outubro de 2013 22:30:28, André Pönitz wrote:
> > One point that seems to be missing in these considerations is a clearly
> > communicated distinction between "actual state" and "intended state".
> >
> > The
https://bugreports.qt-project.org/browse/QTBUG-34329
On Thu, Oct 24, 2013 at 4:36 PM, Knoll Lars wrote:
> Sounds like dlopen¹ing is the way to go. Sucky, but at least it¹ll work.
> And according to the post below most things should be compatible between
> udev0 and udev1.
>
> Cheers,
> Lars
>
>
Sorry, small correction:
> "0" is *not *GREATER_EQUAL to "3"
not the other way around ;-)
On 24.10.2013 21:57, MuldeR wrote:
> Thank you!
>
> I had a look on the proposed code and I think there is a major problem with
> trying to increase only the *minor* version =-O
>
>
> Let's assume we are o
Thank you!
I had a look on the proposed code and I think there is a major problem with
trying to increase only the *minor* version =-O
Let's assume we are on a future Windows 9 and that one has the actual version
number 7.0.
GetVersionEx() would still report v6.2, so the first version we woul
On 23/10/13 07:55, Motyka Rafal wrote:
>
> Hello,
>
>
> It's time for final testing of Beta candidate packages. *The aim is to
> make sure that there are no blocking issues before the Beta release at
> 12:00 CET on Wednesday.
I guess I'm not the first one to ask, are you guys considering to
provi
On 24/10/13 23:36, Heikkinen Jani wrote:
> Hi!
>
> This was some mirroring problem and should be OK now.
Yes, it is now OK.
Thx,
Chris
>
> Br,
> Jani
>
>> -Original Message-
>> From: development-bounces+jani.heikkinen=digia@qt-project.org
>> [mailto:development-bounces+jani.heikkinen
+1
On Thu, Oct 24, 2013 at 8:50 PM, Frederik Gladhorn
wrote:
> Hi,
>
> I'd like to nominate Gatis as approver. He has been with us in the Digia Oslo
> office for quite some time now. Gatis fixed many input/key handling and XCB
> issues and started looking at sensors lately.
>
> Patches by Gatis:
Hi,
I'd like to nominate Gatis as approver. He has been with us in the Digia Oslo
office for quite some time now. Gatis fixed many input/key handling and XCB
issues and started looking at sensors lately.
Patches by Gatis:
https://codereview.qt-project.org/#q,owner:gatis.paeglis%2540digia.com,n,
> But seriously - how about pre-compiled headers? Is anyone using this compiler
> feature? Does it really help?
Yes and yes. There is a huge amount of redundancy in compilation of
typical C++ projects. YMMV but effective use of
precompiled headers can help significantly.
There are a couple of ru
On quinta-feira, 24 de outubro de 2013 17:53:24, Thiago Macieira wrote:
> [erase text I had written]
>
> After writing an example, I realise that there is a solution and it's the
> same I'm implementing for GCC: we need the qstring_compat.cpp (for
> example) that I added in
> https://code
24.10.2013, 19:14, "Diego Iastrubni" :
> On Wed, Oct 23, 2013 at 7:04 PM, Thiago Macieira
> wrote:
>> 3) Don't use Windows (the operating system and filesystems are too slow)
>> 3.b) don't use MinGW (it uses sub-processes a lot, which are slow on
>> Windows)
>
> LOL...
>
> But seriously - how
On quinta-feira, 24 de outubro de 2013 17:42:01, Olivier Goffart wrote:
> On Thursday 24 October 2013 14:49:39 Thiago Macieira wrote:
> > Hello
> >
> > I'm going to add an #error to qcompilerdetection.h for any unreleased
> > version of MSVC.
>
> I am opposed to that.
>
> Can I do the same for a
On quinta-feira, 24 de outubro de 2013 17:14:16, Diego Iastrubni wrote:
> On Wed, Oct 23, 2013 at 7:04 PM, Thiago Macieira
>
> wrote:
> > 3) Don't use Windows (the operating system and filesystems are too slow)
> >
> > 3.b) don't use MinGW (it uses sub-processes a lot, which are slow on
> >
> >
Hi,
Can we do something with this bug before release
https://bugreports.qt-project.org/browse/QTBUG-34107
All qt appstore apps are unusable right now on OS X 10.9
Raul Metsma
On Oct 23, 2013, at 1:16 PM, List for announcements regarding Qt releases and
development wrote:
> Hi,
>
> the Qt 5.2
On Thursday 24 October 2013 14:49:39 Thiago Macieira wrote:
> Hello
>
> I'm going to add an #error to qcompilerdetection.h for any unreleased
> version of MSVC.
I am opposed to that.
Can I do the same for any unreleased version of ICC?
And a qFatal if it Qt runs on any unreleased CPU?
> The r
On 24/10/13 16:51, "Koehne Kai" wrote:
>
>> -Original Message-
>> From: development-bounces+kai.koehne=digia@qt-project.org
>> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On
>> Behalf Of Thiago Macieira
>> Sent: Thursday, October 24, 2013 4:39 PM
>> To: developm
Hello all,
Just a heads up: we restructured doc.qt.digia.com to host Qt Enterprise
documentation.
Previously, it was designated as "Archives" which hosts non-Qt Project
documentation.
"Archives" is now at doc.qt.digia.com/archives and there are links to that page
from the main doc.qt.digia.com p
Sounds like dlopen¹ing is the way to go. Sucky, but at least it¹ll work.
And according to the post below most things should be compatible between
udev0 and udev1.
Cheers,
Lars
On 24/10/13 16:28, "Thiago Macieira" wrote:
>On quinta-feira, 24 de outubro de 2013 13:46:39, Koehne Kai wrote:
>> I ju
If it's a configure option, we should note if this was done in the
binary so that we can know to ignore the inevitable bug reports.
Rich.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Wed, Oct 23, 2013 at 7:04 PM, Thiago Macieira
wrote:
> 3) Don't use Windows (the operating system and filesystems are too slow)
> 3.b) don't use MinGW (it uses sub-processes a lot, which are slow on
> Windows)
>
LOL...
But seriously - how about pre-compiled headers? Is anyone using this
com
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On
> Behalf Of Thiago Macieira
> Sent: Thursday, October 24, 2013 4:39 PM
> To: development@qt-project.org
> Subject: Re: [Development] #e
On quinta-feira, 24 de outubro de 2013 16:09:37, Yves Bailly wrote:
> While I understand the reasoning about binary compatibility, in my humble
> opinion such a drastic change should be at least deactivable, for example
> by adding a switch to "configure", something like
> "-ignore-binary-compatibi
On quinta-feira, 24 de outubro de 2013 13:55:42, Poenitz Andre wrote:
> Am I understanding this right that this will make such versions of Qt
> uncompilable _even for people who do not care about binary compatibility_?
Yes. I do plan on making #error message include information on how you can get
On quinta-feira, 24 de outubro de 2013 13:46:39, Koehne Kai wrote:
> I just asked, it seems not to be possible:
> http://www.marshut.com/yiqmk/can-apps-ship-their-own-copy-of-libudev.html
>
>
> So we're back to either moving the libudev dependency to a plugin that
> qtserialport tries to load (hu
Haven't worked on CI things for years. Looks like I missed sth here.
You could find(git grep) "TESTRUNNER" in qtqa repo,
https://github.com/qtproject/qtqa . You could get an xml result file for
each auto test, then use some script to gather them and generate full
report.
But I really don't know t
Hello,
Le 24/10/2013 15:49, Thiago Macieira a écrit :
> I'm going to add an #error to qcompilerdetection.h for any unreleased version
> of MSVC.
> The reason is this combination:
> 1) MSVC does not provide a way to turn C++11 off (and won't provide for C++14
> either)
> 2) MSVC does instantiates *
Thiago Macieira [thiago.macie...@intel.com]
> I'm going to add an #error to qcompilerdetection.h for any unreleased version
> of MSVC.
>
> ==> In other words, adding new Q_COMPILER_xxx defines for C++11 for MSVC
> breaks
>binary compatibility <===
>
> For that reason and because we don'
Hello
I'm going to add an #error to qcompilerdetection.h for any unreleased version
of MSVC.
The reason is this combination:
1) MSVC does not provide a way to turn C++11 off (and won't provide for C++14
either)
2) MSVC does instantiates *ALL* class members of exported classes, even inline
f
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On
> Behalf Of Thiago Macieira
> Sent: Thursday, October 24, 2013 3:41 PM
> To: development@qt-project.org
> Subject: Re: [Development] Rem
On quinta-feira, 24 de outubro de 2013 13:33:10, Oswald Buddenhagen wrote:
> the lgpl does not limit how *we* can build and distribute our packages,
> because we ship the sources anyway.
> the ones who'd have a problem would be our customers.
>
> but why is everyone talking about static linking, a
Not sure how those auto tests work on android and ios these days.
But in Qt 4 with Symbian ages, we have a tool, runonphone, which could
deploy application and relative resources to devices and run it on device,
if I don't remember wrong.
https://github.com/qtproject/qt/tree/4.8/tools/runonphone
Hi,
for your information, we are working on a patch for this:
https://codereview.qt-project.org/#change,69129 .
Regards,
Friedemann
--
Friedemann Kleint
Digia, Qt
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/
On Thu, Oct 24, 2013 at 10:56:00AM +, Koehne Kai wrote:
> > [...]
> > We agreed with Kai on IRC, when discussing this topic, that we would ask the
> > udev mailing list for an authoritative reply unless someone can confirm that
> > on this list just as well.
>
> Actually I just checked the sou
On quinta-feira, 24 de outubro de 2013 10:56:00, Koehne Kai wrote:
> > -Original Message-
> > From: development-bounces+kai.koehne=digia@qt-project.org
> > [mailto:development-bounces+kai.koehne=digia@qt-project.org] On
> > Behalf Of Laszlo Papp
> > Sent: Wednesday, October 23, 2013
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On
> Behalf Of Laszlo Papp
> Sent: Wednesday, October 23, 2013 5:45 PM
> To: Sune Vuorela
> Cc: development@qt-project.org
> Subject: Re:
Hi!
This was some mirroring problem and should be OK now.
Br,
Jani
> -Original Message-
> From: development-bounces+jani.heikkinen=digia@qt-project.org
> [mailto:development-bounces+jani.heikkinen=digia@qt-project.org]
> On Behalf Of Christian Gagneraud
> Sent: 24. lokakuuta 201
Hi Jocelyn,
Thanks for your inputs. and Sorry for the very late reply (was held up
with some other tasks) .
I finally could figure out what was the issue.
It was because the loading of the resources required for remote inspector
(WebKit.qrc and InspectorBackendStub.qrc) were failing w
On quinta-feira, 24 de outubro de 2013 09:22:47, Tomasz Olszak wrote:
> > To run the tests, you can simply type "make check" in the top dir.
>
> You mean copy shadowbuild directory to device, to the same path as on host,
> install make and invoke "make check" right?
More likely, copy the source d
>
> To run the tests, you can simply type "make check" in the top dir.
>
You mean copy shadowbuild directory to device, to the same path as on host,
install make and invoke "make check" right?
--
regards / pozdrawiam, Tomasz Olszak
Qt for Tizen | http://qt-project.org/wiki/Tizen
Qt Certified Dev
47 matches
Mail list logo
