Digikam GSoC 2021

[Anjani Kumar]

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

On Apr 2 2021, at 12:42 am, Gilles Caulier <[hidden email]> wrote:

Le jeu. 1 avr. 2021 à 20:50, Anjani Kumar <[hidden email]> a écrit :

I have a complete list of files that need to be changed in order to compile with Qt6. I used clazy for this.  However i need to know if i should summarize the report by organizing them in modules or  I should present a complete list  for that, because the file list is huge.

Also what are your thoughts on using clazy to get the suggested changes and apply them and then build and do regression tests on the code?

I'm not sure if clazy is really the best static analyzer to use at first for this project.

After all the warnings from the compiler using Qt5.15.2 is a good start. Qt includes plenty of deprecated warnings to guide developers in the porting stage.

Clazy must be a good helper later, especially for optimization purposes.

Also the main porting stages must be prior. Classes which are removed in Qt6 need to be treated first, even if a qt5 compatibility helper framework exists in Qt6. Considering that compatibility frameworks do not exist can be a good choice to list which classes and codes need to be ported first.

Best

Gilles Caulier

[Gilles Caulier-4]

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <[hidden email]> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Anjani Kumar]

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Gilles Caulier-4]

I currently working on this port : MGA6 => MGA7

I am falling on the same dysfunction.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <[hidden email]> a écrit :

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Gilles Caulier-4]

The way to pass env var to Qt5 configure script is explained in helper doc :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3

Variables most be passed at end of .configure options, else it do not work.

MGA 7 provide openssl 1.1.0, not 1.1.1, as required to build Qt 5.15.2. this is why openssl is previously build as static library in /opt/openssl/ and env is passed to .configure script like this :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89

... but definitively, this doesn't work, certainly because .configure script from Qt is buggy :

Checking for OpenSSL...
Trying source 0 (type openssl) of library openssl ...
$OPENSSL_LIBS is not set.
  => source produced no result.
Trying source 1 (type inline) of library openssl ...
  => source failed condition 'config.win32'.
Trying source 2 (type inline) of library openssl ...
  => source failed condition 'config.msvc'.
Trying source 3 (type inline) of library openssl ...
  => source failed condition 'config.android'.
Trying source 4 (type inline) of library openssl ...
Include path \"/opt/openssl/include/\" is invalid.
  => source produced no result.

So :

1/ we cannot remove the system based openssl 1.1.0 as it used by plenty Qt5/KF5/DK dependencies to comple (aka mariabd, ffmpeg,opencv, etc.)

2/ to compile Qt 5.15.2, openssl 1.1.1 is required (too bad). So we need a extra static openssl only for qtbase.

3/ as .configure make a mess, and as i'm tired to waste my time with this archaic build system. I said stop.

4/ as Qt6 will be based on cmake and not qmake/configure

==> we will use Qt 5.15.1 under MGA7, as this version of Qt only require openssl 1.1.0.

And that all.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:57, Gilles Caulier <[hidden email]> a écrit :

I currently working on this port : MGA6 => MGA7

I am falling on the same dysfunction.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <[hidden email]> a écrit :

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Anjani Kumar]

It seems like Qt 5.15.1 is also failing to be configured. I also set the system installed openssl path but the errors are same :( 

On Apr 3 2021, at 5:45 pm, Gilles Caulier <[hidden email]> wrote:

The way to pass env var to Qt5 configure script is explained in helper doc :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3

Variables most be passed at end of .configure options, else it do not work.

MGA 7 provide openssl 1.1.0, not 1.1.1, as required to build Qt 5.15.2. this is why openssl is previously build as static library in /opt/openssl/ and env is passed to .configure script like this :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89

... but definitively, this doesn't work, certainly because .configure script from Qt is buggy :

Checking for OpenSSL...

Trying source 0 (type openssl) of library openssl ...

$OPENSSL_LIBS is not set.

  => source produced no result.

Trying source 1 (type inline) of library openssl ...

  => source failed condition 'config.win32'.

Trying source 2 (type inline) of library openssl ...

  => source failed condition 'config.msvc'.

Trying source 3 (type inline) of library openssl ...

  => source failed condition 'config.android'.

Trying source 4 (type inline) of library openssl ...

Include path \"/opt/openssl/include/\" is invalid.

  => source produced no result.

So :

1/ we cannot remove the system based openssl 1.1.0 as it used by plenty Qt5/KF5/DK dependencies to comple (aka mariabd, ffmpeg,opencv, etc.)

2/ to compile Qt 5.15.2, openssl 1.1.1 is required (too bad). So we need a extra static openssl only for qtbase.

3/ as .configure make a mess, and as i'm tired to waste my time with this archaic build system. I said stop.

4/ as Qt6 will be based on cmake and not qmake/configure

==> we will use Qt 5.15.1 under MGA7, as this version of Qt only require openssl 1.1.0.

And that all.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:57, Gilles Caulier <[hidden email]> a écrit :

I currently working on this port : MGA6 => MGA7

I am falling on the same dysfunction.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <[hidden email]> a écrit :

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Gilles Caulier-4]

yes i seen . in fact since Qt 5.15.0, openssl 1.1.1 is required.

There is no choice to found a way to force Qt 5.15.2 to use the static openssl compiled version installed to /opt/openssl.

I don't understand why configure script do not acceopt /opt/openssl/include directory as header path.

Gilles Caulier

Le sam. 3 avr. 2021 à 16:41, Anjani Kumar <[hidden email]> a écrit :

It seems like Qt 5.15.1 is also failing to be configured. I also set the system installed openssl path but the errors are same :( 

On Apr 3 2021, at 5:45 pm, Gilles Caulier <[hidden email]> wrote:

The way to pass env var to Qt5 configure script is explained in helper doc :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3

Variables most be passed at end of .configure options, else it do not work.

MGA 7 provide openssl 1.1.0, not 1.1.1, as required to build Qt 5.15.2. this is why openssl is previously build as static library in /opt/openssl/ and env is passed to .configure script like this :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89

... but definitively, this doesn't work, certainly because .configure script from Qt is buggy :

Checking for OpenSSL...

Trying source 0 (type openssl) of library openssl ...

$OPENSSL_LIBS is not set.

  => source produced no result.

Trying source 1 (type inline) of library openssl ...

  => source failed condition 'config.win32'.

Trying source 2 (type inline) of library openssl ...

  => source failed condition 'config.msvc'.

Trying source 3 (type inline) of library openssl ...

  => source failed condition 'config.android'.

Trying source 4 (type inline) of library openssl ...

Include path \"/opt/openssl/include/\" is invalid.

  => source produced no result.

So :

1/ we cannot remove the system based openssl 1.1.0 as it used by plenty Qt5/KF5/DK dependencies to comple (aka mariabd, ffmpeg,opencv, etc.)

2/ to compile Qt 5.15.2, openssl 1.1.1 is required (too bad). So we need a extra static openssl only for qtbase.

3/ as .configure make a mess, and as i'm tired to waste my time with this archaic build system. I said stop.

4/ as Qt6 will be based on cmake and not qmake/configure

==> we will use Qt 5.15.1 under MGA7, as this version of Qt only require openssl 1.1.0.

And that all.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:57, Gilles Caulier <[hidden email]> a écrit :

I currently working on this port : MGA6 => MGA7

I am falling on the same dysfunction.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <[hidden email]> a écrit :

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Gilles Caulier-4]

ok,

After to trying to force Qt5 to use a 3rd party openssl precompiled as static, to second a lower version of system native openssl,

configure script refuse to prior newer version. this work only to link the same openssl version but compiled with different options. The headers must be the same.

We cannot mix different version of openssl at the same time.

Qt5 configure make really a puzzle. Welcome to cmake with Qt6...

So definitely, the only solution is to use a system based with openssl 1.1.1 to support Qt 5.15.x and Qt 6.x, so MGA 8.

Best

Gilles Caulier

