Em sáb 08 fev 2014, às 11:39:15, Sze Howe Koh escreveu:
> As per the email subject, the archive is incomplete:
> http://download.qt-project.org/archive/qt/
They're here:
http://download.qt-project.org/official_releases/qt/
I don't know why we have two different places for the files.
--
Thiago M
As per the email subject, the archive is incomplete:
http://download.qt-project.org/archive/qt/
Regards,
Sze-Howe
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Le 06/02/2014 09:03, Cornelius Hald a écrit :
> Yes, please report those issues as bugs and post the links here. I'd
> like to follow the progress as well. All in all multimedia on Android
> still seems to be quite buggy. Had some issues with videos as well.
Hi,
I just created the bugs:
https
On Friday 07 February 2014 14:05:09 Svetkin Mikhail wrote:
> Hellow all.
> I was creating custom widgets with the help of Qt-designer model.
> And I have noticed I have to duplicate my code, if I want to edit
> properties of the widget in qt-designer property editor.
>
[...]
> Q_PROPERTY(QSt
Em sex 07 fev 2014, às 09:35:09, Dmitry Ashkadov escreveu:
> Hello!
>
> I've tried to merge the patch https://codereview.qt-project.org/72692,
> but CI fails. There is a line in logs:
>
> cc1plus.exe: out of memory allocating 408 bytes
>
> How may it be fixed?
That error means the machine ran o
Is it possible to cross-compile a Windows build from within Linux using the
mingw32 toolchain.
I configure it as follows:
../../qt5/qtbase/configure -v -developer-build -opensource -confirm-license
-release -xplatform win32-g++ -device-option
CROSS_COMPILE=i586-mingw32msvc- -no-gui
It fails with
> > The latest test failures seemed to be due to timeout rather than anything
> > else. The 'waitForDone()' function is exiting with a failure due to DNS
> > lookup timeout. The current timeout is set to 10 secs. This is quite
> large,
> > but still, could there be a network issue with the CI setup
> Returning default-constructed value is heavily used practice in qt api and it
> simplifies our code.
It is often convenient, but he problem is that an error can propagate
a long way from the source before it gets discovered, which makes
debugging difficult, especially if the error gets propagat
>
> > The idea was to silently return a default-constructed type.
>
> I'm not keen on that. Aside from adding extra restrictions to the
> types that the class can be used with as you mention,
> it runs the much more severe risk of masking serious bugs.
>
Returning default-constructed value is heav
> Btw. is Qt's Jenkins CI job setup and configuration open and downloadable? I
> would love to create a Jenkins CI project out of it and let it create
> packages. This would also solve my problem.
Yes, but I think you're better off creating this from scratch. Getting a
working Jenkins setup is
10 matches
Mail list logo
