On Mon, Jan 9, 2023 at 7:10 PM Thiago Macieira
wrote:
The reason is what I stated: the qt-everywhere package is not as
> well-tested
> as the individual modules that compose it. The modules are tested on a
> daily
> basis by the CI. The everywhere package is not.
>
Yes, I understand what you ar
On Monday, 9 January 2023 12:36:33 PST Stefan Seefeld wrote:
> We are actually using the commercial license. I downloaded the source
> package and am trying to build (and package) it internally so we can
> include it in various environments (docker images, say).
> I'm just following the official do
We are actually using the commercial license. I downloaded the source
package and am trying to build (and package) it internally so we can
include it in various environments (docker images, say).
I'm just following the official docs, and had no reason to not use the
`qt-eveywhere-src` source packag
On Monday, 9 January 2023 09:14:16 CST Stefan Seefeld wrote:
> lrelease error: cannot create
> '/home/user/srcdir/qt-build/build/qtbase/share/qt5/translations/qtwebsockets
> _en.qm': No such file or directory
> make[2]: ***
> [qttranslations/translations/CMakeFiles/updateqm-qtwebsockets_en.ts.dir/b
Hi Axel,
I don't think I'll need web sockets (for now). Still, I tried configuring
with and without "-skip qtwebsockets", and both variants failed the same
way.
In fact, the configure step (even with using "-skip qtwebsockets" !) yields
-- Could NOT find Qt6WebSockets (missing: Qt6WebSockets_DIR
Hi Stefan,
is the intention to build with or without web sockets?
It looks like a dependency to websockets causes CMake to search for it.
Could you share the configure output?
Brgds
Axel
Von: Stefan Seefeld
Gesendet: Montag, 9. Januar 2023 16:14
An: Axel Spoerl
Cc
Marten,
Thiago,
I was able to successfully configure for openssl-linked. Below is the configure
line:
C:\Qt\6.4.1\src\build>..\configure.bat -prefix C:\Qt\6.4.1\msvc2019_static
-static -debug-and-release -nomake examples -nomake tests -nomake benchmarks
-nomake manual-tests -nomake minimal-sta
Thanks.
Meanwhile, I'm trying to compile on Ubuntu 20.04 (note that all of this is
done in docker containers).
I'm still observing the same issue, even after a fresh start with an
entirely new build tree:
Updating
'/home/user/srcdir/qt-build/build/qtbase/share/qt5/translations/qtwebsockets_en.qm
We're testing Ubuntu 22.04 at present.
Can't confirm a date though.
Von: Stefan Seefeld
Gesendet: Montag, 9. Januar 2023 15:32
An: Axel Spoerl
Cc: interest@qt-project.org
Betreff: Re: [Interest] Could NOT find Qt6WebSockets trying to compile Qt 6.2.6
(Ubuntu 22.
Thanks. Is there a plan for any other LTS release that will work with
Ubuntu 22.04 ?
On Mon, Jan 9, 2023 at 9:29 AM Axel Spoerl via Interest <
interest@qt-project.org> wrote:
> Hi Stefan,
> pls note that Ubuntu 20.04 is supported on 6.2. Ubuntu 22.04 is known to
> have issues.
> However, if compi
Hi Stefan,
pls note that Ubuntu 20.04 is supported on 6.2. Ubuntu 22.04 is known to have
issues.
However, if compiling w/o websockets is the goal, wiping the build tree and
deleting websockets from the source tree is likely to help.
Sorry for accidently squashing both issues together.
Cheers
Axel
[sorry, forgot to reply to the list]
Thanks for following up. This issue is different from the previous
one, and downgrading cmake to 3.24.x doesn't make any difference. I
still do get the warning from the `configure` process, and the build
error during `make` execution.
Thanks,
On Mon, Jan 9, 2
As Thiago mentioned, dynamically linking OpenSSL tends to be easier.
From what I can tell, the vcpkg directory should work with the
FindOpenssl.cmake module.
You also may have trouble if you are mixing dynamically- and statically linked
libraries!
Since they are likely linking the VC runtime in
13 matches
Mail list logo