Le sam. 3 avr. 2021 à 17:30, Gilles Caulier <[hidden email]> a écrit :

yes i seen . in fact since Qt 5.15.0, openssl 1.1.1 is required.

There is no choice to found a way to force Qt 5.15.2 to use the static openssl compiled version installed to /opt/openssl.

I don't understand why configure script do not acceopt /opt/openssl/include directory as header path.

Gilles Caulier

Le sam. 3 avr. 2021 à 16:41, Anjani Kumar <[hidden email]> a écrit :

It seems like Qt 5.15.1 is also failing to be configured. I also set the system installed openssl path but the errors are same :( 

On Apr 3 2021, at 5:45 pm, Gilles Caulier <[hidden email]> wrote:

The way to pass env var to Qt5 configure script is explained in helper doc :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3

Variables most be passed at end of .configure options, else it do not work.

MGA 7 provide openssl 1.1.0, not 1.1.1, as required to build Qt 5.15.2. this is why openssl is previously build as static library in /opt/openssl/ and env is passed to .configure script like this :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89

... but definitively, this doesn't work, certainly because .configure script from Qt is buggy :

Checking for OpenSSL...

Trying source 0 (type openssl) of library openssl ...

$OPENSSL_LIBS is not set.

  => source produced no result.

Trying source 1 (type inline) of library openssl ...

  => source failed condition 'config.win32'.

Trying source 2 (type inline) of library openssl ...

  => source failed condition 'config.msvc'.

Trying source 3 (type inline) of library openssl ...

  => source failed condition 'config.android'.

Trying source 4 (type inline) of library openssl ...

Include path \"/opt/openssl/include/\" is invalid.

  => source produced no result.

So :

1/ we cannot remove the system based openssl 1.1.0 as it used by plenty Qt5/KF5/DK dependencies to comple (aka mariabd, ffmpeg,opencv, etc.)

2/ to compile Qt 5.15.2, openssl 1.1.1 is required (too bad). So we need a extra static openssl only for qtbase.

3/ as .configure make a mess, and as i'm tired to waste my time with this archaic build system. I said stop.

4/ as Qt6 will be based on cmake and not qmake/configure

==> we will use Qt 5.15.1 under MGA7, as this version of Qt only require openssl 1.1.0.

And that all.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:57, Gilles Caulier <[hidden email]> a écrit :

I currently working on this port : MGA6 => MGA7

I am falling on the same dysfunction.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <[hidden email]> a écrit :

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Anjani Kumar]

Thanks. I'll soon submit a proposal.

Anjani

On Sun, Apr 4, 2021, 3:08 PM Gilles Caulier <[hidden email]> wrote:

ok,

After to trying to force Qt5 to use a 3rd party openssl precompiled as static, to second a lower version of system native openssl,

configure script refuse to prior newer version. this work only to link the same openssl version but compiled with different options. The headers must be the same.

We cannot mix different version of openssl at the same time.

Qt5 configure make really a puzzle. Welcome to cmake with Qt6...

So definitely, the only solution is to use a system based with openssl 1.1.1 to support Qt 5.15.x and Qt 6.x, so MGA 8.

Best

Gilles Caulier

Le sam. 3 avr. 2021 à 17:30, Gilles Caulier <[hidden email]> a écrit :

yes i seen . in fact since Qt 5.15.0, openssl 1.1.1 is required.

There is no choice to found a way to force Qt 5.15.2 to use the static openssl compiled version installed to /opt/openssl.

I don't understand why configure script do not acceopt /opt/openssl/include directory as header path.

Gilles Caulier

Le sam. 3 avr. 2021 à 16:41, Anjani Kumar <[hidden email]> a écrit :

It seems like Qt 5.15.1 is also failing to be configured. I also set the system installed openssl path but the errors are same :( 

On Apr 3 2021, at 5:45 pm, Gilles Caulier <[hidden email]> wrote:

The way to pass env var to Qt5 configure script is explained in helper doc :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3

Variables most be passed at end of .configure options, else it do not work.

MGA 7 provide openssl 1.1.0, not 1.1.1, as required to build Qt 5.15.2. this is why openssl is previously build as static library in /opt/openssl/ and env is passed to .configure script like this :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89

... but definitively, this doesn't work, certainly because .configure script from Qt is buggy :

Checking for OpenSSL...

Trying source 0 (type openssl) of library openssl ...

$OPENSSL_LIBS is not set.

  => source produced no result.

Trying source 1 (type inline) of library openssl ...

  => source failed condition 'config.win32'.

Trying source 2 (type inline) of library openssl ...

  => source failed condition 'config.msvc'.

Trying source 3 (type inline) of library openssl ...

  => source failed condition 'config.android'.

Trying source 4 (type inline) of library openssl ...

Include path \"/opt/openssl/include/\" is invalid.

  => source produced no result.

So :

1/ we cannot remove the system based openssl 1.1.0 as it used by plenty Qt5/KF5/DK dependencies to comple (aka mariabd, ffmpeg,opencv, etc.)

2/ to compile Qt 5.15.2, openssl 1.1.1 is required (too bad). So we need a extra static openssl only for qtbase.

3/ as .configure make a mess, and as i'm tired to waste my time with this archaic build system. I said stop.

4/ as Qt6 will be based on cmake and not qmake/configure

==> we will use Qt 5.15.1 under MGA7, as this version of Qt only require openssl 1.1.0.

And that all.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:57, Gilles Caulier <[hidden email]> a écrit :

I currently working on this port : MGA6 => MGA7

I am falling on the same dysfunction.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <[hidden email]> a écrit :

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Anjani Kumar]

Hello, I have submitted the first draft of the proposal. I am a bit late for submitting it. I would like to apologize for that.

Thanks

Anjani

On Apr 4 2021, at 3:44 pm, Anjani Kumar <[hidden email]> wrote:

Thanks. I'll soon submit a proposal.

Anjani

On Sun, Apr 4, 2021, 3:08 PM Gilles Caulier <[hidden email]> wrote:

ok,

After to trying to force Qt5 to use a 3rd party openssl precompiled as static, to second a lower version of system native openssl,

configure script refuse to prior newer version. this work only to link the same openssl version but compiled with different options. The headers must be the same.

We cannot mix different version of openssl at the same time.

Qt5 configure make really a puzzle. Welcome to cmake with Qt6...

So definitely, the only solution is to use a system based with openssl 1.1.1 to support Qt 5.15.x and Qt 6.x, so MGA 8.

Best

Gilles Caulier

Le sam. 3 avr. 2021 à 17:30, Gilles Caulier <[hidden email]> a écrit :

yes i seen . in fact since Qt 5.15.0, openssl 1.1.1 is required.

There is no choice to found a way to force Qt 5.15.2 to use the static openssl compiled version installed to /opt/openssl.

I don't understand why configure script do not acceopt /opt/openssl/include directory as header path.

Gilles Caulier

Le sam. 3 avr. 2021 à 16:41, Anjani Kumar <[hidden email]> a écrit :

