Re: [Interest] Static build of Qt - debug mode and plugins
On Friday, 30 August 2019 11:27:00 PDT Jakub Narolewski wrote: > As for compression performance, zstd is still not as fast as lz4's > LZ4_compress_fast - at least not in my use case. Indeed. Your data shows you're compressing less than 1.5k of data, which incidentally fits into a single TCP or UDP frame. So the gain in compression at level 0 (234 bytes versus 520) is not worth the time it takes, since it won't be transmitted faster. Zstd's big avantage is the search algorithm. Since your data is so small, it's no surprise it's no better than LZ4. That result is the opposite of what I found when replacing Icecream's compression: the data transferred is in the order of megabytes, so the network time is the biggest contributor. But thanks for the info, it's good to know. PS: Have you tried LZO? That's what Icecream used before I changed. -- 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
Re: [Interest] Static build of Qt - debug mode and plugins
On Friday, 30 August 2019 11:44:43 PDT Konstantin Tokarev wrote: > > As for compression performance, zstd is still not as fast as lz4's > > LZ4_compress_fast - at least not in my use case. > And not only yours - even benchmark results in zstd repository [1] > demonstrate clearly that lz4 is substantially faster than zstd in both > compression and decompression. > > [1] https://github.com/facebook/zstd I guess I mis-remembered my own benchmarks then. -- 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
Re: [Interest] Static build of Qt - debug mode and plugins
30.08.2019, 21:29, "Jakub Narolewski" : > Thank you Thiago for your suggestion :] > > I'm currently not able to use zstandard because I need it to work on my > client side - WebGL targeted Unity Engine builds. > > We had some problems getting it to work using different approaches. > > As for compression performance, zstd is still not as fast as lz4's > LZ4_compress_fast - at least not in my use case. And not only yours - even benchmark results in zstd repository [1] demonstrate clearly that lz4 is substantially faster than zstd in both compression and decompression. [1] https://github.com/facebook/zstd -- Regards, Konstantin ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Static build of Qt - debug mode and plugins
Thank you Thiago for your suggestion :] I'm currently not able to use zstandard because I need it to work on my client side - WebGL targeted Unity Engine builds. We had some problems getting it to work using different approaches. As for compression performance, zstd is still not as fast as lz4's LZ4_compress_fast - at least not in my use case. I have generated some quick'n'very'dirty benchmarks if you want to take look at them: https://docs.google.com/spreadsheets/d/1akfTIbOjRladXbnZx1K8GyekKL5tCBAiBTS6jQ1v0OQ/edit?ouid=116212118529929666006=sheets_home=true The suspiciously similar payload sizes in case of zstd were due to clients inability to properly send their data back to the server - they did not change their positions on 2d plane that much. I can make zstd to 'run' as fast as lz4 if I pass '-100' as a compression level but resulting package size is bigger than lz4's. Dictionary mode is not helping much probably because I'm compressing flatbuffers structures containing only fast-changing numerical data - not much correlation in those. My project is targeting low grade VPS'es, akin to DigitalOcean's Droplets, so in a long run even small CPU time differences makes a difference to me. Jakub Narolewski From: Thiago Macieira Sent: 26 August 2019 07:40 To: interest@qt-project.org Subject: Re: [Interest] Static build of Qt - debug mode and plugins On Sunday, 25 August 2019 08:59:23 PDT Jakub Narolewski wrote: > # small hack to properly set LZ4 library between build modes Suggestion: if you are not required to use LZ4 because of a file format, you should switch to Zstandard. It compresses better *and* faster than LZ4. It requires more RAM to run, but if you're loading QtCore, QtNetwork and QtSql, memory usage is not your limitation. -- 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
Re: [Interest] Static build of Qt - debug mode and plugins
Correct! Somewhat. I’m using VS under Windows configured to use ‘Unix Makefiles’ as generator when I’m connected to remote Linux boxes. Under Windows I use Ninja. Narolewski Jakub From: Elvis Stansvik Sent: 26 August 2019 18:54 To: Matthew Woehlke Cc: interest@qt-project.org Interest; Jakub Narolewski Subject: Re: Static build of Qt - debug mode and plugins Den mån 26 aug. 2019 kl 18:49 skrev Matthew Woehlke : > > On 26/08/2019 12.18, Elvis Stansvik wrote: > > Den mån 26 aug. 2019 17:32Matthew Woehlke skrev: > >> ...or just run `make VERBOSE=1`. > > > > I didn't know if he was using ninja or make, so suggested the solution that > > I believe will work with both (with recent versions of CMake) :) > > Fair point. I'm pretty sure the `[1%] ...` is not Ninja (Ninja would > normally be e.g. `[1/52] ...`), but it might have been Visual Studio. Ah yes, well spotted. It wasn't VS since it's Linux. So your Make assumption was probably correct. > > For some reason I took one look and immediately believed it to be > `make`, but now I think that was my bad :-). (Possibly related to how > often I use Windows these days... hardly ever. Also, when I do have to > use Windows, I still use Ninja ;-).) Amen. Elvis > > -- > Matthew ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Static build of Qt - debug mode and plugins
Den mån 26 aug. 2019 kl 18:49 skrev Matthew Woehlke : > > On 26/08/2019 12.18, Elvis Stansvik wrote: > > Den mån 26 aug. 2019 17:32Matthew Woehlke skrev: > >> ...or just run `make VERBOSE=1`. > > > > I didn't know if he was using ninja or make, so suggested the solution that > > I believe will work with both (with recent versions of CMake) :) > > Fair point. I'm pretty sure the `[1%] ...` is not Ninja (Ninja would > normally be e.g. `[1/52] ...`), but it might have been Visual Studio. Ah yes, well spotted. It wasn't VS since it's Linux. So your Make assumption was probably correct. > > For some reason I took one look and immediately believed it to be > `make`, but now I think that was my bad :-). (Possibly related to how > often I use Windows these days... hardly ever. Also, when I do have to > use Windows, I still use Ninja ;-).) Amen. Elvis > > -- > Matthew ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Static build of Qt - debug mode and plugins
On 26/08/2019 12.18, Elvis Stansvik wrote: > Den mån 26 aug. 2019 17:32Matthew Woehlke skrev: >> ...or just run `make VERBOSE=1`. > > I didn't know if he was using ninja or make, so suggested the solution that > I believe will work with both (with recent versions of CMake) :) Fair point. I'm pretty sure the `[1%] ...` is not Ninja (Ninja would normally be e.g. `[1/52] ...`), but it might have been Visual Studio. For some reason I took one look and immediately believed it to be `make`, but now I think that was my bad :-). (Possibly related to how often I use Windows these days... hardly ever. Also, when I do have to use Windows, I still use Ninja ;-).) -- Matthew ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Static build of Qt - debug mode and plugins
Den mån 26 aug. 2019 17:32Matthew Woehlke skrev: > On 25/08/2019 03.09, Elvis Stansvik wrote: > > Den sön 25 aug. 2019 kl 02:56 skrev Thiago Macieira: > >> On Saturday, 24 August 2019 10:53:45 PDT Jakub Narolewski wrote: > >>> [ 1%] Linking CXX executable mrserver_debug > >> > >> Please expand this line. > > > > Jakub, to do this you can pass -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE to > CMake. > > ...or just run `make VERBOSE=1`. > > Or, better yet, install Ninja and use `-G Ninja` when running CMake ;-). > (And then `ninja -v`.) Your build times will thank you. > I didn't know if he was using ninja or make, so suggested the solution that I believe will work with both (with recent versions of CMake) :) (I could have dreamed up that it also works with ninja though.. It may have just been a suggestion.) Elvis > -- > Matthew > ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Static build of Qt - debug mode and plugins
Although all these examples look nice the CMAKE_VERBOSE_MAKEFILE is good enough for me as I currently develop my software remotely using VS Studio and it's remote CMake integration. I just modify CMakeSettings.json and there comes more stuff to read :) On Mon, 26 Aug 2019, 17:32 Matthew Woehlke, wrote: > On 25/08/2019 03.09, Elvis Stansvik wrote: > > Den sön 25 aug. 2019 kl 02:56 skrev Thiago Macieira: > >> On Saturday, 24 August 2019 10:53:45 PDT Jakub Narolewski wrote: > >>> [ 1%] Linking CXX executable mrserver_debug > >> > >> Please expand this line. > > > > Jakub, to do this you can pass -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE to > CMake. > > ...or just run `make VERBOSE=1`. > > Or, better yet, install Ninja and use `-G Ninja` when running CMake ;-). > (And then `ninja -v`.) Your build times will thank you. > > -- > Matthew > ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Static build of Qt - debug mode and plugins
On 25/08/2019 03.09, Elvis Stansvik wrote: > Den sön 25 aug. 2019 kl 02:56 skrev Thiago Macieira: >> On Saturday, 24 August 2019 10:53:45 PDT Jakub Narolewski wrote: >>> [ 1%] Linking CXX executable mrserver_debug >> >> Please expand this line. > > Jakub, to do this you can pass -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE to CMake. ...or just run `make VERBOSE=1`. Or, better yet, install Ninja and use `-G Ninja` when running CMake ;-). (And then `ninja -v`.) Your build times will thank you. -- Matthew ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Static build of Qt - debug mode and plugins
Thanks again for starting it : ) > On 26. Aug 2019, at 16:01, Kyle Edwards wrote: > > On Sun, 2019-08-25 at 18:07 +, Alexandru Croitor wrote: >> Note that Qt 5.14 will come with support for importing static plugins >> from CMake, and you won't have to bother with the dependency order >> anymore. > > Thanks again for finishing that off for me! > > Kyle ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Static build of Qt - debug mode and plugins
On Sun, 2019-08-25 at 18:07 +, Alexandru Croitor wrote: > Note that Qt 5.14 will come with support for importing static plugins > from CMake, and you won't have to bother with the dependency order > anymore. Thanks again for finishing that off for me! Kyle ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Static build of Qt - debug mode and plugins
On 8/26/19 5:00 AM, Thiago Macieira wrote: It's also interesting that QtCore and QtNetwork are listed three times. Multiple inclusions has been happening for a long time. I butted heads with that when creating that "Explore this computer" app which had to install on Ubuntu 12, 13, 14, and 15 both 32-bit and 64-bit for single executable. Fun times there. Static build wasn't an option either thanks to the Qt Web stuff. -- Roland Hughes, President Logikal Solutions (630)-205-1593 (cell) http://www.theminimumyouneedtoknow.com http://www.infiniteexposure.net http://www.johnsmith-book.com ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Static build of Qt - debug mode and plugins
On Sunday, 25 August 2019 08:59:23 PDT Jakub Narolewski wrote: > # small hack to properly set LZ4 library between build modes Suggestion: if you are not required to use LZ4 because of a file format, you should switch to Zstandard. It compresses better *and* faster than LZ4. It requires more RAM to run, but if you're loading QtCore, QtNetwork and QtSql, memory usage is not your limitation. -- 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
Re: [Interest] Static build of Qt - debug mode and plugins
It's present in the 5.14 branch. Docs: https://doc-snapshots.qt.io/qt5-dev/qtcore-cmake-qt5-import-plugins.html ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Static build of Qt - debug mode and plugins
Sound really awesome – the less steps the better. Does this feature already exist on the dev branch of qt? Can check it out by compiling Qt directly from git? Narolewski Jakub From: Alexandru Croitor Sent: 25 August 2019 20:07 To: Jakub Narolewski; Thiago Macieira; interest@qt-project.org Subject: Re: [Interest] Static build of Qt - debug mode and plugins Note that Qt 5.14 will come with support for importing static plugins from CMake, and you won't have to bother with the dependency order anymore. ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Static build of Qt - debug mode and plugins
Note that Qt 5.14 will come with support for importing static plugins from CMake, and you won't have to bother with the dependency order anymore. ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Static build of Qt - debug mode and plugins
Ah yes, mystery solved. As usual – the butler did it. I suppose I should read
my own code more carefully.
In case of Release builds I’m adding “-flto” switch to the resulting object
using this line of code:
if (NOT CMAKE_BUILD_TYPE STREQUAL "Debug")
if (WIN32)
SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /Ox /fp:fast")
endif (WIN32)
if (LINUX)
SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -flto
-funroll-all-loops -pthread")
endif (LINUX)
if (APPLE)
SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -flto")
endif (APPLE)
endif (NOT CMAKE_BUILD_TYPE STREQUAL "Debug")
When I also force it to exist in Debug builds the order of
target_link_libraries function does not matter anymore and application builds
just fine.
Sorry for the noise.
Thanks again for your help :]
Narolewski Jakub
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Re: [Interest] Static build of Qt - debug mode and plugins
Yea, it builds fine when I reorder them in my CMakeLists.
My ‘invalid’ CMakeLists part dealing with external libraries looks like this:
# global target link libraries
target_link_libraries(${TARGET_FULL_NAME}
PRIVATE
Qt5::Core
Qt5::Sql
Qt5::Network
Qt5::Concurrent
Qt5::WebSockets
${BOX2D_LIBRARY}
${LZ4_LIBRARY}
)
# on unix-based systems we use static qt build - add some stuff to target link
libraries
if (LINUX)
target_link_libraries(${TARGET_FULL_NAME}
PRIVATE
Qt5::QPSQLDriverPlugin
Qt5::QSQLiteDriverPlugin
"libpq.so"
)
endif()
# small hack to properly set LZ4 library between build modes
if (CMAKE_BUILD_TYPE STREQUAL "Debug")
(${TARGET_FULL_NAME} PRIVATE ${LZ4_LIBRARY_DEBUG})
else ()
target_link_libraries(${TARGET_FULL_NAME} PRIVATE
${LZ4_LIBRARY_RELEASE})
endif (CMAKE_BUILD_TYPE STREQUAL "Debug")
I don’t use any more target_link_libraries functions in there so I don’t know
from where this extra libQt5Network come from.
Do you have any idea why it actually builds this way under Release mode?
>From what I see, order of the libraries are the same between Release and Debug
>and only Debug generates those errors.
// RELEASE
/usr/local/Qt-5.13.0/lib/libQt5Core.a
/usr/local/Qt-5.13.0/lib/libQt5Sql.a
/usr/local/Qt-5.13.0/lib/libQt5Network.a
/usr/local/Qt-5.13.0/lib/libQt5Concurrent.a
/usr/local/Qt-5.13.0/lib/libQt5WebSockets.a
/home/izowiuz/vcpkg/installed/x64-linux/lib/libBox2D.a
/usr/local/Qt-5.13.0/plugins/sqldrivers/libqsqlpsql.a
/usr/local/Qt-5.13.0/plugins/sqldrivers/libqsqlite.a
-lpq
/home/izowiuz/vcpkg/installed/x64-linux/lib/liblz4.a
/usr/local/Qt-5.13.0/lib/libQt5Network.a
/usr/local/Qt-5.13.0/lib/libQt5Core.a -lpthread
/usr/local/Qt-5.13.0/lib/libQt5Network.a
/usr/local/Qt-5.13.0/lib/libQt5Core.a -lm
/usr/local/Qt-5.13.0/lib/libqtpcre2.a -ldl -lssl -lcrypto
// DEBUG
/usr/local/Qt-5.13.0/lib/libQt5Core.a
/usr/local/Qt-5.13.0/lib/libQt5Sql.a
/usr/local/Qt-5.13.0/lib/libQt5Network.a
/usr/local/Qt-5.13.0/lib/libQt5Concurrent.a
/usr/local/Qt-5.13.0/lib/libQt5WebSockets.a
/home/izowiuz/vcpkg/installed/x64-linux/debug/lib/libBox2D.a
/usr/local/Qt-5.13.0/plugins/sqldrivers/libqsqlpsql.a
/usr/local/Qt-5.13.0/plugins/sqldrivers/libqsqlite.a
-lpq
/home/izowiuz/vcpkg/installed/x64-linux/debug/lib/liblz4d.a
/usr/local/Qt-5.13.0/lib/libQt5Network.a
/usr/local/Qt-5.13.0/lib/libQt5Core.a -lpthread
/usr/local/Qt-5.13.0/lib/libQt5Network.a
/usr/local/Qt-5.13.0/lib/libQt5Core.a -lm
/usr/local/Qt-5.13.0/lib/libqtpcre2.a -ldl -lssl -lcrypto
Narolewski Jakub
From: Thiago Macieira
Sent: 25 August 2019 17:46
To: interest@qt-project.org
Subject: Re: [Interest] Static build of Qt - debug mode and plugins
On Sunday, 25 August 2019 00:25:50 PDT Jakub Narolewski wrote:
> /usr/local/Qt-5.13.0/lib/libQt5Core.a
> /usr/local/Qt-5.13.0/lib/libQt5Sql.a
> /usr/local/Qt-5.13.0/lib/libQt5Network.a
> /usr/local/Qt-5.13.0/lib/libQt5Concurrent.a
> /usr/local/Qt-5.13.0/lib/libQt5WebSockets.a
> /home/izowiuz/vcpkg/installed/x64-linux/lib/libBox2D.a
> /usr/local/Qt-5.13.0/plugins/sqldrivers/libqsqlpsql.a
> /usr/local/Qt-5.13.0/plugins/sqldrivers/libqsqlite.a
> -lpq
> /home/izowiuz/vcpkg/installed/x64-linux/lib/liblz4.a
> /usr/local/Qt-5.13.0/lib/libQt5Network.a
> /usr/local/Qt-5.13.0/lib/libQt5Core.a -lpthread
> /usr/local/Qt-5.13.0/lib/libQt5Network.a
> /usr/local/Qt-5.13.0/lib/libQt5Core.a -lm
> /usr/local/Qt-5.13.0/lib/libqtpcre2.a -ldl -lssl -lcrypto
The order is wrong, as you can see. libQt5Sql.a appears before the plugins.
Invert the order and make the plugins appear before the library in this link
line.
It's interesting that the order is mostly correct. It seems that CMake is
applying dependency sorting correctly. If that is the case, then either it's a
CMake bug or there's some information missing in the qmake-generated CMake
files. Reporting a bug here is unlikely to get you enough attention, so you
may want to get your hands dirty and debug yourself.
It's also interesting that QtCore and QtNetwork are listed three times.
--
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
Re: [Interest] Static build of Qt - debug mode and plugins
On Sunday, 25 August 2019 00:25:50 PDT Jakub Narolewski wrote: > /usr/local/Qt-5.13.0/lib/libQt5Core.a > /usr/local/Qt-5.13.0/lib/libQt5Sql.a > /usr/local/Qt-5.13.0/lib/libQt5Network.a > /usr/local/Qt-5.13.0/lib/libQt5Concurrent.a > /usr/local/Qt-5.13.0/lib/libQt5WebSockets.a > /home/izowiuz/vcpkg/installed/x64-linux/lib/libBox2D.a > /usr/local/Qt-5.13.0/plugins/sqldrivers/libqsqlpsql.a > /usr/local/Qt-5.13.0/plugins/sqldrivers/libqsqlite.a > -lpq > /home/izowiuz/vcpkg/installed/x64-linux/lib/liblz4.a > /usr/local/Qt-5.13.0/lib/libQt5Network.a > /usr/local/Qt-5.13.0/lib/libQt5Core.a -lpthread > /usr/local/Qt-5.13.0/lib/libQt5Network.a > /usr/local/Qt-5.13.0/lib/libQt5Core.a -lm > /usr/local/Qt-5.13.0/lib/libqtpcre2.a -ldl -lssl -lcrypto The order is wrong, as you can see. libQt5Sql.a appears before the plugins. Invert the order and make the plugins appear before the library in this link line. It's interesting that the order is mostly correct. It seems that CMake is applying dependency sorting correctly. If that is the case, then either it's a CMake bug or there's some information missing in the qmake-generated CMake files. Reporting a bug here is unlikely to get you enough attention, so you may want to get your hands dirty and debug yourself. It's also interesting that QtCore and QtNetwork are listed three times. -- 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
Re: [Interest] Static build of Qt - debug mode and plugins
/ItemBox.cpp.o CMakeFiles/mrserver_debug.dir/src/World/Objects/Entity.cpp.o CMakeFiles/mrserver_debug.dir/src/World/Modes/TeamGameMode.cpp.o CMakeFiles/mrserver_debug.dir/src/World/Modes/Stats/DeathMatchStats.cpp.o CMakeFiles/mrserver_debug.dir/src/World/ContactListener.cpp.o CMakeFiles/mrserver_debug.dir/src/Server/Events/EventSignaler.cpp.o CMakeFiles/mrserver_debug.dir/src/Server/Events/ClientEvent.cpp.o CMakeFiles/mrserver_debug.dir/src/Utilities/b2Separator.cpp.o CMakeFiles/mrserver_debug.dir/src/Server/SlaveServer.cpp.o CMakeFiles/mrserver_debug.dir/src/World/Objects/Car.cpp.o CMakeFiles/mrserver_debug.dir/src/Server/AccountManager.cpp.o CMakeFiles/mrserver_debug.dir/src/Server/Server.cpp.o CMakeFiles/mrserver_debug.dir/src/World/Modes/Stats/GameModeStats.cpp.o CMakeFiles/mrserver_debug.dir/src/World/Objects/Drone.cpp.o CMakeFiles/mrserver_debug.dir/src/World/Road/RoadController.cpp.o CMakeFiles/mrserver_debug.dir/src/World/Road/RoadTraveler.cpp.o CMakeFiles/mrserver_debug.dir/src/Server/LoadoutManager.cpp.o CMakeFiles/mrserver_debug.dir/src/World/Weapons/ZigZagProjectile.cpp.o CMakeFiles/mrserver_debug.dir/src/World/Weapons/BounceProjectile.cpp.o CMakeFiles/mrserver_debug.dir/src/World/Objects/HealthPack.cpp.o CMakeFiles/mrserver_debug.dir/src/Server/TcpServer.cpp.o CMakeFiles/mrserver_debug.dir/src/DataContainers/moc_GameData.cpp.o CMakeFiles/mrserver_debug.dir/src/Server/moc_AccountManager.cpp.o CMakeFiles/mrserver_debug.dir/src/Server/Database/moc_SqlGameDataLoader.cpp.o CMakeFiles/mrserver_debug.dir/src/Server/Events/moc_EventSignaler.cpp.o CMakeFiles/mrserver_debug.dir/src/Server/moc_Room.cpp.o CMakeFiles/mrserver_debug.dir/src/Server/moc_TcpServer.cpp.o CMakeFiles/mrserver_debug.dir/src/Server/moc_Server.cpp.o CMakeFiles/mrserver_debug.dir/src/Server/moc_LoadoutManager.cpp.o CMakeFiles/mrserver_debug.dir/src/Server/moc_StatsManager.cpp.o CMakeFiles/mrserver_debug.dir/src/Server/moc_StatsManagerWorker.cpp.o CMakeFiles/mrserver_debug.dir/src/World/Modes/moc_GameMode.cpp.o CMakeFiles/mrserver_debug.dir/src/World/moc_World.cpp.o -o mrserver_debug /usr/local/Qt-5.13.0/lib/libQt5Core.a /usr/local/Qt-5.13.0/lib/libQt5Sql.a /usr/local/Qt-5.13.0/lib/libQt5Network.a /usr/local/Qt-5.13.0/lib/libQt5Concurrent.a /usr/local/Qt-5.13.0/lib/libQt5WebSockets.a /home/izowiuz/vcpkg/installed/x64-linux/debug/lib/libBox2D.a /usr/local/Qt-5.13.0/plugins/sqldrivers/libqsqlpsql.a /usr/local/Qt-5.13.0/plugins/sqldrivers/libqsqlite.a -lpq /home/izowiuz/vcpkg/installed/x64-linux/debug/lib/liblz4d.a /usr/local/Qt-5.13.0/lib/libQt5Network.a /usr/local/Qt-5.13.0/lib/libQt5Core.a -lpthread /usr/local/Qt-5.13.0/lib/libQt5Network.a /usr/local/Qt-5.13.0/lib/libQt5Core.a -lm /usr/local/Qt-5.13.0/lib/libqtpcre2.a -ldl -lssl -lcrypto In both cases I see that /usr/local/Qt-5.13.0/lib/libQt5Sql.a is listed before SQL plugins: libqsqlite.a and libqsqlpsql.a Nevertheless, when I changed the order of plugins and Qt's Sql component application started building properly in Debug mode. Thank you! Narolewski Jakub From: Elvis Stansvik Sent: 25 August 2019 09:09 To: Thiago Macieira Cc: interest@qt-project.org Interest Subject: Re: [Interest] Static build of Qt - debug mode and plugins Den sön 25 aug. 2019 kl 02:56 skrev Thiago Macieira : > > On Saturday, 24 August 2019 10:53:45 PDT Jakub Narolewski wrote: > > [ 1%] Linking CXX executable mrserver_debug > > Please expand this line. Jakub, to do this you can pass -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE to CMake. Elvis > Since this is a static build, the order in which the > libraries is listed matters. > > Make sure that you list the plugin before the QtSql library. > > -- > 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 mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Static build of Qt - debug mode and plugins
Den sön 25 aug. 2019 kl 02:56 skrev Thiago Macieira : > > On Saturday, 24 August 2019 10:53:45 PDT Jakub Narolewski wrote: > > [ 1%] Linking CXX executable mrserver_debug > > Please expand this line. Jakub, to do this you can pass -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE to CMake. Elvis > Since this is a static build, the order in which the > libraries is listed matters. > > Make sure that you list the plugin before the QtSql library. > > -- > 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
Re: [Interest] Static build of Qt - debug mode and plugins
On Saturday, 24 August 2019 10:53:45 PDT Jakub Narolewski wrote: > [ 1%] Linking CXX executable mrserver_debug Please expand this line. Since this is a static build, the order in which the libraries is listed matters. Make sure that you list the plugin before the QtSql library. -- 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
