Re: [Interest] Force use of QMAKE CXXFLAGS set through ENV Var

2018-10-16 Thread Oliver Niebuhr 

Morning Thiago, morning List.

After more testing, I found out what the problem was.

The Flag must be passed first or it will not work / gets 
ignored/overwritten, when passing the other Configure Flags:


Example:
* %SystemDrive%\qt5srcgit\qt5\configure QMAKE_CFLAGS=-pipe 
QMAKE_CXXFLAGS=-pipe -verbose -platform win32-g++ -c++std c++1z 
-opensource -confirm-license [...]


In the end, it was that easy.
Or like Homer would say: "DOH!" :)

Thanks!
Have a great Day everyone.
Oliver

On 16.10.2018 17:17, Thiago Macieira wrote:

On Tuesday, 16 October 2018 00:51:19 PDT Oliver Niebuhr wrote:

* %SystemDrive%\qt5srcgit\qt5\configure -verbose -platform win32-g++
-c++std c++1z -opensource -confirm-license QMAKE_CXXFLAGS+=-pipe


This one should work, though maybe with = instead of +=.


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Issue with VirtualKeyboad and Wayland compositor.

2018-10-16 Thread Christian Gagneraud 
On Wed, 17 Oct 2018 at 13:51, Christian Gagneraud  wrote:
>
> I'm running the QtWayland 'pure-qml' example on an imx61 board with
> linuxfb QPA, Qt-5.11.1 (I'm waiting for a 5.11.2 build).
> I followed instructions from
> http://doc.qt.io/qt-5/qtvirtualkeyboard-deployment-guide.html#using-qt-virtual-keyboard-with-qt-wayland.
> The wayland client is the QtWidget's 'wiggly' example.
>
> When I click on the QLineEdit of Wiggly, the VKB pops up, but every
> key i tap send QKeyEvent to wiggly, where the key code is always null
> (zero).

So i've run the same setup on Linux Desktop with Qt-5.11.1 and
Qt-5.11.2 and it works as expected in both cases.
I have as well enabled WAYLAND_DEBUG, and discovered that the problem
lies somewhere b/w Qt VKB and QWaylandCompositor, here is a trace that
show the lost of the key code:

Logs from pure-qml:
...
qt.virtualkeyboard: InputContextsendKeyClick(): 16777219
[2541671.231] -> zwp_text_input_v2@14.keysym(0, 0, 1, 0)
[2541671.480] -> zwp_text_input_v2@14.keysym(0, 0, 0, 0)
...

Will investigate, to see the difference of wayland version b/w Linux
Desktop and our custom embedded Linux distro.
Chris


>
> The key codes are correct on the wayland compositor side, from Qt logging:
> qt.virtualkeyboard: InputEngine::virtualKeyPress(): Qt::Key(Key_O) "O"
> QFlags(ShiftModifier) false
> qt.virtualkeyboard: InputEngine::virtualKeyRelease(): Qt::Key(Key_O)
> "O" QFlags(ShiftModifier)
> qt.virtualkeyboard: InputContextsendKeyClick(): 79
>
> But from Wiggly (dumping QKeyEvent via eventFilter on the line edit):
> QKeyEvent(KeyRelease, 0)
> QKeyEvent(KeyPress, 0)
> QKeyEvent(KeyRelease, 0)
> QKeyEvent(KeyPress, 0)
> QKeyEvent(KeyRelease, 0)
>
> All of the above is done with QtCreator:
>
> Wiggly is run with "-platform wayland" command line arguments and the
> following 'Clean Run Environment':
> QML2_IMPORT_PATH=/usr/lib/qt-5.11.1-imx61-shared/qml
> QT_PLUGIN_PATH=/usr/lib/qt-5.11.1-imx61-shared/plugins
> QT_QPA_PLATFORM=wayland
> XDG_RUNTIME_DIR=/tmp
>
> pure-qml is run with "-platform linuxfb -plugin evdevtouch" command
> line arguments and the following 'Clean Run Environment':
> QML2_IMPORT_PATH=/usr/lib/qt-5.11.1-imx61-shared/qml
> QT_IM_MODULE=qtvirtualkeyboard
> QT_LOGGING_DEBUG=1
> QT_LOGGING_RULES=qt.virtualkeyboard=true;qt.qpa.wayland*=true;
> QT_PLUGIN_PATH=/usr/lib/qt-5.11.1-imx61-shared/plugins
> QT_QPA_FB_DISABLE_INPUT=1
> QT_QPA_FONTDIR=/usr/share/fonts
> XDG_RUNTIME_DIR=/tmp
> ___QML_IMPORT_TRACE=1
> ___QT_DEBUG_PLUGINS=1
>
> Any idea about what is going on? As anyone successfully use such a setup?
> Any tip on how to debug this further?
>
> Thanks,
> Chris
>
> Notes:
>
> I have issues with udev and /dev/input, not sure if this can influence
> the VKB. I'm currently waiting for a fix from our platform team.
>
> Full log from pure-qml:
>
> QIconvCodec::convertToUnicode: using Latin-1 for conversion, iconv_open failed
> QIconvCodec::convertFromUnicode: using Latin-1 for conversion, iconv_open 
> failed
> Failed to open tty (No such device)
> This plugin does not support createPlatformOpenGLContext!
> QtCompositor: Failed to initialize EGL display. Could not get
> EglDisplay for window.
> qt.virtualkeyboard: InputContext::setLocale(): "en_GB"
> qt.virtualkeyboard: PlatformInputContext::setLocale():
> QLocale(English, Latin, UnitedKingdom)
> qt.virtualkeyboard: PlatformInputContext::update():
> QFlags(ImInputItemClipRectangle)
> qt.virtualkeyboard: PlatformInputContext::update():
> QFlags(ImInputItemClipRectangle)
> qt.virtualkeyboard: PlatformInputContext::setFocusObject():
> QQuickRootItem(0x80368)
> qt.virtualkeyboard: PlatformInputContext::update():
> QFlags(ImQueryAll)
> qt.virtualkeyboard: PlatformInputContext::commit()
> qt.virtualkeyboard: PlatformInputContext::update():
> QFlags(ImInputItemClipRectangle)
> qt.virtualkeyboard: PlatformInputContext::setFocusObject():
> Chrome_QMLTYPE_4(0x321f98)
> qt.virtualkeyboard: PlatformInputContext::update():
> QFlags(ImQueryAll)
> qt.virtualkeyboard: PlatformInputContext::update():
> QFlags(ImEnabled|ImQueryInput)
> qt.virtualkeyboard: InputContext::setFocus(): true
> qt.virtualkeyboard: InputEngine::setInputMethod():
> QtVirtualKeyboard::PlainInputMethod(0xa51e0)
> qt.virtualkeyboard: InputEngine::setInputMode():
> QtVirtualKeyboard::InputEngine::InputMode(Latin)
> qt.virtualkeyboard: PlatformInputContext::reset()
> qt.virtualkeyboard: PlatformInputContext::update():
> QFlags(ImEnabled|ImMicroFocus|ImCursorPosition|ImSurroundingText|ImCurrentSelection|ImAnchorPosition)
> qt.virtualkeyboard: InputEngine::reselect(): 12 QFlags(0x1|0x2)
> qt.virtualkeyboard: PlatformInputContext::reset()
> qt.virtualkeyboard: PlatformInputContext::update():
> QFlags(ImEnabled|ImMicroFocus)
> qt.virtualkeyboard: PlatformInputContext::showInputPanel()
> qt.virtualkeyboard: InputEngine::virtualKeyPress():
> Qt::Key(Key_Backspace) "" QFlags(ShiftModifier)
> true
> qt.virtualkeyboard: InputEngine::virtualKeyRelease():
> Qt::Key(Key_Backspace) ""

[Interest] Issue with VirtualKeyboad and Wayland compositor.

2018-10-16 Thread Christian Gagneraud 
I'm running the QtWayland 'pure-qml' example on an imx61 board with
linuxfb QPA, Qt-5.11.1 (I'm waiting for a 5.11.2 build).
I followed instructions from
http://doc.qt.io/qt-5/qtvirtualkeyboard-deployment-guide.html#using-qt-virtual-keyboard-with-qt-wayland.
The wayland client is the QtWidget's 'wiggly' example.

When I click on the QLineEdit of Wiggly, the VKB pops up, but every
key i tap send QKeyEvent to wiggly, where the key code is always null
(zero).

The key codes are correct on the wayland compositor side, from Qt logging:
qt.virtualkeyboard: InputEngine::virtualKeyPress(): Qt::Key(Key_O) "O"
QFlags(ShiftModifier) false
qt.virtualkeyboard: InputEngine::virtualKeyRelease(): Qt::Key(Key_O)
"O" QFlags(ShiftModifier)
qt.virtualkeyboard: InputContextsendKeyClick(): 79

But from Wiggly (dumping QKeyEvent via eventFilter on the line edit):
QKeyEvent(KeyRelease, 0)
QKeyEvent(KeyPress, 0)
QKeyEvent(KeyRelease, 0)
QKeyEvent(KeyPress, 0)
QKeyEvent(KeyRelease, 0)

All of the above is done with QtCreator:

Wiggly is run with "-platform wayland" command line arguments and the
following 'Clean Run Environment':
QML2_IMPORT_PATH=/usr/lib/qt-5.11.1-imx61-shared/qml
QT_PLUGIN_PATH=/usr/lib/qt-5.11.1-imx61-shared/plugins
QT_QPA_PLATFORM=wayland
XDG_RUNTIME_DIR=/tmp

pure-qml is run with "-platform linuxfb -plugin evdevtouch" command
line arguments and the following 'Clean Run Environment':
QML2_IMPORT_PATH=/usr/lib/qt-5.11.1-imx61-shared/qml
QT_IM_MODULE=qtvirtualkeyboard
QT_LOGGING_DEBUG=1
QT_LOGGING_RULES=qt.virtualkeyboard=true;qt.qpa.wayland*=true;
QT_PLUGIN_PATH=/usr/lib/qt-5.11.1-imx61-shared/plugins
QT_QPA_FB_DISABLE_INPUT=1
QT_QPA_FONTDIR=/usr/share/fonts
XDG_RUNTIME_DIR=/tmp
___QML_IMPORT_TRACE=1
___QT_DEBUG_PLUGINS=1

Any idea about what is going on? As anyone successfully use such a setup?
Any tip on how to debug this further?

Thanks,
Chris

Notes:

I have issues with udev and /dev/input, not sure if this can influence
the VKB. I'm currently waiting for a fix from our platform team.

Full log from pure-qml:

QIconvCodec::convertToUnicode: using Latin-1 for conversion, iconv_open failed
QIconvCodec::convertFromUnicode: using Latin-1 for conversion, iconv_open failed
Failed to open tty (No such device)
This plugin does not support createPlatformOpenGLContext!
QtCompositor: Failed to initialize EGL display. Could not get
EglDisplay for window.
qt.virtualkeyboard: InputContext::setLocale(): "en_GB"
qt.virtualkeyboard: PlatformInputContext::setLocale():
QLocale(English, Latin, UnitedKingdom)
qt.virtualkeyboard: PlatformInputContext::update():
QFlags(ImInputItemClipRectangle)
qt.virtualkeyboard: PlatformInputContext::update():
QFlags(ImInputItemClipRectangle)
qt.virtualkeyboard: PlatformInputContext::setFocusObject():
QQuickRootItem(0x80368)
qt.virtualkeyboard: PlatformInputContext::update():
QFlags(ImQueryAll)
qt.virtualkeyboard: PlatformInputContext::commit()
qt.virtualkeyboard: PlatformInputContext::update():
QFlags(ImInputItemClipRectangle)
qt.virtualkeyboard: PlatformInputContext::setFocusObject():
Chrome_QMLTYPE_4(0x321f98)
qt.virtualkeyboard: PlatformInputContext::update():
QFlags(ImQueryAll)
qt.virtualkeyboard: PlatformInputContext::update():
QFlags(ImEnabled|ImQueryInput)
qt.virtualkeyboard: InputContext::setFocus(): true
qt.virtualkeyboard: InputEngine::setInputMethod():
QtVirtualKeyboard::PlainInputMethod(0xa51e0)
qt.virtualkeyboard: InputEngine::setInputMode():
QtVirtualKeyboard::InputEngine::InputMode(Latin)
qt.virtualkeyboard: PlatformInputContext::reset()
qt.virtualkeyboard: PlatformInputContext::update():
QFlags(ImEnabled|ImMicroFocus|ImCursorPosition|ImSurroundingText|ImCurrentSelection|ImAnchorPosition)
qt.virtualkeyboard: InputEngine::reselect(): 12 QFlags(0x1|0x2)
qt.virtualkeyboard: PlatformInputContext::reset()
qt.virtualkeyboard: PlatformInputContext::update():
QFlags(ImEnabled|ImMicroFocus)
qt.virtualkeyboard: PlatformInputContext::showInputPanel()
qt.virtualkeyboard: InputEngine::virtualKeyPress():
Qt::Key(Key_Backspace) "" QFlags(ShiftModifier)
true
qt.virtualkeyboard: InputEngine::virtualKeyRelease():
Qt::Key(Key_Backspace) "" QFlags(ShiftModifier)
qt.virtualkeyboard: InputContextsendKeyClick(): 16777219
...

Not sure if the iconv and tty warnings are related.

Full log from wiggly:

QIconvCodec::convertToUnicode: using Latin-1 for conversion, iconv_open failed
QIconvCodec::convertFromUnicode: using Latin-1 for conversion, iconv_open failed
Using Wayland-EGL
EGL not available
Using the 'xdg-shell-v6' shell integration
QFocusEvent(FocusIn, ActiveWindowFocusReason)
QKeyEvent(KeyPress, 0) 0
QKeyEvent(KeyRelease, 0) 0
...

Currently EGL is not ready, hence the warnings, I beleive this is not
an issue here as QtWayland will fallback to SHM buffers.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] [Qt3D] Assimp OBJ importer can not import a file with 500MB size

2018-10-16 Thread Saif Suleiman 
Why then QMesh can import the geometry data even if it is 1GB file ?
Thank you.



On Tue, Oct 16, 2018 at 5:53 PM Olivier B. <
perso.olivier.barthel...@gmail.com> wrote:

> Assimp 4.1, integrated in qt 5.11.1, already added stream reading of
> obj files, and is the most recent version. You will have to raise an
> issue to assimp IMO, then if it can be improved, rebuild qt with that
> new assimp version
> Le mar. 16 oct. 2018 à 16:26, Saif Suleiman  a
> écrit :
> >
> > Hi,
> > As the title says, i can not import a 500MB obj file ( 6 million
> vertices and 11 million faces ) using QSceneloader.
> >
> > getting this msg :
> > Qt3D.AssimpImporter: Assimp scene import failed OBJ: Too many vertices,
> would run out of memory
> >
> > Qt3D.Renderer.SceneLoaders: class Qt3DCore::QEntity *__cdecl
> Qt3DRender::Render::LoadSceneJob::tryLoadScene(class
> Qt3DRender::Render::Scene *,enum Qt3DRender::QSceneLoader::Status &,const
> class QStringList &,const class std::function Qt3DRender::QSceneImporter *)> &) Failed to import
> QUrl("file:///C:/Users/USER/Downloads/a.obj") with errors ("OBJ: Too many
> vertices, would run out of memory")
> >
> >
> > Thanks in advance.
> >
> > ___
> > Interest mailing list
> > Interest@qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] [Qt3D] Assimp OBJ importer can not import a file with 500MB size