It seems like Qt 5.15.1 is also failing to be configured. I also set the system installed openssl path but the errors are same :( 

On Apr 3 2021, at 5:45 pm, Gilles Caulier <[hidden email]> wrote:

The way to pass env var to Qt5 configure script is explained in helper doc :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3

Variables most be passed at end of .configure options, else it do not work.

MGA 7 provide openssl 1.1.0, not 1.1.1, as required to build Qt 5.15.2. this is why openssl is previously build as static library in /opt/openssl/ and env is passed to .configure script like this :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89

... but definitively, this doesn't work, certainly because .configure script from Qt is buggy :

Checking for OpenSSL...

Trying source 0 (type openssl) of library openssl ...

$OPENSSL_LIBS is not set.

  => source produced no result.

Trying source 1 (type inline) of library openssl ...

  => source failed condition 'config.win32'.

Trying source 2 (type inline) of library openssl ...

  => source failed condition 'config.msvc'.

Trying source 3 (type inline) of library openssl ...

  => source failed condition 'config.android'.

Trying source 4 (type inline) of library openssl ...

Include path \"/opt/openssl/include/\" is invalid.

  => source produced no result.

So :

1/ we cannot remove the system based openssl 1.1.0 as it used by plenty Qt5/KF5/DK dependencies to comple (aka mariabd, ffmpeg,opencv, etc.)

2/ to compile Qt 5.15.2, openssl 1.1.1 is required (too bad). So we need a extra static openssl only for qtbase.

3/ as .configure make a mess, and as i'm tired to waste my time with this archaic build system. I said stop.

4/ as Qt6 will be based on cmake and not qmake/configure

==> we will use Qt 5.15.1 under MGA7, as this version of Qt only require openssl 1.1.0.

And that all.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:57, Gilles Caulier <[hidden email]> a écrit :

I currently working on this port : MGA6 => MGA7

I am falling on the same dysfunction.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <[hidden email]> a écrit :

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Gilles Caulier-4]

Hi,

I saw. I will comment on your document inline today.

Best

Gilles Caulier

Le lun. 5 avr. 2021 à 00:08, Anjani Kumar <[hidden email]> a écrit :

Hello, I have submitted the first draft of the proposal. I am a bit late for submitting it. I would like to apologize for that.

Thanks

Anjani

On Apr 4 2021, at 3:44 pm, Anjani Kumar <[hidden email]> wrote:

Thanks. I'll soon submit a proposal.

Anjani

On Sun, Apr 4, 2021, 3:08 PM Gilles Caulier <[hidden email]> wrote:

ok,

After to trying to force Qt5 to use a 3rd party openssl precompiled as static, to second a lower version of system native openssl,

configure script refuse to prior newer version. this work only to link the same openssl version but compiled with different options. The headers must be the same.

We cannot mix different version of openssl at the same time.

Qt5 configure make really a puzzle. Welcome to cmake with Qt6...

So definitely, the only solution is to use a system based with openssl 1.1.1 to support Qt 5.15.x and Qt 6.x, so MGA 8.

Best

Gilles Caulier

Le sam. 3 avr. 2021 à 17:30, Gilles Caulier <[hidden email]> a écrit :

yes i seen . in fact since Qt 5.15.0, openssl 1.1.1 is required.

There is no choice to found a way to force Qt 5.15.2 to use the static openssl compiled version installed to /opt/openssl.

I don't understand why configure script do not acceopt /opt/openssl/include directory as header path.

Gilles Caulier

Le sam. 3 avr. 2021 à 16:41, Anjani Kumar <[hidden email]> a écrit :

It seems like Qt 5.15.1 is also failing to be configured. I also set the system installed openssl path but the errors are same :( 

On Apr 3 2021, at 5:45 pm, Gilles Caulier <[hidden email]> wrote:

The way to pass env var to Qt5 configure script is explained in helper doc :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3

Variables most be passed at end of .configure options, else it do not work.

MGA 7 provide openssl 1.1.0, not 1.1.1, as required to build Qt 5.15.2. this is why openssl is previously build as static library in /opt/openssl/ and env is passed to .configure script like this :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89

... but definitively, this doesn't work, certainly because .configure script from Qt is buggy :

Checking for OpenSSL...

Trying source 0 (type openssl) of library openssl ...

$OPENSSL_LIBS is not set.

  => source produced no result.

Trying source 1 (type inline) of library openssl ...

  => source failed condition 'config.win32'.

Trying source 2 (type inline) of library openssl ...

  => source failed condition 'config.msvc'.

Trying source 3 (type inline) of library openssl ...

  => source failed condition 'config.android'.

Trying source 4 (type inline) of library openssl ...

Include path \"/opt/openssl/include/\" is invalid.

  => source produced no result.

So :

1/ we cannot remove the system based openssl 1.1.0 as it used by plenty Qt5/KF5/DK dependencies to comple (aka mariabd, ffmpeg,opencv, etc.)

2/ to compile Qt 5.15.2, openssl 1.1.1 is required (too bad). So we need a extra static openssl only for qtbase.

3/ as .configure make a mess, and as i'm tired to waste my time with this archaic build system. I said stop.

4/ as Qt6 will be based on cmake and not qmake/configure

==> we will use Qt 5.15.1 under MGA7, as this version of Qt only require openssl 1.1.0.

And that all.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:57, Gilles Caulier <[hidden email]> a écrit :

I currently working on this port : MGA6 => MGA7

I am falling on the same dysfunction.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <[hidden email]> a écrit :

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Anjani Kumar]

Is there a good way extract/export only compiler warnings and errors to file? I can filter them out later from the output but is there a way to do this in a better way?

On Apr 5 2021, at 9:04 am, Gilles Caulier <[hidden email]> wrote:

Hi,

I saw. I will comment on your document inline today.

Best

Gilles Caulier

Le lun. 5 avr. 2021 à 00:08, Anjani Kumar <[hidden email]> a écrit :

Hello, I have submitted the first draft of the proposal. I am a bit late for submitting it. I would like to apologize for that.

Thanks

Anjani

On Apr 4 2021, at 3:44 pm, Anjani Kumar <[hidden email]> wrote:

Thanks. I'll soon submit a proposal.

Anjani

On Sun, Apr 4, 2021, 3:08 PM Gilles Caulier <[hidden email]> wrote:

ok,

After to trying to force Qt5 to use a 3rd party openssl precompiled as static, to second a lower version of system native openssl,

configure script refuse to prior newer version. this work only to link the same openssl version but compiled with different options. The headers must be the same.

We cannot mix different version of openssl at the same time.

Qt5 configure make really a puzzle. Welcome to cmake with Qt6...

So definitely, the only solution is to use a system based with openssl 1.1.1 to support Qt 5.15.x and Qt 6.x, so MGA 8.

Best

Gilles Caulier

Le sam. 3 avr. 2021 à 17:30, Gilles Caulier <[hidden email]> a écrit :

yes i seen . in fact since Qt 5.15.0, openssl 1.1.1 is required.

There is no choice to found a way to force Qt 5.15.2 to use the static openssl compiled version installed to /opt/openssl.

I don't understand why configure script do not acceopt /opt/openssl/include directory as header path.

Gilles Caulier

Le sam. 3 avr. 2021 à 16:41, Anjani Kumar <[hidden email]> a écrit :

It seems like Qt 5.15.1 is also failing to be configured. I also set the system installed openssl path but the errors are same :( 

On Apr 3 2021, at 5:45 pm, Gilles Caulier <[hidden email]> wrote:

The way to pass env var to Qt5 configure script is explained in helper doc :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3

Variables most be passed at end of .configure options, else it do not work.

MGA 7 provide openssl 1.1.0, not 1.1.1, as required to build Qt 5.15.2. this is why openssl is previously build as static library in /opt/openssl/ and env is passed to .configure script like this :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89

... but definitively, this doesn't work, certainly because .configure script from Qt is buggy :

Checking for OpenSSL...

Trying source 0 (type openssl) of library openssl ...

$OPENSSL_LIBS is not set.

  => source produced no result.

Trying source 1 (type inline) of library openssl ...

  => source failed condition 'config.win32'.

Trying source 2 (type inline) of library openssl ...

  => source failed condition 'config.msvc'.

Trying source 3 (type inline) of library openssl ...

  => source failed condition 'config.android'.

Trying source 4 (type inline) of library openssl ...

Include path \"/opt/openssl/include/\" is invalid.

  => source produced no result.

So :

1/ we cannot remove the system based openssl 1.1.0 as it used by plenty Qt5/KF5/DK dependencies to comple (aka mariabd, ffmpeg,opencv, etc.)

2/ to compile Qt 5.15.2, openssl 1.1.1 is required (too bad). So we need a extra static openssl only for qtbase.

3/ as .configure make a mess, and as i'm tired to waste my time with this archaic build system. I said stop.

4/ as Qt6 will be based on cmake and not qmake/configure

==> we will use Qt 5.15.1 under MGA7, as this version of Qt only require openssl 1.1.0.

And that all.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:57, Gilles Caulier <[hidden email]> a écrit :

I currently working on this port : MGA6 => MGA7

I am falling on the same dysfunction.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <[hidden email]> a écrit :

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Gilles Caulier-4]

