[Interest] Regression? Change of html copied to clipboard from QTextEdit

[Olivier B.]

Some text in QTextEdit now seem to lose style when copypasted in an app
built with Qt-5.15.2
In the appli built with 5.11.1, there is not the issue.
I am copying from one read only QTextEdit to an other writable one.

When overloading QTextEdit to debug clipboard data
in createMimeDataFromSelection(), the resulting html has some differences.
Some  markups became , resulting in text in fixed width style
instead of the original text style.
Those changes are not from the original html printed in the QTextEdit

Original printed text contains mycontent
In createMimeDataFromSelection() with 5.11.1, text contains mycontent
In createMimeDataFromSelection() with 5.15.2, text contains mycontent

The strange thing is that in the second writable QTextEdit, if i copy some
text to clipboard,  are added, not 

Should i create a bug? Or any idea if an option of QTextEdit influences
this?
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] [Development] Multi-Selection behavior of item views breaks drag'n'drop UX - options

[Olivier B.]

Here, we have had an issue when switching from 5.11.1 to 5.15.2, with multi
selection and dragNdrop
Now, if we start a drag n drop, but previously clicked on the item a short
time ago (less than the double click delay), then the view starts multi
selection with the mouse moves instead of starting drag n drop, even if the
mouse leaves the widget area.
This did not happen in 5.11.1 with same user code, and dragging was enabled
on a double-click+move
I'm not sure which behaviour is better, but for our use cases, the former
was more fitted.

Maybe looking at what changed between 5.11.1 and 5.15.2 (and why) could
help your decision?

Le ven. 28 mai 2021 à 14:58, Volker Hilsheimer  a
écrit :

> Cross-posting from the development mailing list in case any of you have a
> strong opinion about this.
>
> Volker
>
>
> > On 28 May 2021, at 13:10, Volker Hilsheimer 
> wrote:
> >
> > Hey Widget fans,
> >
> > I need your opinions on https://bugreports.qt.io/browse/QTBUG-59888
> >
> > The UX resulting from our (strange) choice to trigger selection changes
> on mouse press rather than mouse release is indeed quite horrible, as
> explained in the ticket.
> >
> > The options to fix that seem to be:
> >
> > 1) change the default behavior - always change selection on mouse release
> > 2) change the default behavior if drag (as per dragDropMode)
> > 3) make the "selection trigger" a property
> >
> > None of those options would IMHO result in a change that qualifies for
> stable branches. I’ve for now implemented option 3. This introduces new
> API, so if we agree that this is the way to go then it would ideally be
> merged before 6.2 feature freeze next Friday.
> >
> > https://codereview.qt-project.org/c/qt/qtbase/+/351595
> >
> > However, the possible property values seem oddly specific to this
> problem, and give that this is a 6.2 only change anyway, perhaps it would
> be best to simply change the default, which would then also make Qt
> matching native UIs better (ie Windows Explorer or macOS Finder)?
> >
> > Cheers,
> > Volker
> >
> > ___
> > Development mailing list
> > developm...@qt-project.org
> > https://lists.qt-project.org/listinfo/development
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] New double-click-drag selection in lists in QT 5.15?

[Olivier B.]

Hi,

Somewhere between 5.11.1 and 5.15.2, it seems that if you double-click in a
list widget, and move the mouse down before the second mouse button up,
this now selects multiple lines.

This is breaking a little the drag and drop from those lists, since if you
quickly click twice by mistake on an item to drag, then the following mouse
moves are not considered drag anymore, but item selection.

Has this been a willful change? I found no documentation/bugs about it (and
no way to keep the previous behaviour)
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] no_check_exist is now fatal?

[Olivier B.]

I'm transitioning to 5.15.2 from 5.11. It seems that now, qmake install
rules with config no_check_exist became fatal. Previously, they generated
errors, but the build kept going. Now the builds seem to stop at the first
error. Was this change conscient? (was the previous behaviour considered a
bug?)
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QStringBuilder buffer overflow with string litteral?

[Olivier B.]

Oh, you are right, thanks. I thought the + operator was on a QString and
adding a char would be faster than adding a 1-char string, but it just
changed the char* pointer address instead.

Le lun. 25 janv. 2021 à 15:32, Giuseppe D'Angelo via Interest <
interest@qt-project.org> a écrit :

> Hi,
>
> Il 25/01/21 13:56, Olivier B. ha scritto:
> >  fields += (fields.isEmpty() ? "" : ", ") + '"' + field + '"';
>
> QStringBuilder usage is a red herring, pay close attention at what
> you're doing in the first +: you're summing a const char * (result of
> the ternary operator) with a char; that does not do string concatenation...
>
> > Passing one/both of the operands of the ternary operator as QStrings
> makes the problem disappear.
>
> That however kills the advantage of QStringBuilder. Use QStringView /
> QLatin1String instead.
>
> Tip: always define QT_NO_CAST_FROM_ASCII (or the more lenient
> QT_RESTRICTED_CAST_FROM_ASCII) in any Qt project.
>
> HTH,
> --
> 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
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] QStringBuilder buffer overflow with string litteral?

[Olivier B.]

Compiling with QT 5.11.1 &  QT_USE_QSTRINGBUILDER, i get an error with the
following code block:

  QString generateQuery(const QString& tableName, const QStringList&
columns, int count)
  {
QString fields = "*";
if (!columns.isEmpty())
{
  fields.clear();
  for (const QString& field : columns)
  {
fields += (fields.isEmpty() ? "" : ", ") + '"' + field + '"';
  }
}
...

I just want to build a comma separated list of the items in 'columns',
surrounded by quotes.
But instead of giving "A", "B", "C", this gives UNIQUE (%1)"A"UNIQUE
(%1)"B"UNIQUE (%1)"C"

That UNIQUE (%1) is only found in another cpp file of the same DLL project,
in strings ", UNIQUE (%1)" passed to QString constructors. So not only is
it using the wrong string litteral, it does not read it from the string
start.

Passing one/both of the operands of the ternary operator as QStrings makes
the problem disappear.

Are there things i should be aware of when using QStringBuilder, such as
'do not put expressions on operators, because of macros that will evaluate
them multiple times', or something like that?
String pooling (/GF of visual studio) is not used, if that matters
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] qmake.exe not found at install of qt 5.15.1 build

[Olivier B.]

Looking back at it again.
I see that this attempted install is done in Makefile.qmake-aux, coming
from qtbase/qmake/qmake-aux.pro. This one has 'aux' template, so builds
nothing, just tries to install qmake
In qtbase/qmake, is also qmake.pro, but the starting comment says it is for
QtCreator, not to build qmake. Indeed, in qtbase.pro, only qmake-aux.pro is
in the subdirs list

So i get a qmake.exe built during configure in qtbase/bin/, nothing seems
to try to rebuild it from qtbase into qtbase/qmake/, and you say it is not
supposed to be copied but generated? Iam lost on what to then, except
manually doing the copy myself from bin/ to qmake/ between 'configure' &
'nmake' calls

Le mar. 6 oct. 2020 à 23:21, Thiago Macieira  a
écrit :

> On Tuesday, 6 October 2020 00:28:10 PDT Olivier B. wrote:
> > As you can see, the previous command shows that qmake.exe is in
> qtbase\bin,
> > but the install command is looking for it in qtbase\qmake. Nowhere in the
> > whole build log is qmake copied at that path. What could i be missing?
>
> It doesn't get copied there. That's a secondary build of qmake that should
> have been built from the top-level Makefile in qtbase. It's target
> "sub-qmake-qmake-aux-pro"
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel DPG Cloud Engineering
>
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] QDesktopServices::openUrl() without inheriting environment?

[Olivier B.]

An application needs custom library search path to use it's own versions of
external libraries.
But because of this, when opening files in external applications
using QDesktopServices::openUrl(), the system applications (browser)
registered for the file type will first try to use the application's
version of the libraries, instead of the system ones the browser is
supposed to depend on.
FreeType dependency in particular, seems to make executables that depend on
libfreetype.so.6, name which has been used at least between version 2.6 and
2.9. The newer ones having additional new symbols. The application, here,
uses a 2.7 Freetype, but the browser needs at least FreeType 2.9, so
launching the browser from the application fails because the newer Freetype
symbols are not found.