2018-10-16 Thread Saif Suleiman 
 sadly the app for 3D printing, which they use obj and stl formats the most.
Thanks.


On Tue, Oct 16, 2018 at 8:07 PM Giuseppe D'Angelo via Interest <
interest@qt-project.org> wrote:

> Il 16/10/18 16:26, Saif Suleiman ha scritto:
> > Hi,
> > As the title says, i can not import a *500MB* obj file *( 6 million
> > vertices and 11 million faces )* using QSceneloader.
>
> I know it's not a solution, but... ditching .obj for such a use case?
> You really want a real 3D format for these sizes (GLTF comes to mind).
>
> My 2 c,
> --
> Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
> KDAB (France) S.A.S., a KDAB Group company
> Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
> KDAB - The Qt, C++ and OpenGL Experts
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] [Qt3D] Assimp OBJ importer can not import a file with 500MB size

2018-10-16 Thread Saif Suleiman 
 Why then QMesh can import the geometry data even if it is 1GB file ?
Thank you.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] [Qt3D] Assimp OBJ importer can not import a file with 500MB size

2018-10-16 Thread Giuseppe D'Angelo via Interest 

Il 16/10/18 16:26, Saif Suleiman ha scritto:

Hi,
As the title says, i can not import a *500MB* obj file *( 6 million 
vertices and 11 million faces )* using QSceneloader.


