Hi Thiago,
The example in question is Scene Graph
Best,
Nuno
[cmake] Running C:\Qt\Tools\CMake_64\bin\cmake.exe -S
C:/Qt/Examples/Qt-6.6.1/quick/scenegraph/graph -B
C:/Qt/Examples/Qt-6.6.1/quick/scenegraph/build-graph-Desktop_Qt_6_6_3_MSVC2019_64bit_static-Debug
in
C:\Qt\Examples\Qt-6.6.1\q
On Wednesday 26 June 2024 08:17:51 GMT-7 Alexandru Croitor via Interest wrote:
> Regarding compiling a project from the examples, the build system does not
> 'remember' which openssl was used when building qt, so you have to set the
> OPENSSL_ROOT_DIR variable also when configuring the project, eit
You could try using --debug-find as described on
https://wiki.qt.io/Qt_Build_System_Glossary#CMake_find_package_troubleshooting
to see which paths cmake is considering when trying to find the openssl
package, perhaps that reveals some new info why it is not found.
I would also check what's the
Alexander,
Thanks for your reply.
In the meantime I have realised that the OPENSSL_ROOT_DIR was actually wrong
due to unzipping a folder that created another folder with the same name inside
of it.
However I have deleted the cmake cache file and the problem remains. I have
even used the comma
Hi,
You're telling the build system to link openssl, but openssl was likely not
found.
Perhaps you have it installed in a different path on the new machine, and the
value you pass to OPENSSL_ROOT_DIR is incorrect.
> On 26. Jun 2024, at 15:23, Nuno Santos via Interest
> wrote:
>
> Hi,
>
> I
Hi,
I’ve been building Qt 6.X.Y successfully from the source on Windows with the
following configuration command:
configure.bat -prefix C:\Qt\6.6.3\msvc2019_static -static -static-runtime
-debug-and-release -nomake examples -nomake tests -nomake benchmarks -nomake
manual-tests -nomake minimal-