Is there a way to still use the mechanism to find the application to use
from system settings, but launch the command with the default system
environment, not the one inherited from the application's process
(something like calling the command with env -i) ?
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] qmake.exe not found at install of qt 5.15.1 build

[Olivier B.]

Hi,
I am building qt 5.15.1 on windows /VC++2015/64-bit build. The debug shadow
build seems to run the nmake to build fine, but while running the install
rule, i get the error

C:\sdk\src\qt-everywhere-src-5.15.1\shadow_dbg\qtbase\bin\qmake.exe
-install qinstall -exe
C:\sdk\src\qt-everywhere-src-5.15.1\shadow_dbg\qtbase\qmake\qmake.exe
C:\sdk\polaris7\winnt64\apps\qt-5.15.1\bin\qmake.exe
Error copying
C:\sdk\src\qt-everywhere-src-5.15.1\shadow_dbg\qtbase\qmake\qmake.exe to
C:\sdk\apps\qt-5.15.1\bin\qmake.exe: Cannot open
C:\sdk\src\qt-everywhere-src-5.15.1\shadow_dbg\qtbase\qmake\qmake.exe for
input

As you can see, the previous command shows that qmake.exe is in qtbase\bin,
but the install command is looking for it in qtbase\qmake. Nowhere in the
whole build log is qmake copied at that path. What could i be missing?

I reused a script used to compile 5.12, so i doubt i forgot to run a build
rule?
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QT_DISABLE_DEPRECATED_BEFORE and external headers

[Olivier B.]

If you are using a qwt you build yourself, please find attached a patch for
some public qwt 6.1.2 header to stop depending on QString::null when i
incliude them.
I apply it before building qwt, but it might also work if applied on the
installed headers, not sure. Redeclaring some methods with an other default
argument value should be OK. In that case, the relative paths to the
includes will have to be adjusted obviously

Le mar. 11 févr. 2020 à 07:33, Nyall Dawson  a
écrit :

>  Hi list,
>
> I've been defining QT_DISABLE_DEPRECATED_BEFORE in one of my projects
> to avoid use of deprecated Qt methods (in prep for Qt 6!).
> Unfortunately, one of the external libraries in use by my project
> (qwt) uses the deprecated QString::null member in a public header. If
> I try to bump the DEPRECATED_BEFORE version to 5.9 or later, the
> compilation (rightly) breaks when the headers for this library are
> imported.
>
> I'm wondering if there's anyway around this so that I can avoid
> applying QT_DISABLE_DEPRECATED_BEFORE to these external headers.
>
> As further info:
> - QT_DISABLE_DEPRECATED_BEFORE is defined via cmake
> (ADD_DEFINITIONS(-DQT_DISABLE_DEPRECATED_BEFORE=0x050800))
> - I tried inserting a
> #undef QT_DISABLE_DEPRECATED_BEFORE
> #include "..."
> #def QT_DISABLE_DEPRECATED_BEFORE 0x050800
> block around the library includes, but that had no effect and the
> compilation block still occurred at the point of the #include
>
> Any tips?
>
> Nyall
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>


qstring_null.patch
Description: Binary data
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] FW: How can I implement QModbusClient for MODBUS ASCII mode?

[Olivier B.]

I actually don't understand what we can do for you if you don't know
how to do it. Do you want us to implement it for you?

You can use libmodbus and create classes around it. Or implement
modbus ascii in pure Qt

Le ven. 17 mai 2019 à 11:45, Олег Гаврильченко
 a écrit :
>
>
>
> -Original Message-----
> From: Olivier B. [mailto:perso.olivier.barthel...@gmail.com]
> Sent: Friday, May 17, 2019 12:19 PM
> To: Олег Гаврильченко
> Cc: Interests Qt
> Subject: Re: [Interest] FW: How can I implement QModbusClient for MODBUS 
> ASCII mode?
>
> https://doc.qt.io/qt-5/qtserialbus-modbus-master-example.html
> https://doc.qt.io/qt-5/qtserialbus-modbus-slave-example.html
> https://sourceforge.net/projects/qmodmaster/
>
> Le ven. 17 mai 2019 à 11:10, Олег Гаврильченко  
> a écrit :
> >
> > Hello.
> >
> > I want write QModbusClient/QModubsServer subclasses, that communicate via 
> > MODBUS ASCII mode.
> >
> > How can I make this?
> >
> > ___
> > Interest mailing list
> > Interest@qt-project.org
> > https://lists.qt-project.org/listinfo/interest
> You probably don't understand me. I see all this examples. All example use 
> MODBUS RTU or MODUBS TCP protocol.
> Only this protocols realized in QT in classes QModbusRtuSerialMaster and 
> QModbusRtuSerialMaster. But I want to communicate via MODBUS ASDII mode.
> MODBUS ASII mode not implement in QT. I asked, how I can make it?
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] FW: How can I implement QModbusClient for MODBUS ASCII mode?

[Olivier B.]

https://doc.qt.io/qt-5/qtserialbus-modbus-master-example.html
https://doc.qt.io/qt-5/qtserialbus-modbus-slave-example.html
https://sourceforge.net/projects/qmodmaster/

Le ven. 17 mai 2019 à 11:10, Олег Гаврильченко
 a écrit :
>
> Hello.
>
> I want write QModbusClient/QModubsServer subclasses, that communicate via 
> MODBUS ASCII mode.
>
> How can I make this?
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] [qmake] COPIES broken for recent QT?

[Olivier B.]

Seems fixed in 
https://code.qt.io/cgit/qt/qtbase.git/commit/mkspecs/features/file_copies.prf?h=dev=7227e54445021b8c2ce4f4ab638cc7d43e32a5a7

I'll take back that modif in my qt installs

Le ven. 12 avr. 2019 à 04:15, Thiago Macieira
 a écrit :
>
> On Thursday, 11 April 2019 06:43:25 PDT Olivier B. wrote:
> > I just noticed that my COPIES fail in Qt 5.11.1+ in visual studio
> > solutions. This seems caused by the change in
> > mkspecs/features/file_copies.prf; to use $(QINSTALL) instead of the
> > previous $$QMAKE_COPY.
> > But unlike in makefiles, QINSTALL is not defined in the visual studio
> > solutions :(
>
> Please report this to https://bugreports.qt.io.
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel System Software Products
>
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] [qmake] COPIES broken for recent QT?

[Olivier B.]

