>I have been looking in a way to provide with my app some wifi connection
>manager which would
>allow the following functionality :
>F1 - Enable/disable wifi adapters
>F2 - List wifi networks
>F3 - connect to a network specifying the Wifi Key
>That Api allows me to list networks properly (F2), bu
Hello Thiago,First of all, thanks for taking the time to answer that long
message.Yes, you assumption about me making the system wifi control panel is
correct.I followed then you advice to go the introspection -> xml ->
qdbusxml2cpp -> cpp way.I managed to have the connman manager xml retrieved,
On Sunday 22 March 2015 11:36:37 Nikos Chantziaras wrote:
> On 21/03/15 20:19, Thiago Macieira wrote:
> > RHEL 6.6 comes with glibc 2.12, which isn't affected by these issues. See
> > http://distrowatch.com/table.php?distribution=redhat
> >
> > Again, the problem is RHEL 5, which has glibc 2.5.
>
On Sunday 22 March 2015 10:16:09 Liang Jian wrote:
> As you can see, neno is not enabled, what is wrong with my
> configuration?
Nothing. Neon is never enabled by default.
To enable it, edit the mkspec and add the flags:
-mfpu=neon
You may need to adjust the -march option too.
Your
On Sunday March 22 2015 21:35:47 Samir Aguiar wrote:
> I remember that somewhere during the makefile generation qmake runs
> xcrun --find clang
> and uses the output as the compiler path, ignoring what you set in
> QMAKE_CXX.
Yes, that's in qtbase/configure, and it basically determines the compil
> On Sunday March 22 2015 19:01:55 René J.V. Bertin wrote:
>
> I found the immediate culprit: build/qtbase/qmake/.qmake.stash
> This file sets QMAKE_MAC_SDK.macx-clang.macosx.QMAKE_CC etc. to values that
> are completely unrelated to what's specified in the mkspec file. I think that
> also expl
On Sunday March 22 2015 19:01:55 René J.V. Bertin wrote:
I found the immediate culprit: build/qtbase/qmake/.qmake.stash
This file sets QMAKE_MAC_SDK.macx-clang.macosx.QMAKE_CC etc. to values that are
completely unrelated to what's specified in the mkspec file. I think that also
explains another
You are forgetting about QtWebEngine. It needs opengl of some sort
regardless of whether you use Qml or QWidgets.
On Sun, Mar 22, 2015, 09:30 Agocs Laszlo
wrote:
> As long as the application is pure widgets, without ever using QOpenGL/QGL
> classes or QQuickWidget, it will not attempt to initial
Hi,
How come that the bootstrap qmake ignores the mkspec's CMAKE_CC and CMAKE_CXX?
I see `/usr/bin/clang++` and `/Developer/usr/bin/clang` (for C and ObjC++) when
configure runs the config.test tests, and this causes problems because I need
to use the clang compiler specified in my mkspec.
NB:
As long as the application is pure widgets, without ever using QOpenGL/QGL
classes or QQuickWidget, it will not attempt to initialize any OpenGL stuff.
(if that's not the case, it's a bug, we had some of these recently, like
QTBUG-43832) This means that not having OpenGL or ANGLE working (or ava
On 22 March 2015 at 10:28, Nikos Chantziaras wrote:
> For applications that don't use Qml and only use QWidget, does it matter
> whether Qt was built with OpenGL or Angle on Windows?
It still matters because
1) ANGLE means extra dependencies to be shipped along your app
2) ANGLE does not work on
Hello,
Sorry if this has already come up recently: what are the compiler requirements
to build Qt 5.3.2 on OS X 10.6.8? I just discovered that Apple gcc 4.2 fails on
qprintengine_mac.mm, and Apple clang version 3 (211.10.1, the one shipped with
the sole Xcode 4 for 10.6) fails during the config
> On 21/03/15 20:19, Thiago Macieira wrote:
> > On Thursday 19 March 2015 14:41:24 Nikos Chantziaras wrote:
> >> "Qt 5.5 will provide support for Windows 10 (when available) and RedHat
> >> Enterprise Linux 6.6."
> >>
> >> From http://blog.qt.io/blog/2015/03/17/qt-5-5-alpha-available/
> >
> > RHE
On 21/03/15 20:19, Thiago Macieira wrote:
> On Thursday 19 March 2015 14:41:24 Nikos Chantziaras wrote:
>> "Qt 5.5 will provide support for Windows 10 (when available) and RedHat
>> Enterprise Linux 6.6."
>>
>> From http://blog.qt.io/blog/2015/03/17/qt-5-5-alpha-available/
>
> RHEL 6.6 comes with
For applications that don't use Qml and only use QWidget, does it matter
whether Qt was built with OpenGL or Angle on Windows?
As far as I can tell, GL/Angle is only used by Qml. Is that true? Can
there be any circumstances where a non-Qml application might error out
if running with an OpenGL-b
15 matches
Mail list logo
