On Tuesday, 8 October 2019 09:26:19 PDT Roland Hughes wrote:
> > That DOES work with keys produced by OpenSSL that was affected by the
> > Debian bug you described. That's because the bug caused the problem space
> > to be extremely restricted. You said 32768 (2^15) possibilities.
>
> Unless the k
On Tuesday, 8 October 2019 14:09:18 PDT Ola Røer Thorsen wrote:
> Hi all, I've got a thread in an application (Linux, Qt 5.13.0) which just
> writes udp datagrams at a relatively high frequency (video streaming).
> Sometimes the QUdpSocket::writeDatagram function returns -1 and the socket
> error i
On Tuesday, 8 October 2019 14:16:28 PDT Simon Matthews wrote:
> I am trying to build Qt 5.13.1 on CentOS6.
Upgrade.
> I have the related xcb packages installed:
[...]
> Package libxcb-devel-1.12-4.el6.x86_64 already installed and latest version
> Package xcb-util-0.4.0-2.2.el6.x86_64 already inst
“In the latter case, the rational is (I guess) to prevent a company, say, to
work with 20 developers for 3 years on an OSS Qt license, then switch to
commercial when it's time to ship the product and the team is reduced to a core
maintenance crew. That late switch is unfair to companies that are
I am trying to build Qt 5.13.1 on CentOS6. I have run into an error that
others have reported, but the reported solutions don't seem to work.
I am using devtoolset-8, which brings in gcc version 8.3.1
The error is:
ERROR: Feature 'xcb' was enabled, but the pre-condition 'features.thread
&& featu
Hi all, I've got a thread in an application (Linux, Qt 5.13.0) which just
writes udp datagrams at a relatively high frequency (video streaming).
Sometimes the QUdpSocket::writeDatagram function returns -1 and the socket
error is "TemporaryError". Looking into the source code of the udp socket
class
It would maybe be useful to clarify what his mistake is ?
>From what I understand Uwe mixes "contributing to open source project" and
"using open source Qt for a closed project". In the former case, of course
he's welcome to buy commercial licences for whatever project he'll be
working on. In the l
On 10/8/19 5:00 AM, Thiago Macieira wrote:
On Monday, 7 October 2019 18:08:27 PDT Roland Hughes wrote:
There was a time when a Gig of storage would occupy multiple floors of
the Sears Tower and the paper weight was unreal.
Have you ever heard of Claude Shannon?
Nope.
Anyway, you can't get mo
This part is still true:
> I'm stuck in XCode hell. I upgraded XCode because I needed to work with a
> iPhone 11 (iOS 13), which required me to install XCode 11, which created
> issues. I started a new project and got:
> 11:27:26: Starting: "/usr/bin/make" clean -j4
> 'import sitecustomize' fail
On 10/8/19 5:00 AM, Thiago Macieira wrote:
On Monday, 7 October 2019 15:43:21 PDT Roland Hughes wrote:
No. This technique is cracking without cracking. You are looking for a
fingerprint. That fingerprint is the opening string for an xml document
which must be there per the standard. For JSON it
I'm stuck in XCode hell. I upgraded XCode because I needed to work with a
iPhone 11 (iOS 13), which required me to install XCode 11, which created
issues. I started a new project and got:
11:27:26: Starting: "/usr/bin/make" clean -j4
'import sitecustomize' failed; use -v for traceback
Traceback
Am Tue, 8 Oct 2019 10:16:45 +0300
schrieb Vyacheslav Lanovets :
> 2 persons use *Mac* to make the app work on iOS (static linking!).
what about going lgpl and delivering object files to enable relinking
statically with another qt version?
--
/*
* Your lucky number has been disconnected.
*/
Hi Vyacheslav,
Where are you located? It is probably easiest that our regional sales team or
local reseller is in contact to discuss.
Commercial Qt licensing is developer based, so each person working on the same
project (e.g. same end user application) needs to have a commercial license.
One
> I hope to hear expert opinions on the following.
>
> Let's say the company has 10 developers who develop a Mobile app for
> consumer phones.
>
> 2 persons use *Mac* to make the app work on iOS (static linking!).
> Another 2 persons work from PCs on supporting Android specifics
> (shared linking).
Uwe,
You are completely mistaken! I'm more than happy to discuss this with you. My
phone number is listed below. In the meantime please view https://www.qt.io/faq/
2.13. If I have started development of a project using the open source version
(LGPL), can I later purchase a commercial version o
Il 08/10/19 10:24, Yves Maurischat ha scritto:
I dont think that you'll get a definitive answer from this list as
The other side of the coin: this list is NOT for sales or detailed
licensing questions. It's about technical questions related to the usage
of Qt (and, specifically, the parts of
Let me answer that shortly with the gist of severeal other threads on
this list: "It depends. Please contact the sales representatives of The
Qt Company."
I dont think that you'll get a definitive answer from this list as
licensing seems to depend on your project, the mood of the sales rep,
w
On 10/8/19 1:21 AM, Melinda Seifert wrote:
You can use commercial if you previously used Open Source but it’s on
a case by case basis and you need to get approval from the Qt
company.
Like you need to get approval from the Qt company when not having been
Open Source before - it is the basic r
18 matches
Mail list logo