I just noticed that my COPIES fail in Qt 5.11.1+ in visual studio
solutions. This seems caused by the change in
mkspecs/features/file_copies.prf; to use $(QINSTALL) instead of the
previous $$QMAKE_COPY.
But unlike in makefiles, QINSTALL is not defined in the visual studio
solutions :(
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Disable -Og when configuring as developer build

[Olivier B.]

qtbase/configure.json says it is "optimize_debug" option that adds it

Le ven. 15 févr. 2019 à 15:13, Konstantin Shegunov
 a écrit :
>
> On Fri, Feb 15, 2019 at 4:05 PM Mitch Curtis  wrote:
>>
>> Is it the -optimize-debug configure flag?
>
>
> No, not really. The configure script adds it by default to all debug builds 
> as far as I could tell. Here's my configure line:
> $> ./configure -developer-build -opensource -confirm-license -nomake examples 
> -nomake tests
>
> and I get this as the compile command being executed:
>
> g++ -c -include .pch/Qt5Gui -pipe -g -Og -std=c++1z -fvisibility=hidden 
> -fvisibility-inlines-hidden -fno-exceptions -Wall -W -Wvla -Wdate-time 
> -Wshift-overflow=2 -Wduplicated-cond -Wno-stringop-overflow -Werror 
> -Wno-error=cpp -Wno-error=deprecated-declarations -Wno-error=strict-overflow 
> -Wno-error=implicit-fallthrough -D_REENTRANT -fPIC -DQT_NO_USING_NAMESPACE 
> -DQT_NO_FOREACH -DENABLE_PIXMAN_DRAWHELPERS 
> -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_BUILD_GUI_LIB -DQT_BUILDING_QT 
> -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT 
> -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS 
> -DQT_DISABLE_DEPRECATED_BEFORE=0x05 -DQT_NO_EXCEPTIONS 
> -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_CORE_LIB -I. -I../../include 
> -I../../include/QtGui -I../../include/QtGui/5.12.2 
> -I../../include/QtGui/5.12.2/QtGui -I.tracegen -isystem /usr/include/libdrm 
> -I../../include/QtCore/5.12.2 -I../../include/QtCore/5.12.2/QtCore 
> -I../../include/QtCore -I.moc -isystem /usr/include/libpng16 
> -I../../mkspecs/linux-g++ -o .obj/qstatictext.o text/qstatictext.cpp
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Wrong compiler caps check or missing /arch:avx?

[Olivier B.]

It seems it is because i didn't have QT_COMPILER_SUPPORTS_SIMD_ALWAYS

Related config test :
Checking for Intrinsics without -mXXX argument...
+ cd /d C:\sdk\src\qt-everywhere-src-5.12.0\shadow_dbg\config.tests\x86_simd
&& C:\sdk\src\qt-everywhere-src-5.12.0\shadow_dbg\qtbase\bin\qmake.exe
"CONFIG -= qt debug_and_release app_bundle lib_bundle" "CONFIG +=
shared warn_off console single_arch" (stripped) "SIMD=aesni avx avx2
sse2 sse3 sse4_1 sse4_2 ssse3"
C:/sdk/src/qt-everywhere-src-5.12.0/qtbase/config.tests/x86_simd
+ cd /d C:\sdk\src\qt-everywhere-src-5.12.0\shadow_dbg\config.tests\x86_simd
&& set MAKEFLAGS=& nmake clean && set MAKEFLAGS=& nmake
> Microsoft (R) Program Maintenance Utility Version 14.00.24210.0
> Copyright (C) Microsoft Corporation.  All rights reserved.
> del main.obj
> del x86_simd.exp
> Impossible de trouver 
> C:\sdk\src\qt-everywhere-src-5.12.0\shadow_dbg\config.tests\x86_simd\x86_simd.exp
> Microsoft (R) Program Maintenance Utility Version 14.00.24210.0
> Copyright (C) Microsoft Corporation.  All rights reserved.
> cl -c -nologo -Zc:wchar_t -FS -Zc:rvalueCast -Zc:inline -Zc:strictStrings 
> -Zc:throwingNew -O2 -MD -W0 -EHsc -DUNICODE -D_UNICODE -DWIN32 
> -D_ENABLE_EXTENDED_ALIGNED_STORAGE -DWIN64 -DQT_COMPILER_SUPPORTS_AESNI 
> -DQT_COMPILER_SUPPORTS_AVX -DQT_COMPILER_SUPPORTS_AVX2 
> -DQT_COMPILER_SUPPORTS_SSE2 -DQT_COMPILER_SUPPORTS_SSE3 
> -DQT_COMPILER_SUPPORTS_SSE4_1 -DQT_COMPILER_SUPPORTS_SSE4_2 
> -DQT_COMPILER_SUPPORTS_SSSE3 -DNDEBUG (stripped) 
> -IC:\sdk\src\qt-everywhere-src-5.12.0\qtbase\mkspecs\win32-msvc -Fo 
> @C:\cygwin\tmp\nm8037.tmp
> main.cpp
> link /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /SUBSYSTEM:CONSOLE 
> "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' 
> version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' 
> processorArchitecture='*'" /MANIFEST:embed /OUT:x86_simd.exe 
> @C:\cygwin\tmp\nm80D4.tmp
> LINK : fatal error LNK1104: cannot open file 'x86_simd.exe'
> NMAKE : fatal error U1077: 'C:\vs2015\vc\bin\amd64\link.EXE' : return code 
> '0x450'
> Stop.
test config.qtbase.tests.x86SimdAlways FAILED

Strange how the link failed. And after a rebuild, the test now passes.
Something else on the computer probably took too much memory and the
linker crashed



Le lun. 21 janv. 2019 à 18:02, Thiago Macieira
 a écrit :
>
> On Monday, 21 January 2019 08:18:16 PST Olivier B. wrote:
> > It seems that code of the cpp that is compiled "if defined
> > QT_COMPILER_SUPPORTS_SSE4_1" (present in my qconfig.h) references code
> > of qdrawingprimitive_sse2_p.h that is defined "if
> > QT_COMPILER_SUPPORTS_HERE(SSE4_1)" (absent because __SSE_4_1__ is not
> > defined in qsimd_p.h, because configure does not add /arch:avx on the
> > command line)
>
> That's an incorrect conclusion. The correct branch of qsimd_p.h for MSVC 2015
> is this:
>
> #elif defined(Q_PROCESSOR_X86) && defined(QT_COMPILER_SUPPORTS_SIMD_ALWAYS)
> #  define QT_COMPILER_SUPPORTS_HERE(x)((__ ## x ## __) ||
> QT_COMPILER_SUPPORTS(x))
>
> The second condition of that macro is QT_COMPILER_SUPPORTS_SSE4_1 again.
>
> > I did not pass any cpu-specific type flags to configure, and i am not
> > sure i want to. What is the proper fix of the cpu checks and flags
> > that will make this build, without making the code dependant on avx or
> > SSE4.1?
>
> MSVC 2015 compiles out of the box and this code is enabled. Your problem is
> elsewhere.
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center
>
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Wrong compiler caps check or missing /arch:avx?

[Olivier B.]

Compiling 5.12.0 with vs 2015
Configure detects SSE up to 4.2 , and AVX up to AVX2

qdrawhelper_sse4.cpp
C:\sdk\src\qt-everywhere-src-5.12.0\qtbase\src\gui\painting\qdrawhelper_sse4.cpp(164):
error C3861: 'qUnpremultiply_sse4': identifier not found
C:\sdk\src\qt-everywhere-src-5.12.0\qtbase\src\gui\painting\qdrawhelper_sse4.cpp(290):
note: see reference to function template instantiation 'void
convertARGBFromARGB32PM_sse4(uint *,const uint *,int)'
being compiled
C:\sdk\src\qt-everywhere-src-5.12.0\qtbase\src\gui\painting\qdrawhelper_sse4.cpp(258):
error C2065: 'qConvertRgba64ToRgb32_sse4': undeclared identifier
C:\sdk\src\qt-everywhere-src-5.12.0\qtbase\src\gui\painting\qdrawhelper_sse4.cpp(326):
note: see reference to function template instantiation 'void
convertARGBFromRGBA64PM_sse4(uint *,const QRgba64 *,int)' being
compiled
C:\sdk\src\qt-everywhere-src-5.12.0\qtbase\src\gui\painting\qdrawhelper_sse4.cpp(258):
warning C4804: '<': unsafe use of type 'bool' in operation
C:\sdk\src\qt-everywhere-src-5.12.0\qtbase\src\gui\painting\qdrawhelper_sse4.cpp(320):
error C2065: 'qConvertArgb32ToA2rgb30_sse4': undeclared identifier
C:\sdk\src\qt-everywhere-src-5.12.0\qtbase\src\gui\painting\qdrawhelper_sse4.cpp(351):
note: see reference to function template instantiation 'void
storeA2RGB30PMFromARGB32PM_sse4(uchar *,const uint
*,int,int,const QVector *,QDitherInfo *)' being compiled

It seems that code of the cpp that is compiled "if defined
QT_COMPILER_SUPPORTS_SSE4_1" (present in my qconfig.h) references code
of qdrawingprimitive_sse2_p.h that is defined "if
QT_COMPILER_SUPPORTS_HERE(SSE4_1)" (absent because __SSE_4_1__ is not
defined in qsimd_p.h, because configure does not add /arch:avx on the
command line)

Adding /arch:avx, or replacing the #if
QT_COMPILER_SUPPORTS_HERE(SSE4_1) by #if defined
QT_COMPILER_SUPPORTS_SSE4_1. The SSE4 test of configure succeeds
without using -arch:avx

I did not pass any cpu-specific type flags to configure, and i am not
sure i want to. What is the proper fix of the cpu checks and flags
that will make this build, without making the code dependant on avx or
SSE4.1?
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] configure does not find my dependencies headers anymore?