Look in Python script used to parse Clazy compilation trace and extract all relevant warnings based on turned on flag :

https://invent.kde.org/graphics/digikam/-/blob/master/project/reports/clazy_visualizer.py

Gilles Caulier

Le mer. 7 avr. 2021 à 17:08, Anjani Kumar <[hidden email]> a écrit :

Is there a good way extract/export only compiler warnings and errors to file? I can filter them out later from the output but is there a way to do this in a better way?

On Apr 5 2021, at 9:04 am, Gilles Caulier <[hidden email]> wrote:

Hi,

I saw. I will comment on your document inline today.

Best

Gilles Caulier

Le lun. 5 avr. 2021 à 00:08, Anjani Kumar <[hidden email]> a écrit :

Hello, I have submitted the first draft of the proposal. I am a bit late for submitting it. I would like to apologize for that.

Thanks

Anjani

On Apr 4 2021, at 3:44 pm, Anjani Kumar <[hidden email]> wrote:

Thanks. I'll soon submit a proposal.

Anjani

On Sun, Apr 4, 2021, 3:08 PM Gilles Caulier <[hidden email]> wrote:

ok,

After to trying to force Qt5 to use a 3rd party openssl precompiled as static, to second a lower version of system native openssl,

configure script refuse to prior newer version. this work only to link the same openssl version but compiled with different options. The headers must be the same.

We cannot mix different version of openssl at the same time.

Qt5 configure make really a puzzle. Welcome to cmake with Qt6...

So definitely, the only solution is to use a system based with openssl 1.1.1 to support Qt 5.15.x and Qt 6.x, so MGA 8.

Best

Gilles Caulier

Le sam. 3 avr. 2021 à 17:30, Gilles Caulier <[hidden email]> a écrit :

yes i seen . in fact since Qt 5.15.0, openssl 1.1.1 is required.

There is no choice to found a way to force Qt 5.15.2 to use the static openssl compiled version installed to /opt/openssl.

I don't understand why configure script do not acceopt /opt/openssl/include directory as header path.

Gilles Caulier

Le sam. 3 avr. 2021 à 16:41, Anjani Kumar <[hidden email]> a écrit :

It seems like Qt 5.15.1 is also failing to be configured. I also set the system installed openssl path but the errors are same :( 

On Apr 3 2021, at 5:45 pm, Gilles Caulier <[hidden email]> wrote:

The way to pass env var to Qt5 configure script is explained in helper doc :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3

Variables most be passed at end of .configure options, else it do not work.

MGA 7 provide openssl 1.1.0, not 1.1.1, as required to build Qt 5.15.2. this is why openssl is previously build as static library in /opt/openssl/ and env is passed to .configure script like this :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89

... but definitively, this doesn't work, certainly because .configure script from Qt is buggy :

Checking for OpenSSL...

Trying source 0 (type openssl) of library openssl ...

$OPENSSL_LIBS is not set.

  => source produced no result.

Trying source 1 (type inline) of library openssl ...

  => source failed condition 'config.win32'.

Trying source 2 (type inline) of library openssl ...

  => source failed condition 'config.msvc'.

Trying source 3 (type inline) of library openssl ...

  => source failed condition 'config.android'.

Trying source 4 (type inline) of library openssl ...

Include path \"/opt/openssl/include/\" is invalid.

  => source produced no result.

So :

1/ we cannot remove the system based openssl 1.1.0 as it used by plenty Qt5/KF5/DK dependencies to comple (aka mariabd, ffmpeg,opencv, etc.)

2/ to compile Qt 5.15.2, openssl 1.1.1 is required (too bad). So we need a extra static openssl only for qtbase.

3/ as .configure make a mess, and as i'm tired to waste my time with this archaic build system. I said stop.

4/ as Qt6 will be based on cmake and not qmake/configure

==> we will use Qt 5.15.1 under MGA7, as this version of Qt only require openssl 1.1.0.

And that all.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:57, Gilles Caulier <[hidden email]> a écrit :

I currently working on this port : MGA6 => MGA7

I am falling on the same dysfunction.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <[hidden email]> a écrit :

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Anjani Kumar]

I am trying to run clazy.sh

Well it runs and then crashes midway on command "make -j12 2> reports.clazy/trace.log"

when i re-run this command again then build succeeds . I try to visualize it using clazy_visualize.sh and the report it generates contains only one warning type "qt6-qhash-signature"  but clearly in my log file, there are other warnings as well.  I guess this is caused by build failure in between and wrong report is generated.

I'm trying to debug it.

Thanks

Anjani

On Apr 7 2021, at 9:30 pm, Gilles Caulier <[hidden email]> wrote:

Look in Python script used to parse Clazy compilation trace and extract all relevant warnings based on turned on flag :

https://invent.kde.org/graphics/digikam/-/blob/master/project/reports/clazy_visualizer.py

Gilles Caulier

Le mer. 7 avr. 2021 à 17:08, Anjani Kumar <[hidden email]> a écrit :

Is there a good way extract/export only compiler warnings and errors to file? I can filter them out later from the output but is there a way to do this in a better way?

On Apr 5 2021, at 9:04 am, Gilles Caulier <[hidden email]> wrote:

Hi,

I saw. I will comment on your document inline today.

Best

Gilles Caulier

Le lun. 5 avr. 2021 à 00:08, Anjani Kumar <[hidden email]> a écrit :

Hello, I have submitted the first draft of the proposal. I am a bit late for submitting it. I would like to apologize for that.

Thanks

Anjani

On Apr 4 2021, at 3:44 pm, Anjani Kumar <[hidden email]> wrote:

Thanks. I'll soon submit a proposal.

Anjani

On Sun, Apr 4, 2021, 3:08 PM Gilles Caulier <[hidden email]> wrote:

ok,

After to trying to force Qt5 to use a 3rd party openssl precompiled as static, to second a lower version of system native openssl,

configure script refuse to prior newer version. this work only to link the same openssl version but compiled with different options. The headers must be the same.

We cannot mix different version of openssl at the same time.

Qt5 configure make really a puzzle. Welcome to cmake with Qt6...

So definitely, the only solution is to use a system based with openssl 1.1.1 to support Qt 5.15.x and Qt 6.x, so MGA 8.

Best

Gilles Caulier

Le sam. 3 avr. 2021 à 17:30, Gilles Caulier <[hidden email]> a écrit :

yes i seen . in fact since Qt 5.15.0, openssl 1.1.1 is required.

There is no choice to found a way to force Qt 5.15.2 to use the static openssl compiled version installed to /opt/openssl.

I don't understand why configure script do not acceopt /opt/openssl/include directory as header path.

Gilles Caulier

Le sam. 3 avr. 2021 à 16:41, Anjani Kumar <[hidden email]> a écrit :