I know it's not a solution, but... ditching .obj for such a use case? 
You really want a real 3D format for these sizes (GLTF comes to mind).


My 2 c,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts



smime.p7s
Description: Firma crittografica S/MIME
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Force use of QMAKE CXXFLAGS set through ENV Var

2018-10-16 Thread Thiago Macieira 
On Tuesday, 16 October 2018 00:51:19 PDT Oliver Niebuhr wrote:
> * %SystemDrive%\qt5srcgit\qt5\configure -verbose -platform win32-g++
> -c++std c++1z -opensource -confirm-license QMAKE_CXXFLAGS+=-pipe

This one should work, though maybe with = instead of +=.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center



___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] [Qt3D] Assimp OBJ importer can not import a file with 500MB size

2018-10-16 Thread Olivier B. 
Assimp 4.1, integrated in qt 5.11.1, already added stream reading of
obj files, and is the most recent version. You will have to raise an
issue to assimp IMO, then if it can be improved, rebuild qt with that
new assimp version
Le mar. 16 oct. 2018 à 16:26, Saif Suleiman  a écrit :
>
> Hi,
> As the title says, i can not import a 500MB obj file ( 6 million vertices and 
> 11 million faces ) using QSceneloader.
>
> getting this msg :
> Qt3D.AssimpImporter: Assimp scene import failed OBJ: Too many vertices, would 
> run out of memory
>
> Qt3D.Renderer.SceneLoaders: class Qt3DCore::QEntity *__cdecl 
> Qt3DRender::Render::LoadSceneJob::tryLoadScene(class 
> Qt3DRender::Render::Scene *,enum Qt3DRender::QSceneLoader::Status &,const 
> class QStringList &,const class std::function Qt3DRender::QSceneImporter *)> &) Failed to import 
> QUrl("file:///C:/Users/USER/Downloads/a.obj") with errors ("OBJ: Too many 
> vertices, would run out of memory")
>
>
> Thanks in advance.
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] hmac sha256