[Olivier B.]

Ah, i had an invalid configure option (-gtkstyle) in config.opt, so
configure ignored all the following options to run the tests. I'll try
to not forget it this time.

Is that considered normal behaviour? Couldn't configure either
continue parsing the next command line options, or not start running
the tests if it does not understand the full command line?

Le mar. 8 janv. 2019 à 12:08, Olivier B.
 a écrit :
>
> I am having issues building qt 5.12 on linux, with the same script i
> used to build 5.11.1. Configure seems to ignore all the
> -I/path/to/somedep/include that i have in config.opt (one -Iblabla per
> line), so all the external dependencies are not found
>
> Did something change related to dependency include directory config options?
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] configure does not find my dependencies headers anymore?

[Olivier B.]

I am having issues building qt 5.12 on linux, with the same script i
used to build 5.11.1. Configure seems to ignore all the
-I/path/to/somedep/include that i have in config.opt (one -Iblabla per
line), so all the external dependencies are not found

Did something change related to dependency include directory config options?
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QDir::entry(Info)List on macos

[Olivier B.]

What is the encoding of your source file?
QString constructors interprets char* as if they are UTF-8. If the
source file is encoded in your local encoding, the QString created for
QFile constructor will have a wrong unicode storage of your wanted
filename, then will try to convert what it thinks is UTF into your
local encoding to pass the filename to the system calls. Maybe the mac
explorer can work around this and adjust the displayed name, but the
Filesystem interface of Qt can't because that puts forbidden
characters in the real name?
Le jeu. 15 nov. 2018 à 08:55, Manner Róbert  a écrit :
>
> On 11/14/18 5:34 PM, Thiago Macieira wrote:
> > On Wednesday, 14 November 2018 01:34:17 PST Manner Róbert wrote:
> >> int main() {
> >>   qDebug() << QDir(".").entryList();
> > QCoreApplication missing. Try again with it.
> >
> Tried, without success, still does not display these files. Even tried
> with QDirIterator, that is also working the same (skipping these files).
>
> With further checking I noticed that the files are only not displaying
> if I do not create them with Qt. Eg I created with "touch filenamé". If
> I create the same file with QFile, that seems to be found by these dir
> lists. I know it sounds insane.
>
>
> Locale is utf8:
>
> > locale
> LANG="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_CTYPE="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_ALL="en_US.UTF-8"
>
> The modified source code:
>
> > cat main.cpp
> #include 
> #include 
> #include 
> #include 
> #include 
>
> int main(int argc, char** argv) {
>   QFile file("éáőú");  // This file is visible in the list! But not any
> other I create with touch for example.
>   file.open(QFile::WriteOnly);
>   file.close();
>
>   QCoreApplication app(argc, argv);
>   QDirIterator iterator(".", QDir::Files, QDirIterator::Subdirectories);
>   while (iterator.hasNext())
> {
>   qDebug() << "QDiriterator" << iterator.next();
> }
>
>   qDebug() << QDir(".").entryList(QDir::System | QDir::AllEntries |
> QDir::Hidden);
>
>   qDebug() << QDir(".").entryInfoList(QDir::System | QDir::AllEntries |
> QDir::Hidden);
> }
>
> Thanks in advance for any idea.
>
> Robert
>
> ___
> 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] qmake with release config is called for debug build

[Olivier B.]

You can also use the COPIES qmake variable. It's used in a similar way
as INSTALLS, but instead of being run when you 'make install', it will
be run when you run 'make' of build the generated project in your IDE.
It's usefull when your exe has deps that need to be beside it in the
temp build dir for debugging
Le lun. 12 nov. 2018 à 15:13, Jérôme Godbout  a écrit :
>
> The way you wrote it, it will only copy the file when parsing the .pro/.pri 
> files, you need to make a target and add it to the build sequence.
>
> Here's the doc example:
> mytarget.target = .buildfile
> mytarget.commands = touch $$mytarget.target
> mytarget.depends = mytarget2
>
> mytarget2.commands = @echo Building $$mytarget.target
> QMAKE_EXTRA_TARGETS += mytarget mytarget2
>
> http://doc.qt.io/qt-5/qmake-advanced-usage.html
>
> I still wonder why it's not as simple as the MSBuild target system (I not a 
> lover of MSBuild, but that part was clear and simple) where QMake make it 
> super unfriendly.
>
>
> -Original Message-
> From: Interest  On Behalf 
> Of Alexander Dyagilev
> Sent: November 10, 2018 3:28 AM
> To: interest@qt-project.org
> Subject: [Interest] qmake with release config is called for debug build
>
> Hello,
>
> I'm using the following .pri file:
>
> include(macros.pri)
> win32:CONFIG(release, debug|release) {
>VC_RUNTIME_FOLDER="c:/Program Files (x86)/Microsoft Visual Studio 
> 14.0/VC/redist/x64/Microsoft.VC140.CRT"
>copyFilesToDestdir($$VC_RUNTIME_FOLDER, "msvcp140.dll") }
>
> It's supposed to copy msvcp140.dll to build folder for Release configuration 
> (so it will be included into the installer then).
>
> I do not need this msvcp140.dll to be copied to my Debug folder when I'm 
> working on the project. But it does copy it.
>
> Steps:
> 1) Remove file
> 2) Run qmake on project (active configuration is Debug).
>
> Result: file is copied.
>
> Can anything be done here except the using of QMAKE_POST_LINK here instead? 
> Why is CONFIG(release, debug|release) "not working" here?
>
> Some details below:
>
> copyFilesToDestdir is defined in macros.pri:
>
> defineTest(copyFilesToDestdir) {
>  pathSrc = $$1
>  files = $$2
>  folderDst = $$DESTDIR
>  subfolder = $$3
>  !isEmpty(subfolder) {
>  folderDst=$$folderDst/$$subfolder
>  }
>
>  DEST = $$shell_path($$OUT_PWD/$$folderDst)
>
>  for(filename, files) {
>  FILE = $$shell_path($$pathSrc/$$filename)
>  system($$QMAKE_COPY $$shell_quote($$FILE) $$shell_quote($$DEST))
>  }
> }
>
> ___
> 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 mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Fatal Q_ASSERT in 5.12.0-beta4?

[Olivier B.]

It seems that in commit
https://github.com/qt/qtbase/commit/f4169a633b97b7b6e7365172cf3d38d2f16a8914#diff-0e5a174e7dafaad904b9cb7af5a4c89c
of September 19th, an optimisation disable in VS project generator was
reverted. It initially was put to avoid the assert i get in QString
copy constructor, due to a bug in MSVC2010. Could it be that the bug
is still there in VS2015? I only get the issue with "-tp vc", not when
generating nmake makefiles
Le lun. 12 nov. 2018 à 13:00, Kai Koehne  a écrit :
>
> > -Original Message-
> > From: Interest  On Behalf
> > Of Olivier B.
> > Sent: Monday, November 12, 2018 12:33 PM
> > To: interest@qt-project.org
> > Subject: [Interest] Fatal Q_ASSERT in 5.12.0-beta4?
> >
> > I built 5.12.0-beta4 to prepare for the LTS, but qmake on my project aborts 
> > at
> > the assert in QStirng constructor. Trying to remove code to localize the
> > problerm, i get another assert in qvector.
>
> Please try to create a minimal example for the assert, and post it to 
> bugreports.qt.io. Please also include a stack trace.
>
> > I am running the release qmake, and i never saw them in previous
> > (stable) versions. Are asserts enabled for beta releases or something?
>
> I'm not aware of any extra configuration for beta's that we don't also use in 
> the final versions.
>
> Kai
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Fatal Q_ASSERT in 5.12.0-beta4?

[Olivier B.]

I built 5.12.0-beta4 to prepare for the LTS, but qmake on my project
aborts at the assert in QStirng constructor. Trying to remove code to
localize the problerm, i get another assert in qvector.
I am running the release qmake, and i never saw them in previous
(stable) versions. Are asserts enabled for beta releases or something?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Change of indirection of message pointer in nativeEvent()?

[Olivier B.]