It seems like Qt 5.15.1 is also failing to be configured. I also set the system installed openssl path but the errors are same :( 

On Apr 3 2021, at 5:45 pm, Gilles Caulier <[hidden email]> wrote:

The way to pass env var to Qt5 configure script is explained in helper doc :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3

Variables most be passed at end of .configure options, else it do not work.

MGA 7 provide openssl 1.1.0, not 1.1.1, as required to build Qt 5.15.2. this is why openssl is previously build as static library in /opt/openssl/ and env is passed to .configure script like this :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89

... but definitively, this doesn't work, certainly because .configure script from Qt is buggy :

Checking for OpenSSL...

Trying source 0 (type openssl) of library openssl ...

$OPENSSL_LIBS is not set.

  => source produced no result.

Trying source 1 (type inline) of library openssl ...

  => source failed condition 'config.win32'.

Trying source 2 (type inline) of library openssl ...

  => source failed condition 'config.msvc'.

Trying source 3 (type inline) of library openssl ...

  => source failed condition 'config.android'.

Trying source 4 (type inline) of library openssl ...

Include path \"/opt/openssl/include/\" is invalid.

  => source produced no result.

So :

1/ we cannot remove the system based openssl 1.1.0 as it used by plenty Qt5/KF5/DK dependencies to comple (aka mariabd, ffmpeg,opencv, etc.)

2/ to compile Qt 5.15.2, openssl 1.1.1 is required (too bad). So we need a extra static openssl only for qtbase.

3/ as .configure make a mess, and as i'm tired to waste my time with this archaic build system. I said stop.

4/ as Qt6 will be based on cmake and not qmake/configure

==> we will use Qt 5.15.1 under MGA7, as this version of Qt only require openssl 1.1.0.

And that all.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:57, Gilles Caulier <[hidden email]> a écrit :

I currently working on this port : MGA6 => MGA7

I am falling on the same dysfunction.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <[hidden email]> a écrit :

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Anjani Kumar]

clazy_visualizer.sh  missed new added flags. I submitted a patch to fix.

Thanks

Anjani

On Apr 8 2021, at 12:20 am, Anjani Kumar <[hidden email]> wrote:

I am trying to run clazy.sh

Well it runs and then crashes midway on command "make -j12 2> reports.clazy/trace.log"

when i re-run this command again then build succeeds . I try to visualize it using clazy_visualize.sh and the report it generates contains only one warning type "qt6-qhash-signature"  but clearly in my log file, there are other warnings as well.  I guess this is caused by build failure in between and wrong report is generated.

I'm trying to debug it.

Thanks

Anjani

On Apr 7 2021, at 9:30 pm, Gilles Caulier <[hidden email]> wrote:

Look in Python script used to parse Clazy compilation trace and extract all relevant warnings based on turned on flag :

https://invent.kde.org/graphics/digikam/-/blob/master/project/reports/clazy_visualizer.py

Gilles Caulier

Le mer. 7 avr. 2021 à 17:08, Anjani Kumar <[hidden email]> a écrit :

Is there a good way extract/export only compiler warnings and errors to file? I can filter them out later from the output but is there a way to do this in a better way?

On Apr 5 2021, at 9:04 am, Gilles Caulier <[hidden email]> wrote:

Hi,

I saw. I will comment on your document inline today.

Best

Gilles Caulier

Le lun. 5 avr. 2021 à 00:08, Anjani Kumar <[hidden email]> a écrit :

Hello, I have submitted the first draft of the proposal. I am a bit late for submitting it. I would like to apologize for that.

Thanks

Anjani

On Apr 4 2021, at 3:44 pm, Anjani Kumar <[hidden email]> wrote:

Thanks. I'll soon submit a proposal.

Anjani

On Sun, Apr 4, 2021, 3:08 PM Gilles Caulier <[hidden email]> wrote:

ok,

After to trying to force Qt5 to use a 3rd party openssl precompiled as static, to second a lower version of system native openssl,

configure script refuse to prior newer version. this work only to link the same openssl version but compiled with different options. The headers must be the same.

We cannot mix different version of openssl at the same time.

Qt5 configure make really a puzzle. Welcome to cmake with Qt6...

So definitely, the only solution is to use a system based with openssl 1.1.1 to support Qt 5.15.x and Qt 6.x, so MGA 8.

Best

Gilles Caulier

Le sam. 3 avr. 2021 à 17:30, Gilles Caulier <[hidden email]> a écrit :

yes i seen . in fact since Qt 5.15.0, openssl 1.1.1 is required.

There is no choice to found a way to force Qt 5.15.2 to use the static openssl compiled version installed to /opt/openssl.

I don't understand why configure script do not acceopt /opt/openssl/include directory as header path.

Gilles Caulier

Le sam. 3 avr. 2021 à 16:41, Anjani Kumar <[hidden email]> a écrit :

It seems like Qt 5.15.1 is also failing to be configured. I also set the system installed openssl path but the errors are same :( 

On Apr 3 2021, at 5:45 pm, Gilles Caulier <[hidden email]> wrote:

The way to pass env var to Qt5 configure script is explained in helper doc :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3

Variables most be passed at end of .configure options, else it do not work.

MGA 7 provide openssl 1.1.0, not 1.1.1, as required to build Qt 5.15.2. this is why openssl is previously build as static library in /opt/openssl/ and env is passed to .configure script like this :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89

... but definitively, this doesn't work, certainly because .configure script from Qt is buggy :

Checking for OpenSSL...

Trying source 0 (type openssl) of library openssl ...

$OPENSSL_LIBS is not set.

  => source produced no result.

Trying source 1 (type inline) of library openssl ...

  => source failed condition 'config.win32'.

Trying source 2 (type inline) of library openssl ...

  => source failed condition 'config.msvc'.

Trying source 3 (type inline) of library openssl ...

  => source failed condition 'config.android'.

Trying source 4 (type inline) of library openssl ...

Include path \"/opt/openssl/include/\" is invalid.

  => source produced no result.

So :

1/ we cannot remove the system based openssl 1.1.0 as it used by plenty Qt5/KF5/DK dependencies to comple (aka mariabd, ffmpeg,opencv, etc.)

2/ to compile Qt 5.15.2, openssl 1.1.1 is required (too bad). So we need a extra static openssl only for qtbase.

3/ as .configure make a mess, and as i'm tired to waste my time with this archaic build system. I said stop.

4/ as Qt6 will be based on cmake and not qmake/configure

==> we will use Qt 5.15.1 under MGA7, as this version of Qt only require openssl 1.1.0.

And that all.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:57, Gilles Caulier <[hidden email]> a écrit :

I currently working on this port : MGA6 => MGA7

I am falling on the same dysfunction.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <[hidden email]> a écrit :

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Gilles Caulier-4]

You need to use the Clazy stable tag. the last one is v1.9.

The clang version used is important. Here i use 11.0.1

and finally, the check options for clazy to enable is important, as some options are under development and make the process unstable.

