On 6/10/21 06:13, Thiago Macieira wrote:
On Tuesday, 5 October 2021 11:45:23 PDT Christophe Thomas wrote:
For the cert chain we are currently using the default LE setting so we
currently provide the X1 Cross signed with expired X3.
Netherless, the issue is that strangely we need to force caCert
On Tuesday, 5 October 2021 12:28:17 PDT Christophe Thomas wrote:
> one trick is that we had to provide the openssl lib with our soft in order
> to work on some of our users setup. So we might relly in our app on a
> different openssl version than the one installed, making the test with
> openssl bi
I can't reproduce the issue, only maitai (and some users) does, we'll check
the status of his ca cert.
one trick is that we had to provide the openssl lib with our soft in order
to work on some of our users setup. So we might relly in our app on a
different openssl version than the one installed,
On Tuesday, 5 October 2021 11:45:23 PDT Christophe Thomas wrote:
> For the cert chain we are currently using the default LE setting so we
> currently provide the X1 Cross signed with expired X3.
>
> Netherless, the issue is that strangely we need to force caCertificate load
> in order to have the
Formal greetings everyone!! :)
My name is Gregory Cohen.
I am looking for developers to work on this new project with me.
I have recently joined certain mailing lists, and I am looking to get the
word out. There is no readme file yet, but I explain everything here, so
don't get mad :)
Feel free
Hello,
For the cert chain we are currently using the default LE setting so we
currently provide the X1 Cross signed with expired X3.
Netherless, the issue is that strangely we need to force caCertificate load
in order to have the connexion accepted.
Regards,
Christophe
Le mar. 5 oct. 2021 à 19
Please check if the certificate at server is correct created and uses
ISRG Root X1 instead of DST Root CA X3
ekke
Am 05.10.21 um 19:29 schrieb maitai:
Hi all,
Since the Let's Encrypt root certificate expired, we have a few users
unable to initiate a SSL connexion (most of them on recent Wind
On Tuesday, 5 October 2021 10:29:09 PDT maitai wrote:
> Hi all,
>
> Since the Let's Encrypt root certificate expired, we have a few users
> unable to initiate a SSL connexion (most of them on recent Windows 10
> version, app built with qt 5.15.6, but also some linux cases). We are
> using OpenSSL
Hi all,
Since the Let's Encrypt root certificate expired, we have a few users
unable to initiate a SSL connexion (most of them on recent Windows 10
version, app built with qt 5.15.6, but also some linux cases). We are
using OpenSSL 1.1.1.
After some searches, we found out that the ca-certifi
On Tuesday, 5 October 2021 09:53:55 PDT Richard Weickelt wrote:
> Does the "attach to running server" even work for cross builds?
It should. I haven't tested cross-architecture anything in nearly a decade,
but I have tested cross-OS and it worked sometime in the last year or so.
--
Thiago Macie
Tuukka said:
> Qt is well suited for this type of an approach, and we also have a
certified solution to the safety critical functionality:
https://www.qt.io/product/functional-safety-and-qt
...
Yeah, I've always found that link in particular to be at best, shady.
You start with this loud an
Hi,
> You can start it manually with qemu and tell it to stop before the first line
> of the application. Then tell Qt Creator to connect to the GDB server that
> qemu created.
>
> Debug > Start Debugging > Attach to Running Server
>
Thanks, but it doesn't work. The "Attach to Running Server"
On Tuesday, 5 October 2021 03:30:11 PDT joao morgado via Interest wrote:
> The officially supported CMake generator for building Qt is Ninja. You
> are using: 'Unix Makefiles' instead. Thus, you might encounter issues.
> Use at your own risk.
Huh, ok. I thought Makefiles were supported, that'
On Tuesday, 5 October 2021 06:11:50 PDT Richard Weickelt wrote:
> Hi,
>
> I want to run a bare metal application in a QEMU environment and debug it
> with gdb using Qt Creator. But I can only see a limited predefined selection
> of debug providers, like openocd, j-link, ...
>
> Is there no way to
Hi,
I want to run a bare metal application in a QEMU environment and debug it
with gdb using Qt Creator. But I can only see a limited predefined selection
of debug providers, like openocd, j-link, ...
Is there no way to run a custom command instead? I expected the "generic"
provider to cover that
Thiago
I found the problem, followed your advice I installed ninja-build and works
fine.In fact, I checked a old configure output, showed a warning:
+ exec /home/joao/qt6.2/qt5/qtbase/configure -top-level -developer-build -- -D
QT_BUILD_TESTS_BY_DEFAULT=OFF
'/usr/local/bin/cmake' '-D' 'QT_BUILD_
Try QtQuick.Shapes; you can get any shape you want. However those don’t do
vertex antialiasing, so you might need to turn on MSAA to get rid of the
jaggies. So it would be best to try to put all the shapes as children of one
item (or children of a root shape) so that you only need to set layer
Le mar. 5 oct. 2021 à 04:28, Murat ŞEKER via Interest
a écrit :
> We have a Quick scene where we draw a lot of semi-transparent rectangles and
> those rectangles are rounded in one side. As a representative :
> ...
> As it can be seen from the snippet above we use clipping to achieve rounding
>
18 matches
Mail list logo
