<div dir="ltr"><div>The way to pass env var to Qt5 configure script is explained in helper doc :</div><div><br></div><div><a href="https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3">https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/config_help-5.15.txt#L3</a></div><div><br></div><div>Variables most be passed at end of .configure options, else it do not work.</div><div><br></div><div>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 :</div><div><br></div><div><a href="https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89">https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_qt/5.15/CMakeLists.txt#L89</a></div><div><br></div><div>... but definitively, this doesn't work, certainly because .configure script from Qt is buggy :</div><div><br></div><div>Checking for OpenSSL... <br>Trying source 0 (type openssl) of library openssl ...<br>$OPENSSL_LIBS is not set.<br> => source produced no result.<br>Trying source 1 (type inline) of library openssl ...<br> => source failed condition 'config.win32'.<br>Trying source 2 (type inline) of library openssl ...<br> => source failed condition 'config.msvc'.<br>Trying source 3 (type inline) of library openssl ...<br> => source failed condition 'config.android'.<br>Trying source 4 (type inline) of library openssl ...<br>Include path \"/opt/openssl/include/\" is invalid.<br> => source produced no result.</div><div><br></div><div>So : <br></div><div><br></div><div>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.)</div><div>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.</div><div>3/ as .configure make a mess, and as i'm tired to waste my time with this archaic build system. I said stop.</div><div>4/ as Qt6 will be based on cmake and not qmake/configure</div><div><br></div><div>==> we will use Qt 5.15.1 under MGA7, as this version of Qt only require openssl 1.1.0. <br></div><div><br></div><div>And that all.</div><div><br></div><div>Gilles Caulier<br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le sam. 3 avr. 2021 à 12:57, Gilles Caulier <<a href="mailto:caulier.gilles@gmail.com">caulier.gilles@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>I currently working on this port : MGA6 => MGA7</div><div><br></div><div>I am falling on the same dysfunction.</div><div><br></div><div>Gilles Caulier<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le sam. 3 avr. 2021 à 12:23, Anjani Kumar <<a href="mailto:anjanik012@gmail.com" target="_blank">anjanik012@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>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</div><br><div>build ext_openssl, and Qt configuration step always fails with </div><br><div>ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed. </div><br><div>I have tried other ways to provide the path but it always fails with this msg. How to pass the path correctly?</div><br><div>On Apr 3 2021, at 11:01 am, Gilles Caulier <<a href="mailto:caulier.gilles@gmail.com" target="_blank">caulier.gilles@gmail.com</a>> wrote:</div><blockquote><div><div><div><br></div><br></div><div class="gmail_attr"><div>Le sam. 3 avr. 2021 à 06:37, Anjani Kumar <<a href="https://link.getmailspring.com/link/4FF348DD-66C7-4FAA-BC58-1CCE0E059A88@getmailspring.com/0?redirect=mailto%3Aanjanik012%40gmail.com&recipient=ZGlnaWthbS1kZXZlbEBrZGUub3Jn" title="mailto:anjanik012@gmail.com" target="_blank">anjanik012@gmail.com</a>> a écrit :</div></div><blockquote><div><div>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.</div></div></blockquote><div> </div><div><div>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.</div></div><div><br></div><div>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.</div><div>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.</div><div><br></div><div>Gilles Caulier</div></div></blockquote><img alt="Sent from Mailspring" style="border: 0px none; width: 0px; height: 0px;" width="0" height="0"></blockquote></div>
</blockquote></div>