Greetings,
Le 18/01/2013 14:37, Motyka Rafal a écrit :
> Qt 5.0.1 release testing has been started. We would like to kindly ask the Qt
> Community for help by
> testing the new packages.
> 1. Installer packages are available here:
> http://releases.qt-project.org/digia/5.0.1/backups/2013-01-
On Saturday, January 19, 2013 22:26:23 Glen Mabey wrote:
> Hello --
>
> On Friday, December 28, 2012 8:55 AM, Stephen Kelly wrote:
> > On Friday, December 28, 2012 08:36:21 Glen Mabey wrote:
> >> #define Q_DECLARE_METATYPE_2(h1,h2) \
> >>
> >> QT_BEGIN_NAMESPACE \
> >> template <> struct QMetaT
Hello,
I have a problem building Qt Creator 2.6.1 with Qt 4.8.0 and MinGW. First I got
the error that qwineventnotifier_p.h is not found. I fixed this by this:
"If Qt's source code does not exist in your hardware, you can download this
file from
http://qt.gitorious.org/qt/qt/blobs/4.8/src/c
On 21 January 2013 19:03, Labs, Torsten wrote:
> Does anybody has a good how compile Qt Creator with MinGW? Or is there a
> prebuild package anywhere?
You can download Qt Creator 2.6.1 for Windows at http://qt-project.org/downloads
Regards,
Sze-Howe
On 01/18/2013 03:37 PM, Motyka Rafal wrote:
> Hello,
>
> Qt 5.0.1 release testing has been started. We would like to kindly ask
> the Qt Community for help by testing the new packages.
>
> 1. Installer packages are available here:
> http://releases.qt-project.org/digia/5.0.1/backups/2013-01-18
> -Original Message-
> From: Alan Alpert [mailto:4163654...@gmail.com]
> Sent: 17. tammikuuta 2013 18:24
> To: Nurmi J-P
> Cc: development@qt-project.org
> Subject: Re: [Development] Proposal: expose the OS/platform in QML
>
> > I had the impression that platform selectors would work nicel
On 01/21/2013 10:06 PM, Iikka Eklund wrote:
> On 01/18/2013 03:37 PM, Motyka Rafal wrote:
>> Hello,
>>
>> Qt 5.0.1 release testing has been started. We would like to kindly ask
>> the Qt Community for help by testing the new packages.
>>
>> 1. Installer packages are available here:
>> http:/
On 18.01.2013 14:37, Motyka Rafal wrote:
> Hello,
>
> Qt 5.0.1 release testing has been started. We would like to kindly ask the Qt
> Community for help by testing the new
> packages.
>
> 1. Installer packages are available here:
> http://releases.qt-project.org/digia/5.0.1/backups/2013-01-18-41
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On
> Behalf Of Peter Kümmel
> Sent: Monday, January 21, 2013 2:57 PM
> To: development@qt-project.org
> Subject: Re: [Development] Qt 5.0
If you're writing the ChangeLog entry at commit time, not right before
the release, why can't your patch contain a change to dist/changelog
from the get-go which, can be reviewed and integrated along with the
code change?
tor arne
___
Development mail
Finally reading up on some old emails…
I'd say we add the virtual destructors. Better to deal with the fallout now
then in the future.
Cheers,
Lars
On Dec 28, 2012, at 1:03 PM, Thiago Macieira wrote:
> On sexta-feira, 28 de dezembro de 2012 19.11.32, Sze Howe Koh wrote:
>> On 25 December 2012
On 21 January 2013 15:08, Tor Arne Vestbø wrote:
> If you're writing the ChangeLog entry at commit time, not right before
> the release, why can't your patch contain a change to dist/changelog
> from the get-go which, can be reviewed and integrated along with the
> code change?
Because that usual
On 1/21/13 16:37 , Giuseppe D'Angelo wrote:
> On 21 January 2013 15:08, Tor Arne Vestbø wrote:
>> If you're writing the ChangeLog entry at commit time, not right before
>> the release, why can't your patch contain a change to dist/changelog
>> from the get-go which, can be reviewed and integrated
On segunda-feira, 21 de janeiro de 2013 17.02.10, Tor Arne Vestbø wrote:
> On 1/21/13 16:37 , Giuseppe D'Angelo wrote:
> > On 21 January 2013 15:08, Tor Arne Vestbø
wrote:
> >> If you're writing the ChangeLog entry at commit time, not right before
> >> the release, why can't your patch contain a c
On segunda-feira, 21 de janeiro de 2013 15.33.59, Knoll Lars wrote:
> Finally reading up on some old emails…
>
> I'd say we add the virtual destructors. Better to deal with the fallout now
> then in the future.
And rename the libraries to libQt5Multimedia.so.6 ?
--
Thiago Macieira - thiago.macieir
Hi, As far as I know, this is a bug of QtSDK installer for Qt4, you can
download latest Qt Library 4.8.X and Qt Creator manually.
https://code.google.com/p/qextserialport/wiki/qwineventnotifier_p_h
On Mon, Jan 21, 2013 at 7:41 PM, Sze Howe Koh wrote:
> On 21 January 2013 19:03, Labs, Torsten
Hi All,
I am compiling QT-4.8.4 with the following configure options on
Windows(Using Visual Studio 2008 command prompt).
=Configure ===
configure.exe -debug -opensource -little-endian -no-accessibility -no-stl
-no-sql-sqlite -no-qt3support -no-nis -no-cups -no-iconv -no-larg
On terça-feira, 22 de janeiro de 2013 11.46.28, Amogh Kudari wrote:
> I am compiling QT-4.8.4 with the following configure options on
> Windows(Using Visual Studio 2008 command prompt).
>
> =Configure ==> configure.exe -debug -opensource -little-endian
> -no-accessibility -no-s
Hi,
I've been getting requests from several fronts to make ci to handle merge's
between branches. Having automated merge from dev->stable->release doesn't make
sense. But merging from release->stable->dev might be doable, but before doing
that I would like to hear your input.
At the moment, aut
On terça-feira, 22 de janeiro de 2013 07.14.01, Fält Simo wrote:
> At the moment, automated merge would always face a merge conflict due to
> sync.profile pointing to same branch where it currently is. To get this
> sorted out, we would have to leave the sync.profile to serve only one
> branch and
Hi Thiago,
Thanks for your quick response.
Now I reconfigured without -qpa option but *still I am getting the same
errors.*
Now configuration looks something like this...
ConfigureOption=
configure.exe -debug -opensource -confirm-license -little-endian
-no-accessibility -no-stl -no-sql
21 matches
Mail list logo