Nevermind, it is https://bugreports.qt.io/browse/QTBUG-69074
Le mer. 24 oct. 2018 à 09:17, Olivier B.
 a écrit :
>
> With Qt 5.6.2, i used nativeEvent() to capture Windows minimize
> command. I casted the void* message into a MSG* and could read it
> properly
>
> Now, with Qt 5.11.1, this did not detect the messages anymore.
> Debugging, i noticed that at the call of
> QWindowSystemInterface::handleNativeEvent() by filterNativeEvent(),
> the MSG* is not casted as void*, but we pass the address of the MSG*
> in the void* argument.
> So now, in nativeEvent(), to properly decode the message, i have to
> cast the void* to LPMSG, then dereference it to get the original MSG*
>
> Was that change intentionnal?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Change of indirection of message pointer in nativeEvent()?

[Olivier B.]

With Qt 5.6.2, i used nativeEvent() to capture Windows minimize
command. I casted the void* message into a MSG* and could read it
properly

Now, with Qt 5.11.1, this did not detect the messages anymore.
Debugging, i noticed that at the call of
QWindowSystemInterface::handleNativeEvent() by filterNativeEvent(),
the MSG* is not casted as void*, but we pass the address of the MSG*
in the void* argument.
So now, in nativeEvent(), to properly decode the message, i have to
cast the void* to LPMSG, then dereference it to get the original MSG*

Was that change intentionnal?
___
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

[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] QMAKE_COPY not used anymore for files in INSTALLS. Workaround?

[Olivier B.]

This does not seem to be the case.
If i try to qinstall an executable that is on a samba share, and
currently locked because the result of make install is being run,
qinstall fails with "Error copying A to B: Destination already exists"
(this error is after the remove() of previous destination file, when
QFile::copy fails).
In the QFileInfo::exists() in QFile::copy(), the path is still marked
as existing, while the app that locks the file is running. But the
QFile::remove() seems to have been 'acknowledged', and as soon as the
app unlocks the file, it disappears, so i end up without the original
nor the new destination file. Hence my need to rename the original
destination file before asking for it's removal



Le mer. 12 sept. 2018 à 18:15, Thiago Macieira
 a écrit :
>
> On Wednesday, 12 September 2018 08:27:04 PDT Olivier B. wrote:
> > - Make a renamed backup of the previous target file if it already exists on
> > the network share, to avoid some issues (allow to overwrite the installed
> > file on the network path, even if some people are currently using that file
> > by running the project where it was installed)
>
> This one shouldn't be needed anymore. The "qinstall" should do this for you by
> writing to a temporary file and then doing an atomic rename to clobber the old
> file.
>
> --
> 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] QMAKE_COPY not used anymore for files in INSTALLS. Workaround?

[Olivier B.]

I do
- Reset windows executable permissions for files with some extensions after
copy (copied on a network share where executable permission is meaningfull
to run the exes), using icacls
- Make a renamed backup of the previous target file if it already exists on
the network share, to avoid some issues (allow to overwrite the installed
file on the network path, even if some people are currently using that file
by running the project where it was installed)

Sidenote, after some search:
Looking at
https://github.com/qt/qtbase/commit/50acc8680490319c8fe45615c8d6521f0101728b#diff-2c05a7d11c42aacde5f92861cc595e07,
i would say the constraint to have only files of only dirs in COPIES in
files_copies.prf can be removed now that the QINSTALL command is the same
for files or folders

Le mer. 12 sept. 2018 à 17:16, Thiago Macieira 
a écrit :

> On Wednesday, 12 September 2018 07:46:59 PDT Olivier B. wrote:
> > Here is another change i noticed when switching from 5.6.2 to 5.11.1
> >
> > I used to tweak QMAKE_COPY and its cousins, to do extra stuff on the
> files
> > installed by INSTALLS variable.
> >
> > Now, files in INSTALLS are installed using 'qmake -install qinstall',
> > stored in QINSTALL variable, written in the makefile directly from a
> > hardocded value in qmake sources.
> >
> > It seems i am able to do something similar that i used to by
> > - adding my install targets in COPIES instead of INSTALLS,
> > - modifying mkspecs/features/file_copies.prf to use my custom copy
> command
> > instead of $(QINSTALL)
> >
> > This has at least the additionnal limitation of forcing me to also split
> > install lists that used to contain files and folder into separate lists
> > because file_copies.prf does not like it for some reason, even though i
> > don't see it doing anything specific for files or folders. Also, i can
> not
> > add to COPIES, when TEMPLATE=subdirs, when i can do it for INSTALLS
> >
> > Is there really not anymore a simple way of specifying a list of files
> and
> > folders to install, using a custom copy command, without modifying qmake
> > internals or reinventing the wheel?
>
> Can you tell us what customisation you needed? There may be a different
> way of
> doing what you want to do.
>
> --
> 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
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] QMAKE_COPY not used anymore for files in INSTALLS. Workaround?

[Olivier B.]

Here is another change i noticed when switching from 5.6.2 to 5.11.1

I used to tweak QMAKE_COPY and its cousins, to do extra stuff on the files
installed by INSTALLS variable.

Now, files in INSTALLS are installed using 'qmake -install qinstall',
stored in QINSTALL variable, written in the makefile directly from a
hardocded value in qmake sources.

It seems i am able to do something similar that i used to by
- adding my install targets in COPIES instead of INSTALLS,
- modifying mkspecs/features/file_copies.prf to use my custom copy command
instead of $(QINSTALL)

This has at least the additionnal limitation of forcing me to also split
install lists that used to contain files and folder into separate lists
because file_copies.prf does not like it for some reason, even though i
don't see it doing anything specific for files or folders. Also, i can not
add to COPIES, when TEMPLATE=subdirs, when i can do it for INSTALLS

Is there really not anymore a simple way of specifying a list of files and
folders to install, using a custom copy command, without modifying qmake
internals or reinventing the wheel?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Issues building Qt 5.11.1 from source

[Olivier B.]

>
> From: Thiago Macieira 
> To: 
> Cc:
> Bcc:
> Date: Tue, 10 Jul 2018 07:29:29 -0700
> Subject: Re: [Interest] Issues building Qt 5.11.1 from source
> On Tuesday, 10 July 2018 06:11:55 PDT Olivier B. wrote:
> >  I am currently trying 5.11.1 from sources. My previous mails seems to
> not
> > have been sent, i had forgotten i had unsubscribed. Here are the issues i
> > encountered so far:
> >
> > - the source archive does not contain .gitmodules at the root. Without
> it,
> > the root configure.bat does not know of the modules, does not load their
> > json files, so does not understand arguments passed to configure.bat.
> > Either the archive or the building articles need to be updated
>
> Cannot confirm. I can see it in both the .tar.xz and .zip files.
>
> > - config.opt can not contain arguments of strings containing spaces in
> > quotes. In my case it was just OPENSSL_DIR that was valued "lib1 lib2
> > lib3", so i could pass it as en enviropnment variable instead, but what
> > about the path arguments that would contain spaces (for -I, -L,
> -prefix;..)?
> > Since there can be only one argument per line in config.opt, in the for
> > loop that reads config.opt of qtbase/configure.bat,  couldn't  the
> (unused)
> > token delimiter be something else than space, like ';' or '%', so that we
> > can pass arguments with spaces in quotes?
>
> Don't fight config.opt. Even if you manage to get it parsed, you're going
> to
> find issues elsewhere. Instead, rename your directory that contains spaces.
>
> > - option -qt-sql-plugin is not understood anymore. initial parsing
> > recognizes it as an unknown boolean option , and not an enum option, as
> > defined in configure.json of sqldrivers. I switched back to
> > -plugin-sqsl-sqlite for now..
>

Regarding the last point. After lots of manual digging, i found that sql
plugins are now always built as plugins, since commit
0452c25aedb7d2778e5b26fad924ed61b72bbe33
in 5.8 alpha.
It looks like doc about those options was removed, but the disappearance
was never put in a release note. There is still at least
qtbase/src/sql/README.module that references those options. Could it be
cleaned?


>
-- 
> 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

[Interest] Issues building Qt 5.11.1 from source