2018-10-16 Thread Jérôme Godbout 
Ah, sorry about that, I made a typo, the 3rd one is giving the proper
result when I don't make a mistake by copy/paste (I did swap the api_key
and api_secret when calling my function, d'oh).

This is indeed correct:
QMessageAuthenticationCode::hash(payload, m_api_secret,
QCryptographicHash::Sha256).toHex();

Thanks and sorry about that.

On Mon, 15 Oct 2018 at 18:11, Hamish Moffatt 
wrote:

> On 16/10/18 08:16, Jérôme Godbout wrote:
>
> Hi,
> I'm trying to find the C++ equivalent of this python:
> *import hashlib*
> *import hmac*
> *hmac.new(bytearray(m_api_secret, 'utf-8'), bytearray(payload, 'utf-8'),
> hashlib.sha256).hexdigest()*
>
> Or my Javascript equivalent (both give the same results):
> crypto.createHmac("sha256", m_api_secret).update(payload).digest("hex");
>
> I have try the following:
>
>- QMessageAuthenticationCode::hash(payload,
>QByteArray::fromHex(m_api_secret), QCryptographicHash::Sha256).toHex();
>- QMessageAuthenticationCode::hash(payload,
>QByteArray::fromHex(m_api_secret), QCryptographicHash::Sha3_256).toHex();
>- QMessageAuthenticationCode::hash(payload, m_api_secret,
>QCryptographicHash::Sha256).toHex();
>- QMessageAuthenticationCode::hash(payload, m_api_secret,
>QCryptographicHash::Sha3_256).toHex();
>- QMessageAuthenticationCode::hash(QByteArray::fromHex(payload),
>QByteArray::fromHex(m_api_secret), QCryptographicHash::Sha256).toHex();
>- QMessageAuthenticationCode::hash(QByteArray::fromHex(payload),
>QByteArray::fromHex(m_api_secret), QCryptographicHash::Sha3_256).toHex();
>
> But I never get the same results as the Python or Javascript one. Maybe
> I'm using the wrong class here. Anybody have a good pointer on how to do
> this?
> Any good hmac sha256 class to perform this?
>
>
> In Python you encoded the key and payload as utf-8 before hashing, but you
> didn't mention the encoding in C++.
>
> What's in m_api_secret and payload? If they are hex strings then you
> definitely need the fromHex.
>
>
> Hamish
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>


