Ambiguity in documentation description and reality of problems in practice
-
@RazerMind
I can only say that maybe it used to work fine for 32-bit, but now perhaps chromium itself doesn't support that any longer, as it gets bigger/more hungry. [Update: Searching the web indicates to me that 32-bit chromium should still be supported (still requires a 64-bit machine to build it). Whether there is an issue with Qt-supplied stuff, or with just the cross-compilation, I do not know.]Remember I am not saying that I know it should not work. Only that "less attention" is paid to 32-bit nowadays, and increasingly so. There is a huge amount to do for TQtC for each new release, and e.g. testing cross-compilation to 32-bit under Windows for the (already problematic) QtWebEngine module may not be high on their list. You might still raise a bug there to ask whether it is supposed to work if you really need it.
@JonB said in Ambiguity in documentation description and reality of problems in practice:
There is a huge amount to do for TQtC for each new release, and e.g. testing cross-compilation to 32-bit under Windows for the (already problematic) QtWebEngine module may not be high on their list. You might still raise a bug there to ask whether it is supposed to work if you really need it.
Oh yes... I looked in their bug-tracking system for the number of tickets and after I created my own - I don’t even think that the queue for answers will reach me. Such a number of them - I'm just horrified that such a project has so few people at work? That mistakes grow like a snowball and are not corrected ...
-
@JonB said in Ambiguity in documentation description and reality of problems in practice:
There is a huge amount to do for TQtC for each new release, and e.g. testing cross-compilation to 32-bit under Windows for the (already problematic) QtWebEngine module may not be high on their list. You might still raise a bug there to ask whether it is supposed to work if you really need it.
Oh yes... I looked in their bug-tracking system for the number of tickets and after I created my own - I don’t even think that the queue for answers will reach me. Such a number of them - I'm just horrified that such a project has so few people at work? That mistakes grow like a snowball and are not corrected ...
@RazerMind
If you created a bug report there please post a hyperlink here to your issue.They are usually pretty good at looking at all reports and assigning them, even if you might not like the answer they come up with :)
Qt is a big system, so it is expected that there will be lots of bugs reports etc.! I cannot comment on how many people TQtC might or might not employ. Some issues are addressed by open source developers who contribute for free, including several members of this forum.
-
To be fair, using "vcvarsall.bat amd64_x86" is working just fine, and using it is not exactly secret knowledge either (see e.g. https://learn.microsoft.com/en-us/cpp/build/building-on-the-command-line?view=msvc-170) . It also has the benefit of being stable between Visual Studio versions, which is not necessarily true for the start menu shortcuts :)
@kkoehne said in Ambiguity in documentation description and reality of problems in practice:
To be fair, using "vcvarsall.bat amd64_x86" is working just fine
And I didn’t say that it doesn’t work - I clarified that for people who typically work under Windows - there is no habit of using command lines (even if they are developers;) - graphic elements save the brain and hands), and when you/I/they will start checking - and WHAT exactly is indicated in the documentation - and compared with what exactly is indicated in the ready-to-use shortcut - then only questions arise. Yes, this is in fact the same (like your URL is saying) BUT agree that there would be no questions at all - if in Docs we could see a picture! YES - each version of the studio would have its own picture with its 2010/2017/2019/2022 ... versions, but the path was and is and will always be the same ;). And it's easy to find. And what if the developers of the studio suddenly change these constants? Agree that they, in turn, will appeal to the fact that they released the studio installer and it created all the proper shortcuts in the start menu needed to work - so be so kind and please use them ;)
By the way, I seem to have found another bug of compilation.
.\qtbase\src\plugins\sqldrivers\oci\qsql_oci.cpp line 144
your latest sources have:
const QString timeZone = dt.toString("ttt");
but it must be:
const QString timeZone = dt.toString(QStringLiteral("ttt"));
because ctor of QString class which takes const char* declared as private!
private:
#if defined(QT_NO_CAST_FROM_ASCII)
QString &operator+=(const char *s);
QString &operator+=(const QByteArray &s);
QString(const char *ch);
QString(const QByteArray &a);
QString &operator=(const char *ch);
QString &operator=(const QByteArray &a);
#endif -
@kkoehne said in Ambiguity in documentation description and reality of problems in practice:
To be fair, using "vcvarsall.bat amd64_x86" is working just fine
And I didn’t say that it doesn’t work - I clarified that for people who typically work under Windows - there is no habit of using command lines (even if they are developers;) - graphic elements save the brain and hands), and when you/I/they will start checking - and WHAT exactly is indicated in the documentation - and compared with what exactly is indicated in the ready-to-use shortcut - then only questions arise. Yes, this is in fact the same (like your URL is saying) BUT agree that there would be no questions at all - if in Docs we could see a picture! YES - each version of the studio would have its own picture with its 2010/2017/2019/2022 ... versions, but the path was and is and will always be the same ;). And it's easy to find. And what if the developers of the studio suddenly change these constants? Agree that they, in turn, will appeal to the fact that they released the studio installer and it created all the proper shortcuts in the start menu needed to work - so be so kind and please use them ;)
By the way, I seem to have found another bug of compilation.
.\qtbase\src\plugins\sqldrivers\oci\qsql_oci.cpp line 144
your latest sources have:
const QString timeZone = dt.toString("ttt");
but it must be:
const QString timeZone = dt.toString(QStringLiteral("ttt"));
because ctor of QString class which takes const char* declared as private!
private:
#if defined(QT_NO_CAST_FROM_ASCII)
QString &operator+=(const char *s);
QString &operator+=(const QByteArray &s);
QString(const char *ch);
QString(const QByteArray &a);
QString &operator=(const char *ch);
QString &operator=(const QByteArray &a);
#endif@RazerMind
dt.toString("ttt");should work 100% fine, you should not need to writeconst QString timeZone = dt.toString(QStringLiteral("ttt"));unless you wish to. I think it will match one of https://doc.qt.io/qt-6/qdatetime.html#toString-2 or https://doc.qt.io/qt-6/qdatetime.html#toString at Qt6 (I don't have Qt6); it certainly works in my Qt5.15.3. Show a compilation error message if you claim it generates one, together with the exact version of Qt you are using. -
@RazerMind
If you created a bug report there please post a hyperlink here to your issue.They are usually pretty good at looking at all reports and assigning them, even if you might not like the answer they come up with :)
Qt is a big system, so it is expected that there will be lots of bugs reports etc.! I cannot comment on how many people TQtC might or might not employ. Some issues are addressed by open source developers who contribute for free, including several members of this forum.
@JonB said in Ambiguity in documentation description and reality of problems in practice:
if you created a bug report there please post a hyperlink here to your issue.
yep, of course
https://bugreports.qt.io/browse/QTBUG-113035Also, I can't leave comments quickly. I'm just a beginner))) - says the engine of this forum...
And I would like to give answers as soon as possible))) while there is a "connection" between all of us))) -
@RazerMind
dt.toString("ttt");should work 100% fine, you should not need to writeconst QString timeZone = dt.toString(QStringLiteral("ttt"));unless you wish to. I think it will match one of https://doc.qt.io/qt-6/qdatetime.html#toString-2 or https://doc.qt.io/qt-6/qdatetime.html#toString at Qt6 (I don't have Qt6); it certainly works in my Qt5.15.3. Show a compilation error message if you claim it generates one, together with the exact version of Qt you are using.@JonB said in Ambiguity in documentation description and reality of problems in practice:
Show a compilation error message if you claim it generates one.
I can't)) coz I already fix this issue by the provided code.
But I'm surprised you think this code should compile.
I gave you both important pieces of code from the sources, which show that the error will be 100%
("ttt") - This piece of code requires the creation of a temporary QString object. To do this, select one of the existing ctor's is necessarily.
And I gave the code where it is shown - that there is such a QString constructor.
But here's the problem - it is declared in the private part of the class!P.S. why tmp object? because we talk about this declaration:
QString QDateTime::toString(const QString &format, QCalendar cal = QCalendar()) const
but in code developers put not QString object but an object represented by a const string literal "ttt". -
@JonB said in Ambiguity in documentation description and reality of problems in practice:
Show a compilation error message if you claim it generates one.
I can't)) coz I already fix this issue by the provided code.
But I'm surprised you think this code should compile.
I gave you both important pieces of code from the sources, which show that the error will be 100%
("ttt") - This piece of code requires the creation of a temporary QString object. To do this, select one of the existing ctor's is necessarily.
And I gave the code where it is shown - that there is such a QString constructor.
But here's the problem - it is declared in the private part of the class!P.S. why tmp object? because we talk about this declaration:
QString QDateTime::toString(const QString &format, QCalendar cal = QCalendar()) const
but in code developers put not QString object but an object represented by a const string literal "ttt".@RazerMind
Instead of telling me what information you gave me that I should be able to work with. Given that I told youdt.toString("ttt");works fine for me, at least with my Qt, why don't you spend the 10 seconds to write this line for yourself, compile it, and show the compilation error you say it produces? And I don't know whether you compile with or withoutQT_NO_CAST_FROM_ASCIIif that is relevant. Up to you, I don't need to spend my time looking at this. -
@JonB said in Ambiguity in documentation description and reality of problems in practice:
if you created a bug report there please post a hyperlink here to your issue.
yep, of course
https://bugreports.qt.io/browse/QTBUG-113035Also, I can't leave comments quickly. I'm just a beginner))) - says the engine of this forum...
And I would like to give answers as soon as possible))) while there is a "connection" between all of us)))@RazerMind Alright, commented on the bug report - though you might not like the result, as @JonB already suspected ;) But given that x86 is not supported in Qt 6, we will not spend much time on this.
-
@RazerMind
Instead of telling me what information you gave me that I should be able to work with. Given that I told youdt.toString("ttt");works fine for me, at least with my Qt, why don't you spend the 10 seconds to write this line for yourself, compile it, and show the compilation error you say it produces? And I don't know whether you compile with or withoutQT_NO_CAST_FROM_ASCIIif that is relevant. Up to you, I don't need to spend my time looking at this.@JonB said in Ambiguity in documentation description and reality of problems in practice:
why don't you spend the 10 seconds to write this line for yourself, compile it, and show the compilation error you say it produces?
First of all it's a problem of Qt 6.5.0 LTS sources compilation - and not my own code ;)
Secondly here we go:FAILED: qtbase/src/plugins/sqldrivers/oci/CMakeFiles/QOCIDriverPlugin.dir/Debug/qsql_oci.cpp.obj
"I:\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\bin\Hostx64\x86\cl.exe" /nologo /TP -DQOCIDriverPlugin_EXPORTS -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_UP_TO=0x040800 -DQT_EXPLICIT_QFILE_CONSTRUCTION_FROM_PATH -DQT_LEAN_HEADERS=1 -DQT_NO_AS_CONST=1 -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_EXCEPTIONS -DQT_NO_JAVA_STYLE_ITERATORS -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_PLUGIN -DQT_SQL_LIB -DQT_WARN_DEPRECATED_UP_TO=0x070000 -DUNICODE -DWIN32 -D_CRT_SECURE_NO_WARNINGS -D_ENABLE_EXTENDED_ALIGNED_STORAGE -D_UNICODE -DCMAKE_INTDIR="Debug" -ID:_\6.5.0-source\Build\qtbase\src\plugins\sqldrivers\oci\QOCIDriverPlugin_autogen\include_Debug -ID:_\6.5.0-source\qtbase\src\plugins\sqldrivers\oci -ID:_\6.5.0-source\Build\qtbase\src\plugins\sqldrivers\oci -ID:_\6.5.0-source\Build\qtbase\include -ID:_\6.5.0-source\Build\qtbase\include\QtCore -ID:_\6.5.0-source\qtbase\mkspecs\win32-msvc -ID:_\6.5.0-source\Build\qtbase\src\corelib -ID:_\6.5.0-source\Build\qtbase\include\QtCore\6.5.0 -ID:_\6.5.0-source\Build\qtbase\include\QtCore\6.5.0\QtCore -ID:_\6.5.0-source\Build\qtbase\src\sql -ID:_\6.5.0-source\Build\qtbase\include\QtSql\6.5.0 -ID:_\6.5.0-source\Build\qtbase\include\QtSql\6.5.0\QtSql -ID:_\6.5.0-source\Build\qtbase\include\QtSql -external:IC:\oracle\sdk21\include -external:W0 /DWIN32 /D_WINDOWS /Zi /RTC1 -MDd /W3 /EHs-c- /wd4530 /wd4577 -Zc:__cplusplus -permissive- -utf-8 -FS -Zc:rvalueCast -Zc:inline -Zc:strictStrings -Zc:throwingNew -Zc:referenceBinding -Zc:ternary -Zc:externConstexpr -Zc:wchar_t -bigobj -std:c++20 /Foqtbase\src\plugins\sqldrivers\oci\CMakeFiles\QOCIDriverPlugin.dir\Debug\qsql_oci.cpp.obj /Fdqtbase\src\plugins\sqldrivers\oci\CMakeFiles\QOCIDriverPlugin.dir\Debug\ /FS -c D:_\6.5.0-source\qtbase\src\plugins\sqldrivers\oci\qsql_oci.cpp
D:_\6.5.0-source\qtbase\src\plugins\sqldrivers\oci\qsql_oci.cpp(144): error C2248: QString::QString: cannot access private member declared in class "QString"
D:_\6.5.0-source\Build\qtbase\include\QtCore../../../../qtbase/src/corelib/text/qstring.h(1154): note: see declaration of "QString::QString"
D:_\6.5.0-source\Build\qtbase\include\QtSql../../../../qtbase/src/sql/kernel/qsqlresult.h(17): note: see declaration of "QString"
FAILED: qtwebengine/src/core/Debug/AMD64/QtWebEngineCore.stamp qtwebengine/src/core/Debug/AMD64/QtWebEngineCore D://6.5.0-source/Build/qtwebengine/src/core/Debug/AMD64/QtWebEngineCore.stamp D://6.5.0-source/Build/qtwebengine/src/core/Debug/AMD64/QtWebEngineCore
cmd.exe /C "cd /D D:_\6.5.0-source\Build\qtwebengine\src\core && "I:\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja\ninja.exe" -C D:/_/6.5.0-source/Build/qtwebengine/src/core/Debug/AMD64 QtWebEngineCore"
ninja: build stopped: subcommand failed. -
@JonB said in Ambiguity in documentation description and reality of problems in practice:
why don't you spend the 10 seconds to write this line for yourself, compile it, and show the compilation error you say it produces?
First of all it's a problem of Qt 6.5.0 LTS sources compilation - and not my own code ;)
Secondly here we go:FAILED: qtbase/src/plugins/sqldrivers/oci/CMakeFiles/QOCIDriverPlugin.dir/Debug/qsql_oci.cpp.obj
"I:\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\bin\Hostx64\x86\cl.exe" /nologo /TP -DQOCIDriverPlugin_EXPORTS -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_UP_TO=0x040800 -DQT_EXPLICIT_QFILE_CONSTRUCTION_FROM_PATH -DQT_LEAN_HEADERS=1 -DQT_NO_AS_CONST=1 -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_EXCEPTIONS -DQT_NO_JAVA_STYLE_ITERATORS -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_PLUGIN -DQT_SQL_LIB -DQT_WARN_DEPRECATED_UP_TO=0x070000 -DUNICODE -DWIN32 -D_CRT_SECURE_NO_WARNINGS -D_ENABLE_EXTENDED_ALIGNED_STORAGE -D_UNICODE -DCMAKE_INTDIR="Debug" -ID:_\6.5.0-source\Build\qtbase\src\plugins\sqldrivers\oci\QOCIDriverPlugin_autogen\include_Debug -ID:_\6.5.0-source\qtbase\src\plugins\sqldrivers\oci -ID:_\6.5.0-source\Build\qtbase\src\plugins\sqldrivers\oci -ID:_\6.5.0-source\Build\qtbase\include -ID:_\6.5.0-source\Build\qtbase\include\QtCore -ID:_\6.5.0-source\qtbase\mkspecs\win32-msvc -ID:_\6.5.0-source\Build\qtbase\src\corelib -ID:_\6.5.0-source\Build\qtbase\include\QtCore\6.5.0 -ID:_\6.5.0-source\Build\qtbase\include\QtCore\6.5.0\QtCore -ID:_\6.5.0-source\Build\qtbase\src\sql -ID:_\6.5.0-source\Build\qtbase\include\QtSql\6.5.0 -ID:_\6.5.0-source\Build\qtbase\include\QtSql\6.5.0\QtSql -ID:_\6.5.0-source\Build\qtbase\include\QtSql -external:IC:\oracle\sdk21\include -external:W0 /DWIN32 /D_WINDOWS /Zi /RTC1 -MDd /W3 /EHs-c- /wd4530 /wd4577 -Zc:__cplusplus -permissive- -utf-8 -FS -Zc:rvalueCast -Zc:inline -Zc:strictStrings -Zc:throwingNew -Zc:referenceBinding -Zc:ternary -Zc:externConstexpr -Zc:wchar_t -bigobj -std:c++20 /Foqtbase\src\plugins\sqldrivers\oci\CMakeFiles\QOCIDriverPlugin.dir\Debug\qsql_oci.cpp.obj /Fdqtbase\src\plugins\sqldrivers\oci\CMakeFiles\QOCIDriverPlugin.dir\Debug\ /FS -c D:_\6.5.0-source\qtbase\src\plugins\sqldrivers\oci\qsql_oci.cpp
D:_\6.5.0-source\qtbase\src\plugins\sqldrivers\oci\qsql_oci.cpp(144): error C2248: QString::QString: cannot access private member declared in class "QString"
D:_\6.5.0-source\Build\qtbase\include\QtCore../../../../qtbase/src/corelib/text/qstring.h(1154): note: see declaration of "QString::QString"
D:_\6.5.0-source\Build\qtbase\include\QtSql../../../../qtbase/src/sql/kernel/qsqlresult.h(17): note: see declaration of "QString"
FAILED: qtwebengine/src/core/Debug/AMD64/QtWebEngineCore.stamp qtwebengine/src/core/Debug/AMD64/QtWebEngineCore D://6.5.0-source/Build/qtwebengine/src/core/Debug/AMD64/QtWebEngineCore.stamp D://6.5.0-source/Build/qtwebengine/src/core/Debug/AMD64/QtWebEngineCore
cmd.exe /C "cd /D D:_\6.5.0-source\Build\qtwebengine\src\core && "I:\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja\ninja.exe" -C D:/_/6.5.0-source/Build/qtwebengine/src/core/Debug/AMD64 QtWebEngineCore"
ninja: build stopped: subcommand failed.The OCI build failure is fixed in https://codereview.qt-project.org/c/qt/qtbase/+/466234 , and should be fixed in Qt 6.5.1.
-
@JonB said in Ambiguity in documentation description and reality of problems in practice:
why don't you spend the 10 seconds to write this line for yourself, compile it, and show the compilation error you say it produces?
First of all it's a problem of Qt 6.5.0 LTS sources compilation - and not my own code ;)
Secondly here we go:FAILED: qtbase/src/plugins/sqldrivers/oci/CMakeFiles/QOCIDriverPlugin.dir/Debug/qsql_oci.cpp.obj
"I:\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\bin\Hostx64\x86\cl.exe" /nologo /TP -DQOCIDriverPlugin_EXPORTS -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_UP_TO=0x040800 -DQT_EXPLICIT_QFILE_CONSTRUCTION_FROM_PATH -DQT_LEAN_HEADERS=1 -DQT_NO_AS_CONST=1 -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_EXCEPTIONS -DQT_NO_JAVA_STYLE_ITERATORS -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_PLUGIN -DQT_SQL_LIB -DQT_WARN_DEPRECATED_UP_TO=0x070000 -DUNICODE -DWIN32 -D_CRT_SECURE_NO_WARNINGS -D_ENABLE_EXTENDED_ALIGNED_STORAGE -D_UNICODE -DCMAKE_INTDIR="Debug" -ID:_\6.5.0-source\Build\qtbase\src\plugins\sqldrivers\oci\QOCIDriverPlugin_autogen\include_Debug -ID:_\6.5.0-source\qtbase\src\plugins\sqldrivers\oci -ID:_\6.5.0-source\Build\qtbase\src\plugins\sqldrivers\oci -ID:_\6.5.0-source\Build\qtbase\include -ID:_\6.5.0-source\Build\qtbase\include\QtCore -ID:_\6.5.0-source\qtbase\mkspecs\win32-msvc -ID:_\6.5.0-source\Build\qtbase\src\corelib -ID:_\6.5.0-source\Build\qtbase\include\QtCore\6.5.0 -ID:_\6.5.0-source\Build\qtbase\include\QtCore\6.5.0\QtCore -ID:_\6.5.0-source\Build\qtbase\src\sql -ID:_\6.5.0-source\Build\qtbase\include\QtSql\6.5.0 -ID:_\6.5.0-source\Build\qtbase\include\QtSql\6.5.0\QtSql -ID:_\6.5.0-source\Build\qtbase\include\QtSql -external:IC:\oracle\sdk21\include -external:W0 /DWIN32 /D_WINDOWS /Zi /RTC1 -MDd /W3 /EHs-c- /wd4530 /wd4577 -Zc:__cplusplus -permissive- -utf-8 -FS -Zc:rvalueCast -Zc:inline -Zc:strictStrings -Zc:throwingNew -Zc:referenceBinding -Zc:ternary -Zc:externConstexpr -Zc:wchar_t -bigobj -std:c++20 /Foqtbase\src\plugins\sqldrivers\oci\CMakeFiles\QOCIDriverPlugin.dir\Debug\qsql_oci.cpp.obj /Fdqtbase\src\plugins\sqldrivers\oci\CMakeFiles\QOCIDriverPlugin.dir\Debug\ /FS -c D:_\6.5.0-source\qtbase\src\plugins\sqldrivers\oci\qsql_oci.cpp
D:_\6.5.0-source\qtbase\src\plugins\sqldrivers\oci\qsql_oci.cpp(144): error C2248: QString::QString: cannot access private member declared in class "QString"
D:_\6.5.0-source\Build\qtbase\include\QtCore../../../../qtbase/src/corelib/text/qstring.h(1154): note: see declaration of "QString::QString"
D:_\6.5.0-source\Build\qtbase\include\QtSql../../../../qtbase/src/sql/kernel/qsqlresult.h(17): note: see declaration of "QString"
FAILED: qtwebengine/src/core/Debug/AMD64/QtWebEngineCore.stamp qtwebengine/src/core/Debug/AMD64/QtWebEngineCore D://6.5.0-source/Build/qtwebengine/src/core/Debug/AMD64/QtWebEngineCore.stamp D://6.5.0-source/Build/qtwebengine/src/core/Debug/AMD64/QtWebEngineCore
cmd.exe /C "cd /D D:_\6.5.0-source\Build\qtwebengine\src\core && "I:\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja\ninja.exe" -C D:/_/6.5.0-source/Build/qtwebengine/src/core/Debug/AMD64 QtWebEngineCore"
ninja: build stopped: subcommand failed.@RazerMind
It would be really interesting for you to test:QDateTime dt; qDebug() << dt.toString("ttt");in your own code compiled with your Qt 6.5.
I see @kkoehne has answered that this is a known, fixed bug. I see it is due to
SQL/OCI: Compile with QT_NO_CAST_FROM_ASCII. -
The OCI build failure is fixed in https://codereview.qt-project.org/c/qt/qtbase/+/466234 , and should be fixed in Qt 6.5.1.
@kkoehne said in Ambiguity in documentation description and reality of problems in practice:
The OCI build failure is fixed in https://codereview.qt-project.org/c/qt/qtbase/+/466234 , and should be fixed in Qt 6.5.1.
Huge thx!
And I also hope that the cross-compilation process will finally be explained - OR it's possible - OR it's NOT possible in today's realities.
-
@kkoehne said in Ambiguity in documentation description and reality of problems in practice:
The OCI build failure is fixed in https://codereview.qt-project.org/c/qt/qtbase/+/466234 , and should be fixed in Qt 6.5.1.
Huge thx!
And I also hope that the cross-compilation process will finally be explained - OR it's possible - OR it's NOT possible in today's realities.
@RazerMind
As you can see, TQtC peeps do look at bug reports pretty promptly :) -
@RazerMind
As you can see, TQtC peeps do look at bug reports pretty promptly :)@JonB
lucky we)))but not enough/////
Coz I still have enough problems. I should have had working support for compiling QPDF* classes. But because it was built into the QWebEngine module, which now only supports x64, so now I've failed... completely...
Main problem of this topic is revealed, but mine problems are still with me... -
R RazerMind has marked this topic as solved on