[Olivier B.]

 I am currently trying 5.11.1 from sources. My previous mails seems to not
have been sent, i had forgotten i had unsubscribed. Here are the issues i
encountered so far:

- the source archive does not contain .gitmodules at the root. Without it,
the root configure.bat does not know of the modules, does not load their
json files, so does not understand arguments passed to configure.bat.
Either the archive or the building articles need to be updated

- config.opt can not contain arguments of strings containing spaces in
quotes. In my case it was just OPENSSL_DIR that was valued "lib1 lib2
lib3", so i could pass it as en enviropnment variable instead, but what
about the path arguments that would contain spaces (for -I, -L, -prefix;..)?
Since there can be only one argument per line in config.opt, in the for
loop that reads config.opt of qtbase/configure.bat,  couldn't  the (unused)
token delimiter be something else than space, like ';' or '%', so that we
can pass arguments with spaces in quotes?

- option -qt-sql-plugin is not understood anymore. initial parsing
recognizes it as an unknown boolean option , and not an enum option, as
defined in configure.json of sqldrivers. I switched back to
-plugin-sqsl-sqlite for now..
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Binary compatibility between 5.5 and 5.6

[Olivier B.]

I encountered some issues trying to link a library that uses Qt 5.6
into a program that uses Qt 5.5 on linux (providing the 5.5 libs to
the linker when the lib needs 5.6 :P )

This resulted in lots of undefined reference to someQtSymbol()@Qt_5

Indeed, doing 'objdump -CT' on my 5.5.1 Qt5Core.so gives something like
0032fc00 gDF .text  0018  Base
QLibrary::metaObject() const

And objdump on the 5.6 version gives
00313e80 gDF .text  0018  Qt_5
QLibrary::metaObject() const

Those two were custom built with the same script/tools/machine. So i
am assuming the change in "Base" -> "Qt_5" is induced by a change in
the sources? (i could find no "Qt_5" string in the 5.6 sources package
that could be related to this)

A few questions come to my mind (Obviously i am not asking for a magic
solution to link a lib compiled for 5.6 with 5.5.1, it's more out of
curiosity)

 - Won't that cause binary compatibility issues? Or is the link of
Base -> Qt_5 allowed, just not the opposite? I don't really know much
about that column of objdump

- Why was this introduced in 5.6 and not at the start of Qt5?
Shouldn't it be called QT_5.6 if it prevents link with older Qt5
libraries? Or should it already be present in my Qt5.5 libraries, in
function of some qt configure option that i forgot to add before
build?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Statically linking an open-source application with Qt?

[Olivier B.]

I am not sure you are even able to link all Qt statically. Won't you at
least need platform plugins, image plugins, etc as shared libraries?

Google gives this :
https://wiki.qt.io/Building_a_static_Qt_for_Windows_using_MinGW

2016-07-26 17:15 GMT+02:00 Vik k :

> Hey, I wrote an open source application using Qt and now I want to
> statically link it to the Qt library. My question is, is it legal to do so?
>
> On the website I am going to provide several download links to precompiled
> versions of my app for Windows, Mac and Linux and a link to the GitHub
> repository containing the source code of the application.
>
> My application will have no about section tho (as a matter of fact it does
> not have a menubar at all), is it also okay to write that I used Qt on the
> website & in the GitHub repo?
>
> Thanks,
> Vik.
>
> ___
> 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 Location with Mapbox plugin?

[Olivier B.]

There was a message about it in that same mailing list earlier this morning
from alexander.blas...@qt.io :

Hi,

Qt Location provides three content/map provider plugins (HERE, MapBox and
MapQuest). The first two providers require an account to run and MapQuest
was free of any registration so far. Unfortunately this changed this
Monday. More details in:

https://bugreports.qt.io/browse/QTBUG-54599

As a consequence any QtLocation application that uses MapQuest will no
longer receive any map tiles. The only possible way to fix this today is to
change from MapQuest to HERE or MapBox. Although those providers require a
registration they do offer free of charge usage models. Please be aware of
their terms and conditions though.

We are very sorry for this problem but at the end of the day there is not
much Qt can do. We are working on a patch to change to a new registration
free provider and even a related indirection but at the end of the day,
registration free access is becoming a thing of the past.

Going forward I would suggest to to always consider some form of registered
usage for any map provider. While we will continue to address upcoming
service changes this does ensure that there is some form of business
relationship between you and your chosen map tile provider. At the very
least it means that  notifications can be received before drastic changes
happen.

2016-07-15 14:43 GMT+02:00 Ola Røer Thorsen :

> I'm struggling getting any maps shown using the Qt Location Mapbox plugin.
> I'm getting error messages like "failed to fetch tile, , server
> replied: Forbidden".
>
> The plugin needs a map_id and an access_token.
>
> On the mapbox website it's easy to find the access tokens, but no map
> id's. Maybe they have changed the way this is done? They refer a lot to
> Style URLs instead.
>
> Are any of you out there successfully using Mapbox? How did you configure
> the plugin?
>
> Cheers,
> Ola
>
>
> ___
> 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] QTreeView expand icon changes unexpectedly Qt5.6.0 & VS2015

[Olivier B.]

Are you sure it is not https://bugreports.qt.io/browse/QTBUG-52230 ?

2016-05-28 22:59 GMT+02:00 Ben Swerts :

> Hi Anton,
>
> I noticed the same issue with VS2015 Update 2 and Qt 5.6.0 (commercial).
> Your post made me realize this seems to be related to the combination of
> these two tools.
> Our application is built with VS2013 Update 5 while I'm preparing
> everything
> for an upgrade to VS2015. I'm quite certain this issue is not present when
> compiling with VS2013.
>
> So if no one has logged a bug for this yet, I would advise you to log one.
>
> Regards,
>
>
> Ben
>
> -Original Message-
> From: Interest [mailto:interest-bounces+benswerts=
> telenet...@qt-project.org]
> On Behalf Of anton
> Sent: Friday, 27 May, 2016 23:56
> To: interest@qt-project.org
> Subject: [Interest] QTreeView expand icon changes unexpectedly Qt5.6.0 &
> VS2015
>
> Hi,
>
> I installed the following qt version on my Windows 7 (64bit):
>
>
> http://download.qt.io/official_releases/qt/5.6/5.6.0/qt-opensource-windows-x
> 86-msvc2015_64-5.6.0.exe
>
> I use Visual Studio 2015 update 2.
>
>
> I create a Qt Widget application with q QTreeView and some QComboBox'es.
>
> In my treeview I see the expand iccons:
>
> - they look like a triangle lile '>' when the treenode
>   is *not* expanded
>
> - they look like a triangle lile 'V' when the treenode
>   is not *expanded*
>
> Now I click here and there in my application, clicl on a QComboBox and now
> some strange magic happens.
>
> 1. The expand icons change to a '[+]': a plus in a rectangle
>like you know it from the windows explorer.
>
> 2. As soon as the mouse pointer hoovers over the
>expand icon it becomes *insisible*.
>
> In the Qt Designer in Qt Creator, I see the same problem, the expand icons
> (in the property pane) look like a '[+]' like in the windows explorer, but
> they becone invisible as soon as the mouse pointer is over the expand icon.
>
>
> My questions:
>
> - do you observe the same things?
> - did I forget to initialize something?
>   (don't think so because the Qt Designer has the same problem)
> - or is it a bug which will be fixed in 5.6.1 or 5.7.0 ?
>
>
> Thanks for a hint
>
>   Anton
>
> ___
> 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 mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] PRO File defines

[Olivier B.]

Google 'undocumented qmake', or else, qmake source code ?
Le 24 avr. 2016 23:29, "Gianluca"  a écrit :

