Hi,
On 07/29/2015 06:49 PM, Gunnar Roth wrote:
Hi,
i am trying to make a wec2013 build with openssl support and got weird
errors.
What kind of errors?
then i just found this in configureapp.cpp
} else if (dictionary.value(XQMAKESPEC).startsWith(wince)) {
dictionary[
On 07/31/2015 07:40 PM, Gunnar Roth wrote:
Hi.
I found https://codereview.qt-project.org/#/c/122523/
Which says
This library is not supported on WINCE.
The target is to disappear from Qt very soon anyway.
This is written by alexander.blasche@theqtcompany
So is there some secret decison made
On 07/30/2015 12:16 AM, Gunnar Roth wrote:
My effect is that QT_NO_SSL is defined which leads to 100’s of errors.
And i did pass -openssl to configure. I patched configureapp.cpp by removing
that no’s for opens and ssl ( the result i can see tomorrow)
and by the way i think the sse2/3/4
Hi Edi,
On 07/24/2015 06:11 AM, Edi Anderson wrote:
Hello guys I'm a programmer and would like to gain more experience in large
projects, so I would contribute to Qt.
That's wonderful; welcome to the Qt Project!
I have time available and just need
someone to tell me what to do and how to
On 10/23/2015 11:45 AM, Björn Breitmeyer wrote:
> Hi everybody,
>
> since I am changing my employer I will step down, from the position as WEC
> platform maintainer and I propose that Andreas Holzammer will succeed me in
> this position.
>
> He has been working with me on WEC issues for a long
Yes, the EGL interaction in the Windows QPA plugin is independent of the
ANGLE DLLs.
So, I think this is settled - no need to support ANGLE in VS2012 builds.
>
> Thank you
>
> Andy
>
>
>
>> Cheers,
>> Lars
>>
>> On 21/09/15 11:50, "Andrew Knight&
Hello,
tl;dr: I propose that the copy of ANGLE currently in the 5.6 branch of
qtbase be maintained without being upgraded for the next minor release
of Qt (5.6). For Qt 5.7 and beyond, we should upgrade ANGLE from
upstream while dropping support for VS2010 and VS2012.
Around each minor Qt
On 02/22/2016 05:54 PM, Thiago Macieira wrote:
On segunda-feira, 22 de fevereiro de 2016 14:59:52 PST Roger Briggen wrote:
WEC2013 is also supported by Visual Studio 2013 and Visual Studio 2015
(according to https://msdn.microsoft.com/en-us/library/gg154234.aspx)
because it uses now the ARM
I totally applaud the initiative. Should we go a step further, and make
Windows 10 a requirement for building Qt for any platform? The OS ships on
most new PCs, and cross-compilers and sysroots for other platform targets
are pretty much ubiquitous nowadays. I realize there may be a slight
ANGLE is an important third-party library used in Qt for Windows
applications, and keeping the dependency up-to-date over the releases is
an important and challenging task. It involves testing on a sea of
Windows configurations, creating/maintaining patches for Qt, and
upstreaming those to the
The Windows Runtime port of Qt covers the platform-specific code in Qt,
most of it in the "winrt" platform plugin, which enables Qt to run as
Windows 8/10 Store Apps, on Windows Phone 8/10, and Windows IoT Core.
As the standing Windows Runtime Platform Maintainer, I hereby step down
from my
Hi Steve,
On 09/05/16 15:40, Stephen Kelly wrote:
- (Stephen) "In reality, rewriting Qt's build system in CMake will
actually be a PITA, and will require changes to CMake to make everything
better"
I think something was lost in transit on this point. I don’t think it would be
a PITA to
We had a vibrant discussion on Qt Build Systems, hosted by Kai.
tl;dr: Lots of discussion on the merits of which build system (CMake,
Qbs) should replace qmake in building Qt; lots of supporters of CMake
but no volunteers to do the work, many reasons to use Qbs as well. Some
related
On 09/06/16 03:08, Thiago Macieira wrote:
Em segunda-feira, 5 de setembro de 2016, às 12:49:03 PDT, Andrew Knight
escreveu:
** General sentiment:
- As long as Qbs looks like a part of Qt, it is perceived as a Qt
product, and is less attractive to external users.
- Yet, there remains a conflict
Hi,
On 09/21/16 12:34, Friedemann Kleint wrote:
> Hi,
>
> technically speaking: is using the .rst format set in stone? I find
> this difficult to handle; one needs a local web server to view it
> AFAIK. .md comes to mind as alternative?
>
We discussed this at QtCon and settled on ReStructured
On 11/09/16 16:01, Oswald Buddenhagen wrote:
>
> i can offer meta/ as an alternative.
+1
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Hi,
On 12/22/16 09:18, Oliver Wolff wrote:
> Can someone elaborate on how "one package per OS" reduces the testing
> burden significantly? We still have to check every
> platform/configuration that is inside the package. All that changes is
> that the testers install from one big package instead
17 matches
Mail list logo