-- 



RAPPROCHEZ LA DISTANCE


*Jérôme Godbout*Senior Software Developer

*p:* +1 (418) 800-1073 ext.:109

*m:* +1 (581) 777-0050

amotus.ca 
statum-iot.com
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] [Qt3D] Assimp OBJ importer can not import a file with 500MB size

2018-10-16 Thread Saif Suleiman 
Hi,
As the title says, i can not import a *500MB* obj file *( 6 million
vertices and 11 million faces )* using QSceneloader.

getting this msg :
Qt3D.AssimpImporter: Assimp scene import failed OBJ: Too many vertices,
would run out of memory

Qt3D.Renderer.SceneLoaders: class Qt3DCore::QEntity *__cdecl
Qt3DRender::Render::LoadSceneJob::tryLoadScene(class
Qt3DRender::Render::Scene *,enum Qt3DRender::QSceneLoader::Status &,const
class QStringList &,const class std::function &) Failed to import
QUrl("file:///C:/Users/USER/Downloads/a.obj") with errors ("OBJ: Too many
vertices, would run out of memory")


Thanks in advance.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.12 Official packages for MinGW 64 bit?

2018-10-16 Thread Andy 
Yes - that's what I'm doing.

I have > 40 extra DLLs in there. I hope they're the right ones and I hope
it works on all systems.

With MinGW it was straightforward and I didn't have to try it and hope for
the best.

---
Andy Maloney  //  https://asmaloney.com
twitter ~ @asmaloney 



On Tue, Oct 16, 2018 at 9:33 AM Sze Howe Koh  wrote:

> On Tue, 16 Oct 2018 at 12:55, Andy  wrote:
> >
> > Yes - that's exactly why I was asking.
> >
> > I switched to MSVC specifically because I need WebEngine but would much
> rather use MinGW or Clang.
> >
> > I have users who don't have admin privileges, so packaging MSVC-built
> applications is a big headache.
>
> Your users only need admin priviledges if you ask them to run the MSVC
> Redistributable installer.
>
> If I'm not mistaken, the EULA allows you to copy the required MSVC
> DLLs into your application folder instead. See
>
> https://social.msdn.microsoft.com/Forums/en-US/8089a33c-ddeb-48e1-92c3-609e43ca96a2/msvcrt-redistributable-wherehowdocumentationlicensing-
> for example.
>
>
> Regards,
> Sze-Howe
>
> > ---
> > Andy Maloney  //  https://asmaloney.com
> > twitter ~ @asmaloney
> >
> >
> >
> > On Tue, Oct 16, 2018 at 3:58 AM 黄其泽  wrote:
> >>
> >> I heard that the upstream Chromium supports clang for windows. Will Qt
> official package provide clang version?
> >>
> >> Distributing windows desktop software built with msvc is a big trouble.
> As the msvc redistribution packages require administrator privilege, and
> fail to install in many computer.
> >>
> >> Kai Koehne  于2018年10月16日周二 下午2:32写道：
> >>>
> >>> > -Original Message-
> >>> > [...]
> >>> > I don't know how the coin stuff works, but does this mean that there
> will be
> >>> > official MinGW 64 bit packages for 5.12?
> >>> >
> >>> > If so, will WebEngine be included?
> >>>
> >>> No. Qt WebEngine currently supports only MSVC 2017.
> >>>
> >>> Kai
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.12 Official packages for MinGW 64 bit?

2018-10-16 Thread Elvis Stansvik 
Den tis 16 okt. 2018 kl 15:33 skrev Sze Howe Koh :
>
> On Tue, 16 Oct 2018 at 12:55, Andy  wrote:
> >
> > Yes - that's exactly why I was asking.
> >
> > I switched to MSVC specifically because I need WebEngine but would much 
> > rather use MinGW or Clang.
> >
> > I have users who don't have admin privileges, so packaging MSVC-built 
> > applications is a big headache.
>
> Your users only need admin priviledges if you ask them to run the MSVC
> Redistributable installer.
>
> If I'm not mistaken, the EULA allows you to copy the required MSVC
> DLLs into your application folder instead. See
> https://social.msdn.microsoft.com/Forums/en-US/8089a33c-ddeb-48e1-92c3-609e43ca96a2/msvcrt-redistributable-wherehowdocumentationlicensing-
> for example.

This is what we do, it's what Microsoft calls "app-local deployment"
(copying in the DLLs). It's not what they recommend, but we've found
this is the easiest path, especially when using CMake's fixup_bundle
combined with windeployqt.

Here's one of Microsofts blogs explaining their stance on app-local
deployment: 
https://blogs.msdn.microsoft.com/vcblog/2016/04/18/c-runtime-deployment-why-choosing-applocal/

Elvis

>
>
> Regards,
> Sze-Howe
>
> > ---
> > Andy Maloney  //  https://asmaloney.com
> > twitter ~ @asmaloney
> >
> >
> >
> > On Tue, Oct 16, 2018 at 3:58 AM 黄其泽  wrote:
> >>
> >> I heard that the upstream Chromium supports clang for windows. Will Qt 
> >> official package provide clang version?
> >>
> >> Distributing windows desktop software built with msvc is a big trouble. As 
> >> the msvc redistribution packages require administrator privilege, and fail 
> >> to install in many computer.
> >>
> >> Kai Koehne  于2018年10月16日周二 下午2:32写道：
> >>>
> >>> > -Original Message-
> >>> > [...]
> >>> > I don't know how the coin stuff works, but does this mean that there 
> >>> > will be
> >>> > official MinGW 64 bit packages for 5.12?
> >>> >
> >>> > If so, will WebEngine be included?
> >>>
> >>> No. Qt WebEngine currently supports only MSVC 2017.
> >>>
> >>> Kai
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.12 Official packages for MinGW 64 bit?

2018-10-16 Thread Sze Howe Koh 
On Tue, 16 Oct 2018 at 12:55, Andy  wrote:
>
> Yes - that's exactly why I was asking.
>
> I switched to MSVC specifically because I need WebEngine but would much 
> rather use MinGW or Clang.
>
> I have users who don't have admin privileges, so packaging MSVC-built 
> applications is a big headache.

Your users only need admin priviledges if you ask them to run the MSVC
Redistributable installer.

If I'm not mistaken, the EULA allows you to copy the required MSVC
DLLs into your application folder instead. See
https://social.msdn.microsoft.com/Forums/en-US/8089a33c-ddeb-48e1-92c3-609e43ca96a2/msvcrt-redistributable-wherehowdocumentationlicensing-
for example.


Regards,
Sze-Howe

> ---
> Andy Maloney  //  https://asmaloney.com
> twitter ~ @asmaloney
>
>
>
> On Tue, Oct 16, 2018 at 3:58 AM 黄其泽  wrote:
>>
>> I heard that the upstream Chromium supports clang for windows. Will Qt 
>> official package provide clang version?
>>
>> Distributing windows desktop software built with msvc is a big trouble. As 
>> the msvc redistribution packages require administrator privilege, and fail 
>> to install in many computer.
>>
>> Kai Koehne  于2018年10月16日周二 下午2:32写道：
>>>
>>> > -Original Message-
>>> > [...]
>>> > I don't know how the coin stuff works, but does this mean that there will 
>>> > be
>>> > official MinGW 64 bit packages for 5.12?
>>> >
>>> > If so, will WebEngine be included?
>>>
>>> No. Qt WebEngine currently supports only MSVC 2017.
>>>
>>> Kai
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.12 Official packages for MinGW 64 bit?

2018-10-16 Thread Andy 
Yes - that's exactly why I was asking.

I switched to MSVC specifically because I need WebEngine but would much
rather use MinGW or Clang.

I have users who don't have admin privileges, so packaging MSVC-built
applications is a big headache.

---
Andy Maloney  //  https://asmaloney.com
twitter ~ @asmaloney 



On Tue, Oct 16, 2018 at 3:58 AM 黄其泽  wrote:

> I heard that the upstream Chromium supports clang for windows. Will Qt
> official package provide clang version?
>
> Distributing windows desktop software built with msvc is a big trouble. As
> the msvc redistribution packages require administrator privilege, and fail
> to install in many computer.
>
> Kai Koehne  于2018年10月16日周二 下午2:32写道：
>
>> > -Original Message-
>> > [...]
>> > I don't know how the coin stuff works, but does this mean that there
>> will be
>> > official MinGW 64 bit packages for 5.12?
>> >
>> > If so, will WebEngine be included?
>>
>> No. Qt WebEngine currently supports only MSVC 2017.
>>
>> Kai
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>>
>
>
> --
> Python及Qt相关Blog：http://hgoldfish.com/
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] proper (silent) exit in response to SIGHUP?