> It’s not the first time that I see people knowing some “secrets” of Qmake …
> … where is the full documentation of all these details ?
>
>
> Il giorno 24/apr/2016, alle ore 18:47, Igor Mironchik <
> igor.mironc...@gmail.com> ha scritto:
>
> > Hi,
> >
> > For real device you can use:
> >
> > ios {
> >  iphoneos {
> ># Here is the real device
> >  }
> > }
> >
> > On 24.04.2016 20:45, mark diener wrote:
> >> Hello List:
> >>
> >> Who can tell me how to detect whether a build is for IOS or IOS
> Simulator
> >> in the project PRO file.
> >>
> >> ios {
> >> QMAKE_IOS_DEPLOYMENT_TARGET=8.0
> >> QMAKE_IOS_TARGETED_DEVICE_FAMILY=1,2
> >> }
> >>
> >> But how to I differentiate between IOS builds and IOS-simulator builds?
> >>
> >> Thanks,
> >>
> >> Marco
> >> ___
> >> 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 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 modules dependency tree

[Olivier B.]

Cool thanks :)

2016-03-30 18:28 GMT+02:00 Thiago Macieira <thiago.macie...@intel.com>:

> On quarta-feira, 30 de março de 2016 15:26:50 PDT Olivier B. wrote:
> > Hi,
> > Would there be somewhere online a dependency tree of all qt modules of
> the
> > standard distribution?
>
> It used to be in the qt.pro file of the qt5.git repository. Now it's in
> the
> .gitmodules file itself[1]
>
> $ git config --file=.gitmodules --get-regexp
> 'submodule.*(depends|recommends)'
> submodule.qtsvg.depends qtbase
> submodule.qtdeclarative.depends qtbase
> submodule.qtdeclarative.recommends qtsvg qtxmlpatterns
> submodule.qtactiveqt.depends qtbase
> submodule.qtscript.depends qtbase
> submodule.qtscript.recommends qttools
> submodule.qtmultimedia.depends qtbase
> submodule.qtmultimedia.recommends qtdeclarative
> submodule.qttools.depends qtbase
> submodule.qttools.recommends qtdeclarative qtactiveqt qtwebkit
> submodule.qtxmlpatterns.depends qtbase
> submodule.qttranslations.depends qttools
> submodule.qtdoc.depends qtdeclarative
> submodule.qtwebkit.depends qtbase
> submodule.qtwebkit.recommends qtdeclarative qtlocation qtmultimedia
> qtsensors
> qtwebchannel qtxmlpatterns
> submodule.qtwebkit-examples.depends qtwebkit qttools
> submodule.qtqa.depends qtbase
> submodule.qtlocation.depends qtbase
> submodule.qtlocation.recommends qtdeclarative qtquickcontrols qtserialport
> qtsystems
> submodule.qtsensors.depends qtbase
> submodule.qtsensors.recommends qtdeclarative
> submodule.qtsystems.depends qtbase
> submodule.qtsystems.recommends qtdeclarative
> submodule.qtfeedback.depends qtdeclarative
> submodule.qtfeedback.recommends qtmultimedia
> submodule.qtdocgallery.depends qtdeclarative
> submodule.qtpim.depends qtdeclarative
> submodule.qtconnectivity.depends qtbase
> submodule.qtconnectivity.recommends qtdeclarative qtandroidextras
> submodule.qtwayland.depends qtbase
> submodule.qtwayland.recommends qtdeclarative
> submodule.qt3d.depends qtdeclarative qtimageformats
> submodule.qtimageformats.depends qtbase
> submodule.qtquick1.depends qtscript
> submodule.qtquick1.recommends qtsvg qtxmlpatterns
> submodule.qtgraphicaleffects.depends qtdeclarative
> submodule.qtquickcontrols.depends qtdeclarative
> submodule.qtquickcontrols.recommends qtgraphicaleffects
> submodule.qtserialbus.depends qtserialport
> submodule.qtserialport.depends qtbase
> submodule.qtx11extras.depends qtbase
> submodule.qtmacextras.depends qtbase
> submodule.qtwinextras.depends qtbase
> submodule.qtwinextras.recommends qtdeclarative qtmultimedia
> submodule.qtandroidextras.depends qtbase
> submodule.qtenginio.depends qtdeclarative
> submodule.qtwebsockets.depends qtbase
> submodule.qtwebsockets.recommends qtdeclarative
> submodule.qtwebchannel.depends qtbase
> submodule.qtwebchannel.recommends qtdeclarative qtwebsockets
> submodule.qtwebengine.depends qtquickcontrols qtwebchannel
> submodule.qtwebengine.recommends qtlocation
> submodule.qtcanvas3d.depends qtdeclarative
> submodule.qtwebview.depends qtdeclarative
> submodule.qtwebview.recommends qtwebengine
> submodule.qtquickcontrols2.depends qtquickcontrols
> submodule.qtpurchasing.depends qtbase
> submodule.qtpurchasing.recommends qtdeclarative
>
> [1] http://code.qt.io/cgit/qt/qt5.git/tree/.gitmodules
>
>
> --
> 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
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Conflicting libjpeg versions

[Olivier B.]

In that case it's at your app's link time that you have to make sure you
link to the same libjpeg qt used. If both Qt and your app use a static
libjpeg in the same executable, it must be the same

2016-03-29 17:00 GMT+02:00 Etienne Sandré-Chardonnal <etienne.san...@m4x.org
>:

> I will try recompiling Qt. Is there any way to check the actual files Qt
> is linked against?
>
> I was not clear in my original post. The error message is not triggered
> when I use Qt for reading a jpeg, but when I'm directly using the libjpeg
> API.
>
> Etienne
>
> 2016-03-29 16:55 GMT+02:00 Olivier B. <perso.olivier.barthel...@gmail.com>
> :
>
>> oops, ignore my 2nd sentence, i mixed up png and jpeg
>>
>> 2016-03-29 16:51 GMT+02:00 Olivier B. <perso.olivier.barthel...@gmail.com
>> >:
>>
>>> I do -system-libjpeg -I ${ENV_LIBJPEG_PATH}/include -L
>>> ${ENV_LIBJPEG_PATH}/lib  on my configure line to use my own libjpeg
>>> version.
>>> I also sed in qtbase/src/3rdparty/png_dependency.pri between debug and
>>> release build, in order to use a debug libjpeg in my debug qt and a release
>>> libjpeg in my release qt
>>>
>>> If you build a static Qt, it is written in Qt static libs at qt build
>>> time that they need 62. But actual linking with libjpeg is done at link
>>> time of your exe. So if the path to the wrong libjpeg is passed at
>>> executable llink time, you might get the error you are seing at runtime
>>>
>>> 2016-03-29 16:45 GMT+02:00 Etienne Sandré-Chardonnal <
>>> etienne.san...@m4x.org>:
>>>
>>>> Hi,
>>>>
>>>> There is no dependency to any libjpeg DLL, as checked with dependency
>>>> walker. And I have searched for any libjpeg*.dll in my system, none of them
>>>> are inside the PATH. The libjpeg is linked statically.
>>>>
>>>> Which options do I have for configuring Qt? I only know the option
>>>> which switches between embedded libjpeg and system libjpeg, and using the
>>>> latter should normally make Qt use the 6.2 that is installed in the
>>>> compiler folders (include/lib)
>>>>
>>>>
>>>>
>>>>
>>>> 2016-03-29 16:24 GMT+02:00 Olivier B. <
>>>> perso.olivier.barthel...@gmail.com>:
>>>>
>>>>> Either your PATH is set so the wrong libjpeg dll is found first, or qt
>>>>> found the wrong jpeg include first.
>>>>> If you don't care which version is used, set your PATH so that your
>>>>> system libjpeg 6.2 is found first at runtime (or place the libjpeg dll of
>>>>> the version that was detected beside your executable). If you want a
>>>>> specific version, change qt configure options accordingly
>>>>>
>>>>> 2016-03-29 16:18 GMT+02:00 Etienne Sandré-Chardonnal <
>>>>> etienne.san...@m4x.org>:
>>>>>
>>>>>> Dear all,
>>>>>>
>>>>>> I am compiling under windows with MinGW (64-bit)
>>>>>>
>>>>>> I compiled Qt for static linking. I let the default options for
>>>>>> configure regarding jpeg support, and it seems that it choose using the
>>>>>> system libjpeg (as seen in config.summary), probably because it detected
>>>>>> it. My system libjpeg is the binary shipped by libjpeg-turbo 1.4.2 
>>>>>> official
>>>>>> download, installed inside minGW folders. The libjpeg version as in
>>>>>> jconfig.h is 62 (6.2)
>>>>>>
>>>>>> Now when I compile and run my application, libjpeg functions return
>>>>>> the following error message : Wrong JPEG library version: library is
>>>>>> 80, caller expects 62
>>>>>>
>>>>>> So it means that at some point my application was linked (statically
>>>>>> or dynamically) with libjpeg version 80 (8.0)
>>>>>>
>>>>>> If I remove the libjpeg.a from my compiler path, I cannot compile my
>>>>>> application anymore. So it is properly linking against that file, or I am
>>>>>> missing something.
>>>>>>
>>>>>> What could be the issue?
>>>>>>
>>>>>> Thanks...
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> 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 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] Conflicting libjpeg versions

