Hi,
On 03.01.2018 22:21, Thiago Macieira wrote:
On Wednesday, 3 January 2018 14:26:49 -02 Igor Mironchik wrote:
Hello,
What does it mean: Project ERROR: Could not find feature future.
This is from qmake-ing corelib.pro in dev branch.
Are you sure you've finished configure in the qtbase top
On Wednesday, 3 January 2018 18:01:43 -02 Thiago Macieira wrote:
> > -prefix /opt/qt5.10.0 -no-separate-debug-info -system-zlib -system-libpng
> > -confirm-license -nomake examples -I /usr/X11/include -release
> > -webengine-webrtc -qt-libjpeg -no-sse2 -no-sse3 -no-sse3 -no-sse4.1
> > -no-sse4.2 -n
On Wednesday, 3 January 2018 17:53:40 -02 Toan Pham wrote:
> Thiago,
>
> I am using gcc 4.8.5, but the compiler was optimized for pentium4 so all of
> those vector instructions had to be disabled at build time.
Ah, ok, provided "all those" imply "those that Pentium 4 did not support".
> BTW, I g
Thiago,
I am using gcc 4.8.5, but the compiler was optimized for pentium4 so all of
those vector instructions had to be disabled at build time.
BTW, I got webengine to compile successfully with several patches to
libvpx. Now, I just ran into another brick wall with the errors attached
at the end
On Wednesday, 3 January 2018 15:29:19 -02 Igor Mironchik wrote:
> How do you organize work on Qt in case of contributions?
I develop everything on top of the current stable branch (5.10 today), except
for a brief time between the first beta and the release of a new minor
version.
--
Thiago Mac
On Wednesday, 3 January 2018 14:26:49 -02 Igor Mironchik wrote:
> Hello,
>
> What does it mean: Project ERROR: Could not find feature future.
>
> This is from qmake-ing corelib.pro in dev branch.
Are you sure you've finished configure in the qtbase top (or qt5.git)?
--
Thiago Macieira - thiago
On Wednesday, 3 January 2018 16:02:33 -02 Toan Pham wrote:
> The compiler I built a few years back was optimized for pentium4; it
> wouldn't accept the -mavx2 option. That's why I had to hack libvpx to
> disable avx completely.
AVX2 is a "relatively" modern instruction set, only available in GCC
@Kevin,
The compiler I built a few years back was optimized for pentium4; it
wouldn't accept the -mavx2 option. That's why I had to hack libvpx to
disable avx completely.
Anyway, Here's the patch to libvpx if anyone is running into the same issue
at link time:
--- source/config/linux/ia32/vpx
When I get that error, I do:
git clean -dxf
and run configure again.
From: Development on
behalf of Igor Mironchik
Sent: Wednesday, January 3, 2018 6:29:19 PM
To: development@qt-project.org
Subject: Re: [Development] Project ERROR: Could not find featur
Toan Pham wrote:
> I over came the memory limitation by forcing ninja to run in single thread
> (pass -j 1 to ninja). However, at linking stage using a 32bit linker, the
> linker failed because it could not find references to avx2 in libvpx, a
> third-party library that I hacked to get AVX2 disabl
Hi,
I will ask with another words: does dev branch compiles?
How do you organize work on Qt in case of contributions? For example, I
created a contribution based on dev branch and can't even check if it
compiles. Maybe you, guys, do such things somehow in different way?
Maybe I understood som
Hello,
What does it mean: Project ERROR: Could not find feature future.
This is from qmake-ing corelib.pro in dev branch.
Thank you.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Hi!
Branching from '5.9' to '5.9.4' is now ready. So all changes targeted to Qt
5.9.4 release must be done in '5.9.4' and '5.9' is for Qt 5.9.5 from now on
br,
Jani
From: Development on
behalf of Jani Heikkinen
Sent: Friday, December 22, 2017 4:26 PM
T
13 matches
Mail list logo