2018-10-16 Thread René J . V . Bertin 
On Tuesday October 16 2018 06:47:04 Kai Koehne wrote:

>There's a good chance this got fixed in Qt 5.12:
>
> https://codereview.qt-project.org/#/c/203587/

Ah! I was already building the Assistant from the dev branch (against Qt 5.9 
currently) so I should be able to test this (but only in the Assistant itself 
because this standalone build uses a static QtHelp library, evidently...)

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.12 Official packages for MinGW 64 bit?

2018-10-16 Thread 黄其泽 
I heard that the upstream Chromium supports clang for windows. Will Qt
official package provide clang version?

Distributing windows desktop software built with msvc is a big trouble. As
the msvc redistribution packages require administrator privilege, and fail
to install in many computer.

Kai Koehne  于2018年10月16日周二 下午2:32写道：

> > -Original Message-
> > [...]
> > I don't know how the coin stuff works, but does this mean that there
> will be
> > official MinGW 64 bit packages for 5.12?
> >
> > If so, will WebEngine be included?
>
> No. Qt WebEngine currently supports only MSVC 2017.
>
> Kai
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>


-- 
Python及Qt相关Blog：http://hgoldfish.com/
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Force use of QMAKE CXXFLAGS set through ENV Var

2018-10-16 Thread Oliver Niebuhr 