I recommend limiting multicore use. No need to overload the computer with plenty of concurrent memory allocation to compile codes. 12 cores is heavy. 4 or 6 is enough i think (here i use 3 cores only.

Gilles Caulier

Le mer. 7 avr. 2021 à 20:51, Anjani Kumar <[hidden email]> a écrit :

I am trying to run clazy.sh

Well it runs and then crashes midway on command "make -j12 2> reports.clazy/trace.log"

when i re-run this command again then build succeeds . I try to visualize it using clazy_visualize.sh and the report it generates contains only one warning type "qt6-qhash-signature"  but clearly in my log file, there are other warnings as well.  I guess this is caused by build failure in between and wrong report is generated.

I'm trying to debug it.

Thanks

Anjani

On Apr 7 2021, at 9:30 pm, Gilles Caulier <[hidden email]> wrote:

Look in Python script used to parse Clazy compilation trace and extract all relevant warnings based on turned on flag :

https://invent.kde.org/graphics/digikam/-/blob/master/project/reports/clazy_visualizer.py

Gilles Caulier

Le mer. 7 avr. 2021 à 17:08, Anjani Kumar <[hidden email]> a écrit :

Is there a good way extract/export only compiler warnings and errors to file? I can filter them out later from the output but is there a way to do this in a better way?

On Apr 5 2021, at 9:04 am, Gilles Caulier <[hidden email]> wrote:

Hi,

I saw. I will comment on your document inline today.

Best

Gilles Caulier

Le lun. 5 avr. 2021 à 00:08, Anjani Kumar <[hidden email]> a écrit :

Hello, I have submitted the first draft of the proposal. I am a bit late for submitting it. I would like to apologize for that.

Thanks

Anjani

On Apr 4 2021, at 3:44 pm, Anjani Kumar <[hidden email]> wrote:

Thanks. I'll soon submit a proposal.

Anjani

On Sun, Apr 4, 2021, 3:08 PM Gilles Caulier <[hidden email]> wrote:

ok,

After to trying to force Qt5 to use a 3rd party openssl precompiled as static, to second a lower version of system native openssl,

configure script refuse to prior newer version. this work only to link the same openssl version but compiled with different options. The headers must be the same.

We cannot mix different version of openssl at the same time.

Qt5 configure make really a puzzle. Welcome to cmake with Qt6...

So definitely, the only solution is to use a system based with openssl 1.1.1 to support Qt 5.15.x and Qt 6.x, so MGA 8.

Best

Gilles Caulier

Le sam. 3 avr. 2021 à 17:30, Gilles Caulier <[hidden email]> a écrit :

yes i seen . in fact since Qt 5.15.0, openssl 1.1.1 is required.

There is no choice to found a way to force Qt 5.15.2 to use the static openssl compiled version installed to /opt/openssl.

I don't understand why configure script do not acceopt /opt/openssl/include directory as header path.

Gilles Caulier

Le sam. 3 avr. 2021 à 16:41, Anjani Kumar <[hidden email]> a écrit :

It seems like Qt 5.15.1 is also failing to be configured. I also set the system installed openssl path but the errors are same :( 

On Apr 3 2021, at 5:45 pm, Gilles Caulier <[hidden email]> wrote:

The way to pass env var to Qt5 configure script is explained in helper doc :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3

Variables most be passed at end of .configure options, else it do not work.

MGA 7 provide openssl 1.1.0, not 1.1.1, as required to build Qt 5.15.2. this is why openssl is previously build as static library in /opt/openssl/ and env is passed to .configure script like this :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89

... but definitively, this doesn't work, certainly because .configure script from Qt is buggy :

Checking for OpenSSL...

Trying source 0 (type openssl) of library openssl ...

$OPENSSL_LIBS is not set.

  => source produced no result.

Trying source 1 (type inline) of library openssl ...

  => source failed condition 'config.win32'.

Trying source 2 (type inline) of library openssl ...

  => source failed condition 'config.msvc'.

Trying source 3 (type inline) of library openssl ...

  => source failed condition 'config.android'.

Trying source 4 (type inline) of library openssl ...

Include path \"/opt/openssl/include/\" is invalid.

  => source produced no result.

So :

1/ we cannot remove the system based openssl 1.1.0 as it used by plenty Qt5/KF5/DK dependencies to comple (aka mariabd, ffmpeg,opencv, etc.)

2/ to compile Qt 5.15.2, openssl 1.1.1 is required (too bad). So we need a extra static openssl only for qtbase.

3/ as .configure make a mess, and as i'm tired to waste my time with this archaic build system. I said stop.

4/ as Qt6 will be based on cmake and not qmake/configure

==> we will use Qt 5.15.1 under MGA7, as this version of Qt only require openssl 1.1.0.

And that all.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:57, Gilles Caulier <[hidden email]> a écrit :

I currently working on this port : MGA6 => MGA7

I am falling on the same dysfunction.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <[hidden email]> a écrit :

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Gilles Caulier-4]

Hi,

I can reproduce the crash at around 35% of CLazy compilation.

It Sounds like one of the Qt6 checkers is buggy.

Try to re-run clazy with only with the first Qt6 option enabled to see if it passes. If yes, try again to activate the second, etc... The goal is to determine which option cannot be used.

Gilles Caulier

Le mer. 7 avr. 2021 à 17:17, Gilles Caulier <[hidden email]> a écrit :

You need to use the Clazy stable tag. the last one is v1.9.

The clang version used is important. Here i use 11.0.1

and finally, the check options for clazy to enable is important, as some options are under development and make the process unstable.

I recommend limiting multicore use. No need to overload the computer with plenty of concurrent memory allocation to compile codes. 12 cores is heavy. 4 or 6 is enough i think (here i use 3 cores only.

Gilles Caulier

Le mer. 7 avr. 2021 à 20:51, Anjani Kumar <[hidden email]> a écrit :

I am trying to run clazy.sh

Well it runs and then crashes midway on command "make -j12 2> reports.clazy/trace.log"

when i re-run this command again then build succeeds . I try to visualize it using clazy_visualize.sh and the report it generates contains only one warning type "qt6-qhash-signature"  but clearly in my log file, there are other warnings as well.  I guess this is caused by build failure in between and wrong report is generated.

I'm trying to debug it.

Thanks

Anjani

On Apr 7 2021, at 9:30 pm, Gilles Caulier <[hidden email]> wrote:

Look in Python script used to parse Clazy compilation trace and extract all relevant warnings based on turned on flag :

https://invent.kde.org/graphics/digikam/-/blob/master/project/reports/clazy_visualizer.py

Gilles Caulier

Le mer. 7 avr. 2021 à 17:08, Anjani Kumar <[hidden email]> a écrit :

Is there a good way extract/export only compiler warnings and errors to file? I can filter them out later from the output but is there a way to do this in a better way?

On Apr 5 2021, at 9:04 am, Gilles Caulier <[hidden email]> wrote:

Hi,

I saw. I will comment on your document inline today.

Best

Gilles Caulier

Le lun. 5 avr. 2021 à 00:08, Anjani Kumar <[hidden email]> a écrit :

Hello, I have submitted the first draft of the proposal. I am a bit late for submitting it. I would like to apologize for that.

Thanks

Anjani

On Apr 4 2021, at 3:44 pm, Anjani Kumar <[hidden email]> wrote:

Thanks. I'll soon submit a proposal.

Anjani

On Sun, Apr 4, 2021, 3:08 PM Gilles Caulier <[hidden email]> wrote:

ok,

After to trying to force Qt5 to use a 3rd party openssl precompiled as static, to second a lower version of system native openssl,

configure script refuse to prior newer version. this work only to link the same openssl version but compiled with different options. The headers must be the same.

We cannot mix different version of openssl at the same time.

Qt5 configure make really a puzzle. Welcome to cmake with Qt6...

So definitely, the only solution is to use a system based with openssl 1.1.1 to support Qt 5.15.x and Qt 6.x, so MGA 8.

Best

Gilles Caulier

Le sam. 3 avr. 2021 à 17:30, Gilles Caulier <[hidden email]> a écrit :

yes i seen . in fact since Qt 5.15.0, openssl 1.1.1 is required.

There is no choice to found a way to force Qt 5.15.2 to use the static openssl compiled version installed to /opt/openssl.

I don't understand why configure script do not acceopt /opt/openssl/include directory as header path.

Gilles Caulier

Le sam. 3 avr. 2021 à 16:41, Anjani Kumar <[hidden email]> a écrit :

It seems like Qt 5.15.1 is also failing to be configured. I also set the system installed openssl path but the errors are same :( 

On Apr 3 2021, at 5:45 pm, Gilles Caulier <[hidden email]> wrote:

The way to pass env var to Qt5 configure script is explained in helper doc :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3

Variables most be passed at end of .configure options, else it do not work.

MGA 7 provide openssl 1.1.0, not 1.1.1, as required to build Qt 5.15.2. this is why openssl is previously build as static library in /opt/openssl/ and env is passed to .configure script like this :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89

... but definitively, this doesn't work, certainly because .configure script from Qt is buggy :

Checking for OpenSSL...

Trying source 0 (type openssl) of library openssl ...

$OPENSSL_LIBS is not set.

  => source produced no result.

Trying source 1 (type inline) of library openssl ...

  => source failed condition 'config.win32'.

Trying source 2 (type inline) of library openssl ...

  => source failed condition 'config.msvc'.

Trying source 3 (type inline) of library openssl ...

  => source failed condition 'config.android'.

Trying source 4 (type inline) of library openssl ...

Include path \"/opt/openssl/include/\" is invalid.

  => source produced no result.

So :

1/ we cannot remove the system based openssl 1.1.0 as it used by plenty Qt5/KF5/DK dependencies to comple (aka mariabd, ffmpeg,opencv, etc.)

2/ to compile Qt 5.15.2, openssl 1.1.1 is required (too bad). So we need a extra static openssl only for qtbase.

3/ as .configure make a mess, and as i'm tired to waste my time with this archaic build system. I said stop.

4/ as Qt6 will be based on cmake and not qmake/configure

==> we will use Qt 5.15.1 under MGA7, as this version of Qt only require openssl 1.1.0.

And that all.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:57, Gilles Caulier <[hidden email]> a écrit :

I currently working on this port : MGA6 => MGA7

I am falling on the same dysfunction.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <[hidden email]> a écrit :

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Anjani Kumar]

I think qt6-deprecated-api-fixes option is the culprit though I'm not sure.

On Apr 8 2021, at 6:16 pm, Gilles Caulier <[hidden email]> wrote:

Hi,

I can reproduce the crash at around 35% of CLazy compilation.

It Sounds like one of the Qt6 checkers is buggy.

Try to re-run clazy with only with the first Qt6 option enabled to see if it passes. If yes, try again to activate the second, etc... The goal is to determine which option cannot be used.

Gilles Caulier

Le mer. 7 avr. 2021 à 17:17, Gilles Caulier <[hidden email]> a écrit :

You need to use the Clazy stable tag. the last one is v1.9.

The clang version used is important. Here i use 11.0.1

and finally, the check options for clazy to enable is important, as some options are under development and make the process unstable.

I recommend limiting multicore use. No need to overload the computer with plenty of concurrent memory allocation to compile codes. 12 cores is heavy. 4 or 6 is enough i think (here i use 3 cores only.

Gilles Caulier

Le mer. 7 avr. 2021 à 20:51, Anjani Kumar <[hidden email]> a écrit :

I am trying to run clazy.sh

Well it runs and then crashes midway on command "make -j12 2> reports.clazy/trace.log"

when i re-run this command again then build succeeds . I try to visualize it using clazy_visualize.sh and the report it generates contains only one warning type "qt6-qhash-signature"  but clearly in my log file, there are other warnings as well.  I guess this is caused by build failure in between and wrong report is generated.

I'm trying to debug it.

Thanks

Anjani

On Apr 7 2021, at 9:30 pm, Gilles Caulier <[hidden email]> wrote:

Look in Python script used to parse Clazy compilation trace and extract all relevant warnings based on turned on flag :

https://invent.kde.org/graphics/digikam/-/blob/master/project/reports/clazy_visualizer.py

Gilles Caulier

Le mer. 7 avr. 2021 à 17:08, Anjani Kumar <[hidden email]> a écrit :

Is there a good way extract/export only compiler warnings and errors to file? I can filter them out later from the output but is there a way to do this in a better way?

On Apr 5 2021, at 9:04 am, Gilles Caulier <[hidden email]> wrote:

Hi,

I saw. I will comment on your document inline today.

Best

Gilles Caulier

Le lun. 5 avr. 2021 à 00:08, Anjani Kumar <[hidden email]> a écrit :

Hello, I have submitted the first draft of the proposal. I am a bit late for submitting it. I would like to apologize for that.

Thanks

Anjani

On Apr 4 2021, at 3:44 pm, Anjani Kumar <[hidden email]> wrote:

Thanks. I'll soon submit a proposal.

Anjani

On Sun, Apr 4, 2021, 3:08 PM Gilles Caulier <[hidden email]> wrote:

ok,

After to trying to force Qt5 to use a 3rd party openssl precompiled as static, to second a lower version of system native openssl,

configure script refuse to prior newer version. this work only to link the same openssl version but compiled with different options. The headers must be the same.

We cannot mix different version of openssl at the same time.

Qt5 configure make really a puzzle. Welcome to cmake with Qt6...

So definitely, the only solution is to use a system based with openssl 1.1.1 to support Qt 5.15.x and Qt 6.x, so MGA 8.

Best

Gilles Caulier

Le sam. 3 avr. 2021 à 17:30, Gilles Caulier <[hidden email]> a écrit :

yes i seen . in fact since Qt 5.15.0, openssl 1.1.1 is required.

There is no choice to found a way to force Qt 5.15.2 to use the static openssl compiled version installed to /opt/openssl.

I don't understand why configure script do not acceopt /opt/openssl/include directory as header path.

Gilles Caulier

Le sam. 3 avr. 2021 à 16:41, Anjani Kumar <[hidden email]> a écrit :

It seems like Qt 5.15.1 is also failing to be configured. I also set the system installed openssl path but the errors are same :( 

On Apr 3 2021, at 5:45 pm, Gilles Caulier <[hidden email]> wrote:

The way to pass env var to Qt5 configure script is explained in helper doc :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3

Variables most be passed at end of .configure options, else it do not work.

MGA 7 provide openssl 1.1.0, not 1.1.1, as required to build Qt 5.15.2. this is why openssl is previously build as static library in /opt/openssl/ and env is passed to .configure script like this :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89

... but definitively, this doesn't work, certainly because .configure script from Qt is buggy :

Checking for OpenSSL...

Trying source 0 (type openssl) of library openssl ...

$OPENSSL_LIBS is not set.

  => source produced no result.

Trying source 1 (type inline) of library openssl ...

  => source failed condition 'config.win32'.

Trying source 2 (type inline) of library openssl ...

  => source failed condition 'config.msvc'.

Trying source 3 (type inline) of library openssl ...

  => source failed condition 'config.android'.

Trying source 4 (type inline) of library openssl ...

Include path \"/opt/openssl/include/\" is invalid.

  => source produced no result.

So :

1/ we cannot remove the system based openssl 1.1.0 as it used by plenty Qt5/KF5/DK dependencies to comple (aka mariabd, ffmpeg,opencv, etc.)

2/ to compile Qt 5.15.2, openssl 1.1.1 is required (too bad). So we need a extra static openssl only for qtbase.

3/ as .configure make a mess, and as i'm tired to waste my time with this archaic build system. I said stop.

4/ as Qt6 will be based on cmake and not qmake/configure

==> we will use Qt 5.15.1 under MGA7, as this version of Qt only require openssl 1.1.0.

And that all.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:57, Gilles Caulier <[hidden email]> a écrit :

I currently working on this port : MGA6 => MGA7

I am falling on the same dysfunction.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <[hidden email]> a écrit :

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Anjani Kumar]

Hello,

I have tried to resolve all the issues and suggestions in the proposal. There are a few things I would like to clear. 

• What to do with the rajce plugin?  I have proposed that the plugin's new implementation be written when the new api arrives which I don't find it on the website https://www.rajce.idnes.cz/api.
• Why is it necessary to include changes in classes for platforms macOS and Windows if this project focuses on the Linux port?  I have no issues in adding this. It is just that I am trying to understand why.
• I have made some changes to the timeline. Please point out any issues

Thanks

Anjani

On Apr 8 2021, at 6:20 pm, Anjani Kumar <[hidden email]> wrote:

I think qt6-deprecated-api-fixes option is the culprit though I'm not sure.

On Apr 8 2021, at 6:16 pm, Gilles Caulier <[hidden email]> wrote:

Hi,

I can reproduce the crash at around 35% of CLazy compilation.

It Sounds like one of the Qt6 checkers is buggy.

Try to re-run clazy with only with the first Qt6 option enabled to see if it passes. If yes, try again to activate the second, etc... The goal is to determine which option cannot be used.

Gilles Caulier

Le mer. 7 avr. 2021 à 17:17, Gilles Caulier <[hidden email]> a écrit :

You need to use the Clazy stable tag. the last one is v1.9.

The clang version used is important. Here i use 11.0.1

and finally, the check options for clazy to enable is important, as some options are under development and make the process unstable.

I recommend limiting multicore use. No need to overload the computer with plenty of concurrent memory allocation to compile codes. 12 cores is heavy. 4 or 6 is enough i think (here i use 3 cores only.

Gilles Caulier

Le mer. 7 avr. 2021 à 20:51, Anjani Kumar <[hidden email]> a écrit :

I am trying to run clazy.sh

Well it runs and then crashes midway on command "make -j12 2> reports.clazy/trace.log"

when i re-run this command again then build succeeds . I try to visualize it using clazy_visualize.sh and the report it generates contains only one warning type "qt6-qhash-signature"  but clearly in my log file, there are other warnings as well.  I guess this is caused by build failure in between and wrong report is generated.

I'm trying to debug it.

Thanks

Anjani

On Apr 7 2021, at 9:30 pm, Gilles Caulier <[hidden email]> wrote:

Look in Python script used to parse Clazy compilation trace and extract all relevant warnings based on turned on flag :

https://invent.kde.org/graphics/digikam/-/blob/master/project/reports/clazy_visualizer.py

Gilles Caulier

Le mer. 7 avr. 2021 à 17:08, Anjani Kumar <[hidden email]> a écrit :

Is there a good way extract/export only compiler warnings and errors to file? I can filter them out later from the output but is there a way to do this in a better way?

On Apr 5 2021, at 9:04 am, Gilles Caulier <[hidden email]> wrote:

Hi,

I saw. I will comment on your document inline today.

Best

Gilles Caulier

Le lun. 5 avr. 2021 à 00:08, Anjani Kumar <[hidden email]> a écrit :

Hello, I have submitted the first draft of the proposal. I am a bit late for submitting it. I would like to apologize for that.

Thanks

Anjani

On Apr 4 2021, at 3:44 pm, Anjani Kumar <[hidden email]> wrote:

Thanks. I'll soon submit a proposal.

Anjani

On Sun, Apr 4, 2021, 3:08 PM Gilles Caulier <[hidden email]> wrote:

ok,

After to trying to force Qt5 to use a 3rd party openssl precompiled as static, to second a lower version of system native openssl,

configure script refuse to prior newer version. this work only to link the same openssl version but compiled with different options. The headers must be the same.

We cannot mix different version of openssl at the same time.

Qt5 configure make really a puzzle. Welcome to cmake with Qt6...

So definitely, the only solution is to use a system based with openssl 1.1.1 to support Qt 5.15.x and Qt 6.x, so MGA 8.

Best

Gilles Caulier

Le sam. 3 avr. 2021 à 17:30, Gilles Caulier <[hidden email]> a écrit :

yes i seen . in fact since Qt 5.15.0, openssl 1.1.1 is required.

There is no choice to found a way to force Qt 5.15.2 to use the static openssl compiled version installed to /opt/openssl.

I don't understand why configure script do not acceopt /opt/openssl/include directory as header path.

Gilles Caulier

Le sam. 3 avr. 2021 à 16:41, Anjani Kumar <[hidden email]> a écrit :

It seems like Qt 5.15.1 is also failing to be configured. I also set the system installed openssl path but the errors are same :( 

On Apr 3 2021, at 5:45 pm, Gilles Caulier <[hidden email]> wrote:

The way to pass env var to Qt5 configure script is explained in helper doc :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3

Variables most be passed at end of .configure options, else it do not work.

MGA 7 provide openssl 1.1.0, not 1.1.1, as required to build Qt 5.15.2. this is why openssl is previously build as static library in /opt/openssl/ and env is passed to .configure script like this :

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89

... but definitively, this doesn't work, certainly because .configure script from Qt is buggy :

Checking for OpenSSL...

Trying source 0 (type openssl) of library openssl ...

$OPENSSL_LIBS is not set.

  => source produced no result.

Trying source 1 (type inline) of library openssl ...

  => source failed condition 'config.win32'.

Trying source 2 (type inline) of library openssl ...

  => source failed condition 'config.msvc'.

Trying source 3 (type inline) of library openssl ...

  => source failed condition 'config.android'.

Trying source 4 (type inline) of library openssl ...

Include path \"/opt/openssl/include/\" is invalid.

  => source produced no result.

So :

1/ we cannot remove the system based openssl 1.1.0 as it used by plenty Qt5/KF5/DK dependencies to comple (aka mariabd, ffmpeg,opencv, etc.)

2/ to compile Qt 5.15.2, openssl 1.1.1 is required (too bad). So we need a extra static openssl only for qtbase.

3/ as .configure make a mess, and as i'm tired to waste my time with this archaic build system. I said stop.

4/ as Qt6 will be based on cmake and not qmake/configure

==> we will use Qt 5.15.1 under MGA7, as this version of Qt only require openssl 1.1.0.

And that all.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:57, Gilles Caulier <[hidden email]> a écrit :

I currently working on this port : MGA6 => MGA7

I am falling on the same dysfunction.

Gilles Caulier

Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <[hidden email]> a écrit :

Hello, I am running a Mageia 7.1 instance and trying to run appimage scripts. The first script is failing in configuring Qt 5.15.  There are the things I have done

build ext_openssl, and Qt configuration step always fails with

ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed.

I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?

On Apr 3 2021, at 11:01 am, Gilles Caulier <[hidden email]> wrote:

Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <anjanik012@...> a écrit :

Is there a specific reason to upgrade to mageia 7.1 and not 8?  Qt 5.15 is available in the official repos for mageia 8 while for mageia 7.1 it is 5.12 and we would have to build Qt 5.15.

 

yes there is. the libc version to use when AppImage bundle contents is compiled must be an older version for binary compatibility with other Linux systems.

Currently Mageia6 is used. This OS has not been maintained since a while but the GCC version is enough recent to compile all Qt5, KF5, and DK codes.

This will be the same with Mageia7 which will become unmaintained in the near future to promote Mageia 8. This last one is too much recent to make a large compatible AppImage with all current Linux.

Gilles Caulier

[Gilles Caulier-4]

Le jeu. 8 avr. 2021 à 20:16, Anjani Kumar <[hidden email]> a écrit :

Hello,

I have tried to resolve all the issues and suggestions in the proposal. There are a few things I would like to clear. 

• What to do with the rajce plugin?  I have proposed that the plugin's new implementation be written when the new api arrives which I don't find it on the website https://www.rajce.idnes.cz/api.

Place Rajce in quarantine if code needs to be ported to a new talker because communication is broken due to changes in web service.

If web service continues to work with current implementation and if Qt6 port needs an extra Qt5 porting help classes propose a temporary solution.

• Why is it necessary to include changes in classes for platforms macOS and Windows if this project focuses on the Linux port?  I have no issues in adding this. It is just that I am trying to understand why.

Linux port to Qt6 is a prior. For the moment ignore MacOS and Windows OS, but if specificity for non Linux systems exists with Qt6 (as there are few differences with Qt5), well, list the points to take care for the future...

 

• I have made some changes to the timeline. Please point out any issues

All sounds fine to me, as I can see...

 

Thanks

Anjani

On Apr 8 2021, at 6:20 pm, Anjani Kumar <[hidden email]> wrote:

I think qt6-deprecated-api-fixes option is the culprit though I'm not sure.

On Apr 8 2021, at 6:16 pm, Gilles Caulier <[hidden email]> wrote:

Hi,

I can reproduce the crash at around 35% of CLazy compilation.

It Sounds like one of the Qt6 checkers is buggy.

Try to re-run clazy with only with the first Qt6 option enabled to see if it passes. If yes, try again to activate the second, etc... The goal is to determine which option cannot be used.

Gilles Caulier

qt6-qhash-signature generate 1218 warnings

https://www.digikam.org/reports/clazy/master/#

I remove all qt6 checks which includes -fix in name

Gilles Caulier

qt6-qhash-signature

qt6-qhash-signature