On Tuesday 26 August 2014 12:58:41 Kuba Ober wrote:
> > Unless we want to make this a tri-state: definitely local, definitely
> > remote, could be either.
>
> Absolutely. It’s not even an option not to distinguish those three states.
> The consumer of this data can then decide which side to err on
On Tuesday 26 August 2014 09:35:28 Simon Hausmann wrote:
> On Tuesday 26. August 2014 09.30.05 Friedemann Kleint wrote:
> > Hi,
> >
> > > That said, he surely has less time for Qt. Is the cmake integration
> >
> > creating any problems?
> >
> > Every now and then, we hit on a failure (fex with
On Aug 26, 2014, at 12:43 PM, Thiago Macieira wrote:
> On Tuesday 26 August 2014 09:22:32 Rutledge Shawn wrote:
>> After the harrowing review process (92 rounds of patches over 9 months!) the
>> VolumeTypeFlag didn't end up in the final patch. It's a credit to Ivan
>> that he had the patience t
On Tuesday 26 August 2014 08:45:38 Blasche Alexander wrote:
> > month in parentheses):
> > Arch (rolling release)
> > CentOS 7.0 (7/2014)
> > Debian testing (no release!)
> > Fedora 17 (5/2012)
> > Mageia 3 (5/2013)
> > Mint 13 (5/2012)
> > OpenSUSE 12.2 (9/2012)
> >
On Tuesday 26 August 2014 09:22:32 Rutledge Shawn wrote:
> After the harrowing review process (92 rounds of patches over 9 months!) the
> VolumeTypeFlag didn't end up in the final patch. It's a credit to Ivan
> that he had the patience to finally get the current form of QStorageInfo
> into 5.4 bra
On Tuesday 26 August 2014 10:27:52 Allan Sandfeld Jensen wrote:
> Well. That would the safe way, and we should keep that in mind for Qt6, but
> I believe with symbol versioning it can be done without breaking ABI,
> assuming it works as advertised. The libraries would export all symbols as
> both t
Thanks for starting the thread, Alex. I still hadn't had time to
really do my homework on my side of this problem, apart from talking
to you :-)
On Mon, Aug 25, 2014 at 5:25 PM, Blasche Alexander
wrote:
> It is my understanding that the current Linux release binary packages are
> built on Ubuntu
On 26 Aug 2014, at 8:19 AM, Bo Thorsen wrote:
> Which is probably the way people will have to go about doing it. Since
> this distinction isn't reliably available on Linux and it is on Windows,
> then the proper way would be to be able to get the native handle on the
> drive to call Windows meth
On 2014-08-26, Allan Sandfeld Jensen wrote:
> Well. That would the safe way, and we should keep that in mind for Qt6, but I
> believe with symbol versioning it can be done without breaking ABI, assuming
> it works as advertised. The libraries would export all symbols as both their
> normal form
--
Alex
> -Original Message-
> From: development-bounces+alexander.blasche=digia@qt-project.org
> [mailto:development-bounces+alexander.blasche=digia@qt-project.org]
> On Behalf Of Thiago Macieira
> That would mean these are the minimum versions the popular distros (release
>
On Tuesday 26 August 2014, Thiago Macieira wrote:
> On Monday 25 August 2014 22:44:38 Allan Sandfeld Jensen wrote:
> > Using namespace or versioned symbols. I think something like
> > -Wl,--default- symver on all Qt modules and
> > -Wl,--default-imported-symver on anything using Qt modules could s
> -Original Message-
> From: development-bounces+alexander.blasche=digia@qt-project.org
> [mailto:development-bounces+alexander.blasche=digia@qt-project.org]
> On Behalf Of Alejandro Exojo
> How feasable is to backport a newer BlueZ to that old distro, on the machines
> that build
Well, I can approve that but I guess there should be some changes in that file
as well ;)
Br,
Jani
>>-Original Message-
>>From: Marc Mutz [mailto:marc.m...@kdab.com]
>>Sent: 26. elokuuta 2014 9:47
>>To: development@qt-project.org
>>Cc: Heikkinen Jani
>>Subject: Re: [Development] HEADS UP
On Tuesday 26. August 2014 09.30.05 Friedemann Kleint wrote:
> Hi,
>
> > That said, he surely has less time for Qt. Is the cmake integration
>
> creating any problems?
>
> Every now and then, we hit on a failure (fex with dynamic GL). So far,
> these have been simple compile/link errors in the
Hi,
> That said, he surely has less time for Qt. Is the cmake integration
creating any problems?
Every now and then, we hit on a failure (fex with dynamic GL). So far,
these have been simple compile/link errors in the tests, but the issue
is that we might hit a wall once we really need to ad
On Aug 26, 2014, at 4:02 AM, quinn.wj.xie wrote:
>
> Hello, everyone at development@qt-project
>
> I have a question and want some suggestions. Right now I am learning Qt
> programming. And I was wondering if Qt supports a customed web browser.
> Because our lab is working on a new Interne
16 matches
Mail list logo