Oops. Small Correction. Dumb Copy and Paste Error. It is:
* SET QMAKE=-project "QMAKE_CXXFLAGS+=-pipe"

And I forgot to mention, I also tried:
* doskey g++=g++ -pipe
* doskey gcc=gcc -pipe
Oliver

On 16/10/2018 09:51, Oliver Niebuhr wrote:

Morning everyone.

OS: Windows 10
Compiler: MingW-64, 8.1.0
Qt: 5.12, latest Git (but not really important in that case)

What do I want:
A.) Build Qt5 from Source
A.1.) While forcing "g++" to use the flag "-pipe", without modifying 
"QMAKE.CONF" in the local Git Directory every time.


I tried:
Setting the following Environment Variables in the Windows CMD Shell:

* SET QMAKE="QMAKE_CFLAGS+=-pipe QMAKE_CXXFLAGS+=-pipe"
* SET QMAKE_CFLAGS+="-pipe"
* SET QMAKE_CXXFLAGS+="-pipe"
* SET G++="-pipe"
* SET QMAKE=-project "QMAKE_CXXFLAGS+=-std=c++11"

I tested with and without the --> "" <--

I also tried to use it as a Configure Parameter. For Example:
* %SystemDrive%\qt5srcgit\qt5\configure -verbose -platform win32-g++ 
-c++std c++1z -opensource -confirm-license QMAKE_CXXFLAGS+=-pipe
* %SystemDrive%\qt5srcgit\qt5\configure -verbose -platform win32-g++ 
-c++std c++1z -opensource -confirm-license -device-option 
QMAKE_CXXFLAGS+=-pipe