[Olivier B.]

oops, ignore my 2nd sentence, i mixed up png and jpeg

2016-03-29 16:51 GMT+02:00 Olivier B. <perso.olivier.barthel...@gmail.com>:

> I do -system-libjpeg -I ${ENV_LIBJPEG_PATH}/include -L
> ${ENV_LIBJPEG_PATH}/lib  on my configure line to use my own libjpeg
> version.
> I also sed in qtbase/src/3rdparty/png_dependency.pri between debug and
> release build, in order to use a debug libjpeg in my debug qt and a release
> libjpeg in my release qt
>
> If you build a static Qt, it is written in Qt static libs at qt build time
> that they need 62. But actual linking with libjpeg is done at link time of
> your exe. So if the path to the wrong libjpeg is passed at executable llink
> time, you might get the error you are seing at runtime
>
> 2016-03-29 16:45 GMT+02:00 Etienne Sandré-Chardonnal <
> etienne.san...@m4x.org>:
>
>> Hi,
>>
>> There is no dependency to any libjpeg DLL, as checked with dependency
>> walker. And I have searched for any libjpeg*.dll in my system, none of them
>> are inside the PATH. The libjpeg is linked statically.
>>
>> Which options do I have for configuring Qt? I only know the option which
>> switches between embedded libjpeg and system libjpeg, and using the latter
>> should normally make Qt use the 6.2 that is installed in the compiler
>> folders (include/lib)
>>
>>
>>
>>
>> 2016-03-29 16:24 GMT+02:00 Olivier B. <perso.olivier.barthel...@gmail.com
>> >:
>>
>>> Either your PATH is set so the wrong libjpeg dll is found first, or qt
>>> found the wrong jpeg include first.
>>> If you don't care which version is used, set your PATH so that your
>>> system libjpeg 6.2 is found first at runtime (or place the libjpeg dll of
>>> the version that was detected beside your executable). If you want a
>>> specific version, change qt configure options accordingly
>>>
>>> 2016-03-29 16:18 GMT+02:00 Etienne Sandré-Chardonnal <
>>> etienne.san...@m4x.org>:
>>>
>>>> Dear all,
>>>>
>>>> I am compiling under windows with MinGW (64-bit)
>>>>
>>>> I compiled Qt for static linking. I let the default options for
>>>> configure regarding jpeg support, and it seems that it choose using the
>>>> system libjpeg (as seen in config.summary), probably because it detected
>>>> it. My system libjpeg is the binary shipped by libjpeg-turbo 1.4.2 official
>>>> download, installed inside minGW folders. The libjpeg version as in
>>>> jconfig.h is 62 (6.2)
>>>>
>>>> Now when I compile and run my application, libjpeg functions return the
>>>> following error message : Wrong JPEG library version: library is 80,
>>>> caller expects 62
>>>>
>>>> So it means that at some point my application was linked (statically or
>>>> dynamically) with libjpeg version 80 (8.0)
>>>>
>>>> If I remove the libjpeg.a from my compiler path, I cannot compile my
>>>> application anymore. So it is properly linking against that file, or I am
>>>> missing something.
>>>>
>>>> What could be the issue?
>>>>
>>>> Thanks...
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ___
>>>> 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 mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Conflicting libjpeg versions

[Olivier B.]

I do -system-libjpeg -I ${ENV_LIBJPEG_PATH}/include -L
${ENV_LIBJPEG_PATH}/lib  on my configure line to use my own libjpeg
version.
I also sed in qtbase/src/3rdparty/png_dependency.pri between debug and
release build, in order to use a debug libjpeg in my debug qt and a release
libjpeg in my release qt

If you build a static Qt, it is written in Qt static libs at qt build time
that they need 62. But actual linking with libjpeg is done at link time of
your exe. So if the path to the wrong libjpeg is passed at executable llink
time, you might get the error you are seing at runtime

2016-03-29 16:45 GMT+02:00 Etienne Sandré-Chardonnal <etienne.san...@m4x.org
>:

> Hi,
>
> There is no dependency to any libjpeg DLL, as checked with dependency
> walker. And I have searched for any libjpeg*.dll in my system, none of them
> are inside the PATH. The libjpeg is linked statically.
>
> Which options do I have for configuring Qt? I only know the option which
> switches between embedded libjpeg and system libjpeg, and using the latter
> should normally make Qt use the 6.2 that is installed in the compiler
> folders (include/lib)
>
>
>
>
> 2016-03-29 16:24 GMT+02:00 Olivier B. <perso.olivier.barthel...@gmail.com>
> :
>
>> Either your PATH is set so the wrong libjpeg dll is found first, or qt
>> found the wrong jpeg include first.
>> If you don't care which version is used, set your PATH so that your
>> system libjpeg 6.2 is found first at runtime (or place the libjpeg dll of
>> the version that was detected beside your executable). If you want a
>> specific version, change qt configure options accordingly
>>
>> 2016-03-29 16:18 GMT+02:00 Etienne Sandré-Chardonnal <
>> etienne.san...@m4x.org>:
>>
>>> Dear all,
>>>
>>> I am compiling under windows with MinGW (64-bit)
>>>
>>> I compiled Qt for static linking. I let the default options for
>>> configure regarding jpeg support, and it seems that it choose using the
>>> system libjpeg (as seen in config.summary), probably because it detected
>>> it. My system libjpeg is the binary shipped by libjpeg-turbo 1.4.2 official
>>> download, installed inside minGW folders. The libjpeg version as in
>>> jconfig.h is 62 (6.2)
>>>
>>> Now when I compile and run my application, libjpeg functions return the
>>> following error message : Wrong JPEG library version: library is 80,
>>> caller expects 62
>>>
>>> So it means that at some point my application was linked (statically or
>>> dynamically) with libjpeg version 80 (8.0)
>>>
>>> If I remove the libjpeg.a from my compiler path, I cannot compile my
>>> application anymore. So it is properly linking against that file, or I am
>>> missing something.
>>>
>>> What could be the issue?
>>>
>>> Thanks...
>>>
>>>
>>>
>>>
>>>
>>>
>>> ___
>>> 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 mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Conflicting libjpeg versions

[Olivier B.]

Either your PATH is set so the wrong libjpeg dll is found first, or qt
found the wrong jpeg include first.
If you don't care which version is used, set your PATH so that your system
libjpeg 6.2 is found first at runtime (or place the libjpeg dll of the
version that was detected beside your executable). If you want a specific
version, change qt configure options accordingly

2016-03-29 16:18 GMT+02:00 Etienne Sandré-Chardonnal :

> Dear all,
>
> I am compiling under windows with MinGW (64-bit)
>
> I compiled Qt for static linking. I let the default options for configure
> regarding jpeg support, and it seems that it choose using the system
> libjpeg (as seen in config.summary), probably because it detected it. My
> system libjpeg is the binary shipped by libjpeg-turbo 1.4.2 official
> download, installed inside minGW folders. The libjpeg version as in
> jconfig.h is 62 (6.2)
>
> Now when I compile and run my application, libjpeg functions return the
> following error message : Wrong JPEG library version: library is 80,
> caller expects 62
>
> So it means that at some point my application was linked (statically or
> dynamically) with libjpeg version 80 (8.0)
>
> If I remove the libjpeg.a from my compiler path, I cannot compile my
> application anymore. So it is properly linking against that file, or I am
> missing something.
>
> What could be the issue?
>
> Thanks...
>
>
>
>
>
>
> ___
> 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