If anyone could point me to the right Direction, I would be very 
grateful! All the Stuff I have tried, is from the Internet and the Qt5 
Configure Script. And yes, I am aware that it makes not much difference 
using "-pipe" these Days. Its about reducing write cycles on my SSD. And 
also figuring out, how to optimize my Linux Scripts / Windows Batch 
Files further.


Thanks!
Oliver
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Force use of QMAKE CXXFLAGS set through ENV Var

2018-10-16 Thread Oliver Niebuhr 

Morning everyone.

OS: Windows 10
Compiler: MingW-64, 8.1.0
Qt: 5.12, latest Git (but not really important in that case)

What do I want:
A.) Build Qt5 from Source
A.1.) While forcing "g++" to use the flag "-pipe", without modifying 
"QMAKE.CONF" in the local Git Directory every time.


I tried:
Setting the following Environment Variables in the Windows CMD Shell:

* SET QMAKE="QMAKE_CFLAGS+=-pipe QMAKE_CXXFLAGS+=-pipe"
* SET QMAKE_CFLAGS+="-pipe"
* SET QMAKE_CXXFLAGS+="-pipe"
* SET G++="-pipe"
* SET QMAKE=-project "QMAKE_CXXFLAGS+=-std=c++11"

I tested with and without the --> "" <--

I also tried to use it as a Configure Parameter. For Example:
* %SystemDrive%\qt5srcgit\qt5\configure -verbose -platform win32-g++ 
-c++std c++1z -opensource -confirm-license QMAKE_CXXFLAGS+=-pipe
* %SystemDrive%\qt5srcgit\qt5\configure -verbose -platform win32-g++ 
-c++std c++1z -opensource -confirm-license -device-option 
QMAKE_CXXFLAGS+=-pipe


If anyone could point me to the right Direction, I would be very 
grateful! All the Stuff I have tried, is from the Internet and the Qt5 
Configure Script. And yes, I am aware that it makes not much difference 
using "-pipe" these Days. Its about reducing write cycles on my SSD. And 
also figuring out, how to optimize my Linux Scripts / Windows Batch 
Files further.


Thanks!
Oliver
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest