Created attachment 133337 [details] analysis of startup process done by big sur After installing Big Sur (mac os 11.0) digikam does not start up. after klicking the icon digikam tries to launch but hangs in the process. no window or startup-screen is opened. a few seconds after launch SOFTWARE/OS VERSIONS macOS: 11.0 ADDITIONAL INFORMATION see below attachment
digiKam is currently compiled under Catalina and never tested on Big Sur. Gilles Caulier
*** Bug 429116 has been marked as a duplicate of this bug. ***
Thank´s for your fast response. As I´m no programmer (no more since 20 years) I cannot help very much (beside donning some money - as I already did when getting the app). If there is any way to get it earlier on working on big sur, i would be grateful to assist. MArtin
I just recompiled digiKam 7.2.0-beta2 PKG installer with last update of XCode with Big Sur support. Please take a look here : https://files.kde.org/digikam/ My MacBook Pro 2012 do not support Big Sur, so, i cannot test here... Gilles Caulier
hello Gilles, thanks for the new compiled version. I tryed your version of beta 2 on an Imac retina 2019 cpu 3.1Ghz i5, 24Go of ram and a Radeon pro 4Go, before osx big sur, all was well with beta1 but now it hangs, like Martin, no startup-screen, no windows, nothing, just "the application does not respond" i'm obliged to force to quit !! So the beta2 pkg didn't launch either. I do't know how to compile but i would like to try !
Created attachment 133363 [details] my stratup with commandline my startup with the command line found on the documentation part of the digikam website : Freezes and Other Run-Time Issues MacOS Host As under Linux, run the application from a terminal. digiKam executable is installed in /opt/digikam/Applications/KF5/digikam.app/Contents/MacOS/digikam. Just start it from the command line to view text traces. Note that you need to turn on before all debug traces from digiKam with QT_LOGGIN_RULES environment variable. export QT_LOGGING_RULES="digikam*=true" /opt/digikam/Applications/KF5/digikam.app/Contents/MacOS/digikam
I am new to both digikam and the KDE bug tracking system. I have the same problem as reported. I am not sure that I am downloading the recompiled version created by Gilles since it appears to have been created on Oct 30. The most current version for MacOS appears to be https://files.kde.org/digikam/digiKam-7.2.0-beta2-20201030T184354-MacOS-x86-64.pkg. Is this the correct recompiled package? Thanks Mark
Mark, Yes, it's the right version. Cristofoto, To recompile whole digiKam under MacOS, please read the instructions here : https://invent.kde.org/graphics/digikam/-/tree/master/project/bundles/macports Gilles Caulier
(In reply to caulier.gilles from comment #8) > Mark, > > Yes, it's the right version. > > Cristofoto, > > To recompile whole digiKam under MacOS, please read the instructions here : > > https://invent.kde.org/graphics/digikam/-/tree/master/project/bundles/ > macports > > Gilles Caulier Problem compiling, ---> Fetching distfiles for clang-3.4 Error: clang-3.4 is not supported on macOS Sierra or newer. Error: Failed to fetch clang-3.4: unsupported platform Error: See /opt/digikam/var/macports/logs/_opt_digikam_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_llvm-3.4/clang-3.4/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. Error: Processing of port clang-3.4 failed FAILED COMMAND: port install clang-3.4
Not reprocible here with MAcOS Catalina. which MacOS and Xcode version do you use exactly ? Gilles Caulier
(In reply to caulier.gilles from comment #10) > Not reprocible here with MAcOS Catalina. > > which MacOS and Xcode version do you use exactly ? > > Gilles Caulier bonsoir gilles, i use mac osx 11.0.1 ancd Xcode 12.2
Hum, try to comment line 224, 225, and 226 from this script : https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/macports/01-build-macports.sh#L224 Gilles
I can't do it, there are still errors, surely the method is not the right one, or the organization of folders and files, I'm missing a real step by step and I don't have the necessary knowledge, I think I'll leave the hand to someone who knows how to do it. Je n'y arrive pas, il y a encore des erreurs, surement la méthode n'est pas la bonne, ou l'organisation des dossiers et fichiers, il me manque un vrai pas à pas et je n'ai pas les connaissances nécessaires, je pense laisser la main à quelqu'un qui sait faire. >> copy from terminal screen >> ******* gawk has the following notes: readline support has been removed from gawk. If you need to run gawk interactively, install rlwrap: sudo port install rlwrap and run gawk using rlwrap: rlwrap gawk ... grep has the following notes: This port previously installed itself without a g* prefix, thus overshadowing system binaries such as grep, fgrep, and egrep. The port is now changed so that it does install with a g* prefix, like other GNU ports. This means that you'll now find GNU grep at /opt/digikam/bin/ggrep. If you dislike typing ggrep, you can create a shell alias or you can add /opt/digikam/libexec/gnubin to your PATH, wherein non-g* prefixed symlinks are installed. In other words, /opt/digikam/libexec/gnubin contains GNU binaries without any prefix to the file names, so you can type grep and get GNU grep just as before. libidn has the following notes: Please be aware that GNU libidn2 is the successor of GNU libidn. It comes with IDNA 2008 and TR46 implementations and also provides a compatibility layer for GNU libidn. libpsl has the following notes: libpsl API documentation is provided by the port 'libpsl-docs'. lzma has the following notes: The LZMA SDK program is installed as "lzma_alone", to avoid conflict with LZMA Utils py38-pygments has the following notes: To make the Python 3.8 version of Pygments the one that is run when you execute the commands without a version suffix, e.g. 'pygmentize', run: port select --set pygments py38-pygments python27 has the following notes: To make this the default Python or Python 2 (i.e., the version run by the 'python' or 'python2' commands), run one or both of: sudo port select --set python python27 sudo port select --set python2 python27 python38 has the following notes: To make this the default Python or Python 3 (i.e., the version run by the 'python' or 'python3' commands), run one or both of: sudo port select --set python python38 sudo port select --set python3 python38 FAILED COMMAND: port install ld64 +ld64_xcode subversion cmake libpng jpeg tiff boost eigen3 gettext libusb libgphoto2 jasper lcms2 expat libxml2 libxslt libical lensfun bison x265 ffmpeg qt5-qtbase qt5-qtdeclarative qt5-qtmacextras qt5-qtquickcontrols qt5-qtxmlpatterns qt5-qtsvg qt5-qttools qt5-qttranslations qt5-qtimageformats qt5-sqlite-plugin qt5-mysql-plugin wget +ssl ImageMagick
(In reply to Cristofoto from comment #13) > I can't do it, there are still errors, > surely the method is not the right one, or the organization of folders and > files, I'm missing a real step by step and I don't have the necessary > knowledge, I think I'll leave the hand to someone who knows how to do it. > > Je n'y arrive pas, il y a encore des erreurs, > surement la méthode n'est pas la bonne, ou l'organisation des dossiers et > fichiers, il me manque un vrai pas à pas et je n'ai pas les connaissances > nécessaires, je pense laisser la main à quelqu'un qui sait faire. > > >> copy from terminal screen > >> > ******* > gawk has the following notes: > readline support has been removed from gawk. If you need to run gawk > interactively, install rlwrap: > > sudo port install rlwrap > > and run gawk using rlwrap: > > rlwrap gawk ... > grep has the following notes: > This port previously installed itself without a g* prefix, thus > overshadowing system binaries such as grep, fgrep, and egrep. The port is > now changed so that it does install with a g* prefix, like other GNU ports. > This means that you'll now find GNU grep at /opt/digikam/bin/ggrep. If you > dislike typing ggrep, you can create a shell alias or you can add > /opt/digikam/libexec/gnubin to your PATH, wherein non-g* prefixed symlinks > are installed. In other words, /opt/digikam/libexec/gnubin contains GNU > binaries without any prefix to the file names, so you can type grep and get > GNU grep just as before. > libidn has the following notes: > Please be aware that GNU libidn2 is the successor of GNU libidn. It comes > with IDNA 2008 > and TR46 implementations and also provides a compatibility layer for GNU > libidn. > libpsl has the following notes: > libpsl API documentation is provided by the port 'libpsl-docs'. > lzma has the following notes: > The LZMA SDK program is installed as "lzma_alone", to avoid conflict with > LZMA Utils > py38-pygments has the following notes: > To make the Python 3.8 version of Pygments the one that is run when you > execute the commands without a version suffix, e.g. 'pygmentize', run: > > port select --set pygments py38-pygments > python27 has the following notes: > To make this the default Python or Python 2 (i.e., the version run by the > 'python' or 'python2' commands), run one or both of: > > sudo port select --set python python27 > sudo port select --set python2 python27 > python38 has the following notes: > To make this the default Python or Python 3 (i.e., the version run by the > 'python' or 'python3' commands), run one or both of: > > sudo port select --set python python38 > sudo port select --set python3 python38 > FAILED COMMAND: port install ld64 +ld64_xcode subversion cmake libpng jpeg > tiff boost eigen3 gettext libusb libgphoto2 jasper lcms2 expat libxml2 > libxslt libical lensfun bison x265 ffmpeg qt5-qtbase qt5-qtdeclarative > qt5-qtmacextras qt5-qtquickcontrols qt5-qtxmlpatterns qt5-qtsvg qt5-qttools > qt5-qttranslations qt5-qtimageformats qt5-sqlite-plugin qt5-mysql-plugin > wget +ssl ImageMagick Since Cristofoto is unable to continue, I would like to try and help. I have a MacBook Pro 2019 with VMware Fusion so my first steps was to create a new VM running macOS Catalina 10.15.7 with the current Xcode and follow the steps in https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/macports/README to make sure I am able to get a running application, then I would create a VM running Big Sur and try the same steps to build the application. Since I am new to developing on mac/linux/windows I have run into some confusion and problems following the steps in the README under 10.15.7. I am currently stuck on a problem building qt5-qtwebengine in script 01-build-macports-sh it is saying "Exeception: No 11.0+ SDK found". My question now is should I open a new bug related to trying to recompile under 10.15.7?
No new bug here. Remember that whole digiKAm dependencies as Qt5::WebEngine, are compiled and installed with Macports. If a dysfunction exists as this one, this must be reported to MAcports. But, by experience, Macports take time to support new main MacOS release. You need to be patient. This typically fully supported after few weeks. Gilles Caulier
As a note, regardless of any other Macport issues. Solid doesn't seem to find any more drives when I look at the startup log. And this problem could cause significantly more problems if the querying of hardware information has changed so drastically. There is currently almost no music program running on Big Sur and all manufacturers warn against an update to Big Sur. Maik
(In reply to Mark Christensen from comment #7) > I have the same problem as reported. I am not sure that I am downloading > the recompiled version created by Gilles since it appears to have been > created on Oct 30. The most current version for MacOS appears to be > https://files.kde.org/digikam/digiKam-7.2.0-beta2-20201030T184354-MacOS-x86- > 64.pkg. I'm having the same launch problems on macOS 11.0.1. I tried downloading this beta2 version but the problem persists.
(In reply to graeme.rubble from comment #17) > (In reply to Mark Christensen from comment #7) > > > I have the same problem as reported. I am not sure that I am downloading > > the recompiled version created by Gilles since it appears to have been > > created on Oct 30. The most current version for MacOS appears to be > > https://files.kde.org/digikam/digiKam-7.2.0-beta2-20201030T184354-MacOS-x86- > > 64.pkg. > > I'm having the same launch problems on macOS 11.0.1. > > I tried downloading this beta2 version but the problem persists. I believe the problem relates to issue 61103 on the MacPorts site. https://trac.macports.org/ticket/61103 see comment 60 (https://trac.macports.org/ticket/61103#comment:60) Mark
Hi all, Good news: i just book a new MacBook pro 2015 compatible with Big Sur to be able to build a digiKam version with the new MacOS. I don't book a recent version of the Macbook Pro for plenty of reasons, as it's very expensive and the touch-bar is really a pain to use to develop. Also the 2015 version is the last one where the SSD can be upgraded. This want mean that digiKam will continue to be packaged for future MacOS (Intel CPU only for the moment). Using Apple M1 arm CPU is too young and certainly it will introduce plenty of compatibility problems, even if an Intel emulation mode is provided by Apple. Supporting M1 will be planed for later, when hardware will be available and less expensive. So please, be patient. I will receive the new Macbook pro laptop in a few days. I will upgrade the computer with Big Sur and start to install all dependencies with Macports. This last stage can take a while by experience. When digiKam will be compiled under Big Sur, i plan a set of regression tests, which will take another long time to complete. For the moment, digiKam still compiled on my old MacBook pro 2012 (which work like a charm, i really like this computer). MacOS and XCode versions are the last one for this computer (Catalina 10.15.7 and XCode 11.5). I hope to be ready to provide a new digiKam Big sur compatible PKG for Christmas... Best Regards Gilles Caulier
Thank you very much for your committment to digigkam. one question: is it possible to direct some funds directly to you? (you are working for us, at least there should be some compensation) martin
Hi Martin, You can make donations through Paypal following instruction here: https://www.digikam.org/donate/ Thanks to support digiKam project Best regards Gilles Caulier
I recieve the new MacBook Pro mid 2015, installed BigSur and XCode, and start to patch code to compile with this MacOS version. For the moment, all progress well, please wait... Gilles Caulier
yess cool hope this work without problem !
Until now, Macports compile without problem since 1h30, with a least 200 packages already installed. We will see in few hours... Gilles Caulier
Some progress update: I lost my internet connection while tonight. Compile was stopped at QtWebEngine, the most huge part of digiKam dependencies to compile with Macports. I fixed the problem and compilation continue from now, and it will take age. I see Macports installing plenty of clang and gcc version to compile different ports under Big Sur. It's not optimum of course and it's certainly to be sure that ports compile fine until ends with this MacOS version. So we need to wait again a little bits. I hope to see a new PKG available for testing this evening. Gilles Caulier
Gilles Caulier <null@kde.org> 10:42 (il y a 0 minute) À kde-commits Traduire le message Désactiver pour : anglais Git commit 3e2c4f6264bee572be98aabc62e7f875d6b6342f by Gilles Caulier. Committed on 06/12/2020 at 09:40. Pushed by cgilles into branch 'master'. try to fix QtWebEngine under BigSur as wrong MacOS detection is performed with Qt 5.14.2 Details : https://bugreports.qt.io/browse/QTBUG-85546 M +1 -0 project/bundles/macports/01-build-macports.sh https://invent.kde.org/graphics/digikam/commit/3e2c4f6264bee572be98aabc62e7f875d6b6342f diff --git a/project/bundles/macports/01-build-macports.sh b/project/bundles/macports/01-build-macports.sh index c163d7fab9..193e15d976 100755 --- a/project/bundles/macports/01-build-macports.sh +++ b/project/bundles/macports/01-build-macports.sh @@ -265,6 +265,7 @@ port install \ ImageMagick if [[ $DK_QTWEBENGINE = 1 ]] ; then + export SYSTEM_VERSION_COMPAT=1 port install qt5-qtwebengine fi
Bad news... QtWebEngine 5.14.2 do not compile yet under BigSur. It detect the wrong Apple SDK version... Gilles Caulier
Git commit e83074a368c51504e9e82f232ed4f54be9e6af6c by Gilles Caulier. Committed on 06/12/2020 at 13:30. Pushed by cgilles into branch 'master'. MacOS BigSur support : Switch back from QtWebEngine to QtWebkit to fix temporally the broken compilation. QtWebKit 5.14.2 from MAcports do not support yet BigSur. This will probably fixed inthe future. M +6 -3 project/bundles/macports/01-build-macports.sh M +1 -1 project/bundles/macports/config.sh https://invent.kde.org/graphics/digikam/commit/e83074a368c51504e9e82f232ed4f54be9e6af6c
Git commit e396fae4584cfae0fe99d859cf863f4bb631489a by Gilles Caulier. Committed on 06/12/2020 at 16:09. Pushed by cgilles into branch 'master'. MacOS BigSur support: add patch to bild KF5.76 under Macports, where onlt Qt 5.14.2 is available for the moment. M +1 -1 project/bundles/3rdparty/ext_kf5_frameworks/CMakeLists.txt A +14 -0 project/bundles/3rdparty/ext_kf5_frameworks/kiconthemes-qt5.14.patch https://invent.kde.org/graphics/digikam/commit/e396fae4584cfae0fe99d859cf863f4bb631489a diff --git a/project/bundles/3rdparty/ext_kf5_frameworks/CMakeLists.txt b/project/bundles/3rdparty/ext_kf5_frameworks/CMakeLists.txt index db275d67b6..47483c2cbd 100755 --- a/project/bundles/3rdparty/ext_kf5_frameworks/CMakeLists.txt +++ b/project/bundles/3rdparty/ext_kf5_frameworks/CMakeLists.txt @@ -228,7 +228,7 @@ InstallKF5Component(kwidgetsaddons ${KF5_VERSION} "" InstallKF5Component(kitemviews ${KF5_VERSION} "" "") InstallKF5Component(kcompletion ${KF5_VERSION} "" "") InstallKF5Component(kconfigwidgets ${KF5_VERSION} "" "") -InstallKF5Component(kiconthemes ${KF5_VERSION} "" "") +InstallKF5Component(kiconthemes ${KF5_VERSION} "" "kiconthemes-qt5.14.patch") InstallKF5Component(kservice ${KF5_VERSION} "" "") InstallKF5Component(kglobalaccel ${KF5_VERSION} "" "") InstallKF5Component(kcalendarcore ${KF5_VERSION} "" "") diff --git a/project/bundles/3rdparty/ext_kf5_frameworks/kiconthemes-qt5.14.patch b/project/bundles/3rdparty/ext_kf5_frameworks/kiconthemes-qt5.14.patch new file mode 100644 index 0000000000..9ecd6b2d46 --- /dev/null +++ b/project/bundles/3rdparty/ext_kf5_frameworks/kiconthemes-qt5.14.patch @@ -0,0 +1,14 @@ +diff --git a/src/tools/ksvg2icns/ksvg2icns.cpp b/src/tools/ksvg2icns/ksvg2icns.cpp +index 08a7805..b217f84 100644 +--- a/src/tools/ksvg2icns/ksvg2icns.cpp ++++ b/src/tools/ksvg2icns/ksvg2icns.cpp +@@ -35,7 +35,9 @@ static bool writeImage(QSvgRenderer &svg, int size, const QString &outFile1, con + out.fill(Qt::transparent); + + QPainter painter(&out); ++#if (QT_VERSION >= QT_VERSION_CHECK(5, 15, 0)) + svg.setAspectRatioMode(Qt::KeepAspectRatio); ++#endif + svg.render(&painter); + painter.end(); +
Git commit 8c33718ee8c6335d15cfd894fbec51dfd0161795 by Gilles Caulier. Committed on 05/12/2020 at 05:54. Pushed by cgilles into branch 'master'. fix detection of MacOS BigSur and fix Clang install failure due to wrong major version tested M +1 -1 project/bundles/macports/01-build-macports.sh M +48 -32 project/bundles/macports/common.sh https://invent.kde.org/graphics/digikam/commit/8c33718ee8c6335d15cfd894fbec51dfd0161795 diff --git a/project/bundles/macports/01-build-macports.sh b/project/bundles/macports/01-build-macports.sh index 75dd1fb5d6..c163d7fab9 100755 --- a/project/bundles/macports/01-build-macports.sh +++ b/project/bundles/macports/01-build-macports.sh @@ -218,7 +218,7 @@ echo "---------- Building digiKam dependencies with Macports" # With OSX less than El Capitan, we need a more recent Clang compiler than one provided by XCode. -if [[ $MAJOR_OSX_VERSION -lt 10 ]]; then +if [[ $MAJOR_OSX_VERSION -lt 11 && $MINOR_OSX_VERSION -lt 10 ]]; then echo "---------- Install more recent Clang compiler from Macports for specific ports" port install clang_select diff --git a/project/bundles/macports/common.sh b/project/bundles/macports/common.sh index c4b4fc2b91..fc283d824b 100755 --- a/project/bundles/macports/common.sh +++ b/project/bundles/macports/common.sh @@ -110,44 +110,60 @@ echo "Elaspsed time for script execution : $(($difftimelps / 3600 )) hours $((($ ######################################################################## # Set strings with detected MacOS info : -# $MAJOR_OSX_VERSION : detected MacOS major ID (as 7 for 10.7 or 10 for 10.10) +# $MAJOR_OSX_VERSION : detected MacOS major ID (as 10 or 11) +# $MINOR_OSX_VERSION : detected MacOS minor ID (as 7 for 10.7 or 10 for 10.10) # $OSX_CODE_NAME : detected MacOS code name OsxCodeName() { -MAJOR_OSX_VERSION=$(sw_vers -productVersion | awk -F '.' '{print $1 "." $2}'| cut -d . -f 2) - -if [[ $MAJOR_OSX_VERSION == "13" ]] - then OSX_CODE_NAME="HighSierra" -elif [[ $MAJOR_OSX_VERSION == "12" ]] - then OSX_CODE_NAME="Sierra" -elif [[ $MAJOR_OSX_VERSION == "11" ]] - then OSX_CODE_NAME="ElCapitan" -elif [[ $MAJOR_OSX_VERSION == "10" ]] - then OSX_CODE_NAME="Yosemite" -elif [[ $MAJOR_OSX_VERSION == "9" ]] - then OSX_CODE_NAME="Mavericks" -elif [[ $MAJOR_OSX_VERSION == "8" ]] - then OSX_CODE_NAME="MountainLion" -elif [[ $MAJOR_OSX_VERSION == "7" ]] - then OSX_CODE_NAME="Lion" -elif [[ $MAJOR_OSX_VERSION == "6" ]] - then OSX_CODE_NAME="SnowLeopard" -elif [[ $MAJOR_OSX_VERSION == "5" ]] - then OSX_CODE_NAME="Leopard" -elif [[ $MAJOR_OSX_VERSION == "4" ]] - then OSX_CODE_NAME="Tiger" -elif [[ $MAJOR_OSX_VERSION == "3" ]] - then OSX_CODE_NAME="Panther" -elif [[ $MAJOR_OSX_VERSION == "2" ]] - then OSX_CODE_NAME="Jaguar" -elif [[ $MAJOR_OSX_VERSION == "1" ]] - then OSX_CODE_NAME="Puma" -elif [[ $MAJOR_OSX_VERSION == "0" ]] - then OSX_CODE_NAME="Cheetah" +MAJOR_OSX_VERSION=$(sw_vers -productVersion | awk -F '.' '{print $1 "." $2}'| cut -d . -f 1) +MINOR_OSX_VERSION=$(sw_vers -productVersion | awk -F '.' '{print $1 "." $2}'| cut -d . -f 2) + +if [[ $MAJOR_OSX_VERSION == "10" ]] ; then + + if [[ $MAJOR_OSX_VERSION == "16" ]] + then OSX_CODE_NAME="Catalina" + elif [[ $MAJOR_OSX_VERSION == "14" ]] + then OSX_CODE_NAME="Mojave" + elif [[ $MAJOR_OSX_VERSION == "13" ]] + then OSX_CODE_NAME="HighSierra" + elif [[ $MAJOR_OSX_VERSION == "12" ]] + then OSX_CODE_NAME="Sierra" + elif [[ $MAJOR_OSX_VERSION == "11" ]] + then OSX_CODE_NAME="ElCapitan" + elif [[ $MAJOR_OSX_VERSION == "10" ]] + then OSX_CODE_NAME="Yosemite" + elif [[ $MAJOR_OSX_VERSION == "9" ]] + then OSX_CODE_NAME="Mavericks" + elif [[ $MAJOR_OSX_VERSION == "8" ]] + then OSX_CODE_NAME="MountainLion" + elif [[ $MAJOR_OSX_VERSION == "7" ]] + then OSX_CODE_NAME="Lion" + elif [[ $MAJOR_OSX_VERSION == "6" ]] + then OSX_CODE_NAME="SnowLeopard" + elif [[ $MAJOR_OSX_VERSION == "5" ]] + then OSX_CODE_NAME="Leopard" + elif [[ $MAJOR_OSX_VERSION == "4" ]] + then OSX_CODE_NAME="Tiger" + elif [[ $MAJOR_OSX_VERSION == "3" ]] + then OSX_CODE_NAME="Panther" + elif [[ $MAJOR_OSX_VERSION == "2" ]] + then OSX_CODE_NAME="Jaguar" + elif [[ $MAJOR_OSX_VERSION == "1" ]] + then OSX_CODE_NAME="Puma" + elif [[ $MAJOR_OSX_VERSION == "0" ]] + then OSX_CODE_NAME="Cheetah" + fi + +elif [[ $MAJOR_OSX_VERSION == "11" ]] ; then + + if [[ $MAJOR_OSX_VERSION == "0" ]] + then OSX_CODE_NAME="BigSur" + fi + fi -echo -e "---------- Detected OSX version 10.$MAJOR_OSX_VERSION and code name $OSX_CODE_NAME" +echo -e "---------- Detected OSX version $MAJOR_OSX_VERSION.$MINOR_OSX_VERSION and code name $OSX_CODE_NAME" }
Git commit 6928a9436cf4665655e27242133804285992190a by Gilles Caulier. Committed on 05/12/2020 at 06:02. Pushed by cgilles into branch 'master'. Fix Major and Minor detection for the target MacOS and linking with libc++ M +3 -2 project/bundles/macports/common.sh https://invent.kde.org/graphics/digikam/commit/6928a9436cf4665655e27242133804285992190a diff --git a/project/bundles/macports/common.sh b/project/bundles/macports/common.sh index fc283d824b..2e722ccc5c 100755 --- a/project/bundles/macports/common.sh +++ b/project/bundles/macports/common.sh @@ -36,9 +36,10 @@ fi export MACOSX_DEPLOYMENT_TARGET=$OSX_MIN_TARGET -OSX_MAJOR=`echo $MACOSX_DEPLOYMENT_TARGET | awk -F '.' '{print $1 "." $2}'| cut -d . -f 2` +MACOS_MAJOR=`echo $MACOSX_DEPLOYMENT_TARGET | awk -F '.' '{print $1 "." $2}'| cut -d . -f 1` +MACOS_MINOR=`echo $MACOSX_DEPLOYMENT_TARGET | awk -F '.' '{print $1 "." $2}'| cut -d . -f 2` -if [[ $OSX_MAJOR -lt 9 ]]; then +if [[ $MACOS_MAJOR -lt 11 && $MACOS_MINOR -lt 9 ]]; then export CXXFLAGS=-stdlib=libc++ fi
Git commit 24bb77174c27bb09c04cc3c56fde385b69115ac9 by Gilles Caulier. Committed on 05/12/2020 at 06:05. Pushed by cgilles into branch 'master'. Add BigSur on list of supported Qt version M +1 -0 project/bundles/macports/config.sh https://invent.kde.org/graphics/digikam/commit/24bb77174c27bb09c04cc3c56fde385b69115ac9 diff --git a/project/bundles/macports/config.sh b/project/bundles/macports/config.sh index 75f708c538..ba3e14c5f5 100644 --- a/project/bundles/macports/config.sh +++ b/project/bundles/macports/config.sh @@ -26,6 +26,7 @@ BUILDING_DIR="`pwd`/temp.build" # sudo /usr/libexec/PlistBuddy -c "Set MinimumSDKVersion 10.13" /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Info.plist # # Possible values: +# 11.0 : BigSur : : Qt 5.12, 5.13, 5.14, 5.15 # 10.15 : Catalina : : Qt 5.11, 5.12, 5.13, 5.14 # 10.14 : Mojave : tested : Qt 5.9, 5.10, 5.11, 5.12, 5.13, 5.14 # 10.13 : High Sierra : tested : Qt 5.9, 5.10, 5.11, 5.12, 5.13, 5.14
Removing subscriber per abuse reports we've received.
Git commit feb7d64f31e8476816b64b702748614d8b74be75 by Gilles Caulier. Committed on 05/12/2020 at 13:14. Pushed by cgilles into branch 'master'. BigSur support: bump KF5 and KApp to last stable release M +3 -3 project/bundles/3rdparty/ext_kf5_frameworks/CMakeLists.txt M +1 -1 project/bundles/3rdparty/ext_libksane/CMakeLists.txt M +1 -1 project/bundles/3rdparty/ext_marble/CMakeLists.txt https://invent.kde.org/graphics/digikam/commit/feb7d64f31e8476816b64b702748614d8b74be75 diff --git a/project/bundles/3rdparty/ext_kf5_frameworks/CMakeLists.txt b/project/bundles/3rdparty/ext_kf5_frameworks/CMakeLists.txt index 44b478936e..db275d67b6 100755 --- a/project/bundles/3rdparty/ext_kf5_frameworks/CMakeLists.txt +++ b/project/bundles/3rdparty/ext_kf5_frameworks/CMakeLists.txt @@ -198,11 +198,11 @@ function(InstallKF5Component endfunction() if(MINGW) - set(KF5_VERSION 5.74) # we have Qt 5.14.2 available. + set(KF5_VERSION 5.76) # we have Qt 5.14.2 available. elseif(APPLE) - set(KF5_VERSION 5.74) # we have Qt 5.14.1 available. + set(KF5_VERSION 5.76) # we have Qt 5.14.1 available. else() - set(KF5_VERSION 5.74) # we have Qt 5.14.2 available. + set(KF5_VERSION 5.76) # we have Qt 5.14.2 available. endif() if(APPLE) diff --git a/project/bundles/3rdparty/ext_libksane/CMakeLists.txt b/project/bundles/3rdparty/ext_libksane/CMakeLists.txt index e349cb3678..e85c2a5cb7 100755 --- a/project/bundles/3rdparty/ext_libksane/CMakeLists.txt +++ b/project/bundles/3rdparty/ext_libksane/CMakeLists.txt @@ -7,7 +7,7 @@ # set(EXTPREFIX_libksane "${EXTPREFIX}" ) -set(KA_VERSION 20.08.1) +set(KA_VERSION 20.08.3) GetKF5ApplicationMd5Sums(libksane ${KA_VERSION}) diff --git a/project/bundles/3rdparty/ext_marble/CMakeLists.txt b/project/bundles/3rdparty/ext_marble/CMakeLists.txt index f8f28a2abf..74d123df30 100755 --- a/project/bundles/3rdparty/ext_marble/CMakeLists.txt +++ b/project/bundles/3rdparty/ext_marble/CMakeLists.txt @@ -7,7 +7,7 @@ # set(EXTPREFIX_marble "${EXTPREFIX}" ) -set(KA_VERSION 20.08.1) +set(KA_VERSION 20.08.3) GetKF5ApplicationMd5Sums(marble ${KA_VERSION})
Voilà, at least all dependencies including KF5 libraries are now compiled under BigSur. Of course we use now QtWebKit instead QtWebEngine, but it's a temporary solution. We have few weeks before the digiKam 7.2.0 final release. I'm waiting a fix from Macports about this problem. Gilles Caulier
Now digiKam is compiling, please wait few minutes... Gilles Caulier
Fine! :-) I am new. I have an iMac with the Big sur version and I would try Digikam for the first time. So I am waiting for your new version to test it.
(In reply to caulier.gilles from comment #36) > Now digiKam is compiling, please wait few minutes... > > Gilles Caulier Merci gilles pour ton travail acharné. il me tarde de pouvoir tester ce build de digikam sur BigSur. Thank you Gilles for your hard work. I'm looking forward to test this digikam build on BigSur
Git commit d193f8888dda5c3ca1474103f357e512a427bb12 by Gilles Caulier. Committed on 06/12/2020 at 21:46. Pushed by cgilles into branch 'master'. BigSur support: fix webengine option to configure digiKam M +2 -3 project/bundles/macports/03-build-digikam.sh https://invent.kde.org/graphics/digikam/commit/d193f8888dda5c3ca1474103f357e512a427bb12
Hi all, A first PKG version of digiKam working on BigSur arrive. I'm testing currently : https://i.imgur.com/LztlOvt.png Gilles Caulier
(In reply to caulier.gilles from comment #40) > Hi all, > > A first PKG version of digiKam working on BigSur arrive. I'm testing > currently : > > https://i.imgur.com/LztlOvt.png > > Gilles Caulier youppi !!
Git commit 7b07d68618e2bc285398ad249a7ee17ebe012f69 by Gilles Caulier. Committed on 07/12/2020 at 05:43. Pushed by cgilles into branch 'master'. BigSur support: do not generate exception if system lib is not found M +2 -2 project/bundles/macports/rll.py https://invent.kde.org/graphics/digikam/commit/7b07d68618e2bc285398ad249a7ee17ebe012f69
Hi all, A first PKG version compiled under BigSur of digiKam 7.2.0 beta2 will be available in one hour at usual place: https://files.kde.org/digikam/ Currently i recompile digiKam code. I tried a pre version this morning and it start and run without problem. Of course, as usual under MacOS : 1/ to install a PKG from developers not signed in Apple, you need to tune installer right in MacOS control panel. For the question about to register developers on Apple infrastructure, i respond : I never paid 99 USD per year for an open source project. Apple know really the open source world which try to support this operating system, and the time passed to hack, develop, and support Mac platform ? For me it me be the opposite: Apple must paid open source developer for that... 2/ When digiKam start, BigSur ask to front user if you want to give access to your photo library (if you setup one root digiKam collection at this place). Of course, it save to respond yes. I recommend to place database in another place of course. 3/ This PKG version for BigSur is compiled (temporally) with QtWebKit. It's an older version of the Qt Web browser interface based on WebKit (Safari like browser). QtWebKit is outdated, and new QtWebEngine component must be used instead. This last one is a switch to Chromium web Browser and include all recent security fixes. This is not the case of QtWebKit. So take a care when you try to share items on the cloud. The Qt web browser component is used for that. For the rest to show GoogleMaps in geolocation view, i think it safe to use. I will report the dysfunction on Macports project to compile QtWebEngine under BigSur. I'm suprised to not see a UPSTREAM report, as all the Qt5 components compile fine (else digiKam will not here). You must know that QtWebEngine is just a giant part to compile. It take some hours with the compiler... 4/ Face Engine data file models downloading: At startup, digiKam ask to download from digikam.org web site extra large files to run face detection and recognition. It's new to 7.2.0, as these files was included in digiKam installer before. We separate these files now as the bundles become heavy more and more. There is an error while downloading file as digiKam report the url as not secure. Files are not processed and digiKam just said that new download will run at next startup... but it fail too. It's a bug that we need to fix. So it will be clear that Face workflow will not work yet. Be patient please, we will solve one problem step y step... Voilà, for the rest, all feedback will help to finalize this port under MacOS. Remember that 2 PKG version will be available to download: one with debug symbols, one other without debug symbol. The first one is larger to be able to catch a debugger back-trace if digiKam crash. Of course you must install Apple XCode for that. Best regards Gilles Caulier
Ah, i forget to ask something: The new PKG installer compatible with BigSur is compiled with a backward compatibility. It must run fine under Catalina, Mojave, and HighSierra. Older versions are not supported due to lack of compatibility from Qt 5.14.2 used to compile digiKam. The only solution to support older MAcOS versions can be to compile with an older Qt version, which include plenty of bugs under MacOS, so we will never do that. Sorry... So if somebody can check if the new PKG run fine at least under Catalina, Mojave, and HighSierra, it will be great. Thanks in advance Gilles Caulier
To point 4. The files are downloaded from files.kde.org. However, it is forwarded to a random mirror. I think BigSur checks the URL internally. Of course we check the download with a SHA256 checksum. I think we need a server that BigSur trusts. Unfortunately the KDE admins do not want the files hosted on our website. Maik
Git commit 742fcfe06bf2245d42b8060e88f312689dad4709 by Maik Qualmann. Committed on 07/12/2020 at 18:54. Pushed by mqualmann into branch 'master'. for a test we ignore SSL errors M +3 -0 core/utilities/setup/downloader/filesdownloader.cpp https://invent.kde.org/graphics/digikam/commit/742fcfe06bf2245d42b8060e88f312689dad4709
hello, where could i find the pkg, i don't see it on https://files.kde.org/digikam/ i could test it on HighSierra because my wife's mac is runnin HighSierra and couldn't upgrade anymore. And my mac is on BigSur thanks
Hi, 2 PKG are now avaialble at usual place (one with debug symbols, one without): https://files.kde.org/digikam/ Both are now compiled under BigSur. Thanks for your feedbacks Gilles Caulier
I just tested the version you published, it works as intended on Big Sur. I understand that we cannot download facerecognition binary within Digikam, but since they are available on https://files.kde.org/digikam/, where do I need to put them ? I tried to move the files to /Users/TinyTableshelf/Library/Application Support/digikam/facesengine, but Digikam cannot find them.
Hi, thank you Gilles for the very fast working solution. Downloading the face recognition parets does not work. shapepredictor.dat is repeatedly downloaded but not stored at al, so the download restarts again and again. putting th efile into the mentioned folder does not work. any manual workaround to install the files? thanks in advance Martin In spite of that the app seems to work without problems have to do some tests.
@TinyTableshelf, do I understand correctly that trying to download the same file again within one session? If so, it just won't be found. In MacOS, this is related to differences between the data path and the generic data path and we can easily fix it. Maik
@Maik Qualmann yes, I tried to download manually the facesengine files, but I could not get Digikam to work with them, no matter in which folder I put them.
hi, at least according to the progress bar the download completes 100%. but then it restarts again and again and the file isn´t found in the mentioned (by the dialog-window)folder. martin (In reply to Maik Qualmann from comment #51) > @TinyTableshelf, do I understand correctly that trying to download the same > file again within one session? If so, it just won't be found. In MacOS, this > is related to differences between the data path and the generic data path > and we can easily fix it. > > Maik
Ok, the file (shapepredictor.dat) was then saved for sure. Please take a look where it was stored and post the path that is displayed in the download window. Maik
Git commit 34c846a62ad19a4da091444caf6ef2549e397a3f by Maik Qualmann. Committed on 08/12/2020 at 17:22. Pushed by mqualmann into branch 'master'. show the same path in the window as is used to save M +2 -4 core/utilities/setup/downloader/filesdownloader.cpp https://invent.kde.org/graphics/digikam/commit/34c846a62ad19a4da091444caf6ef2549e397a3f
/Users/myname/Library/Application Support/digikam/facesengine (In reply to Maik Qualmann from comment #54) > Ok, the file (shapepredictor.dat) was then saved for sure. Please take a > look where it was stored and post the path that is displayed in the download > window. > > Maik
Created attachment 133935 [details] download dialog dest dowbload dialog
to be more accurate: file was stored in /Users/myname/Library/Application Support/digikam/facesengine according to download dialog window should be stored in /opt/digikam/Applications/KF5Ä/ .... (see attachment) martin (In reply to Martin Neuß from comment #56) > /Users/myname/Library/Application Support/digikam/facesengine > > (In reply to Maik Qualmann from comment #54) > > Ok, the file (shapepredictor.dat) was then saved for sure. Please take a > > look where it was stored and post the path that is displayed in the download > > window. > > > > Maik
As for me, dialog said it was saved to /Users/myname/Library/Application Support/digikam/digikam whereas is was actually saved to /Users/myname/Library/Application Support/digikam/facesengine
Ok, the path to save is correct: /Users/myname/Library/Application Support/digikam/facesengine But the search path is not correct under MacOS and is also different from what is written in the Qt Doc. Maik
For info, i tested the PKG under Catalina, and it work: https://i.imgur.com/51B532Q.png Gilles Caulier
Git commit 81b6de000a686e44532de918013afb58c7614521 by Maik Qualmann. Committed on 08/12/2020 at 21:55. Pushed by mqualmann into branch 'master'. move from deprecated QStandardPaths::DataLocation to QStandardPaths::AppDataLocation This moves the files under Windows to the desired roaming directory M +2 -1 core/app/main/digikamapp.cpp M +2 -2 core/app/main/main.cpp M +1 -1 core/dplugins/generic/tools/mediaserver/server/dmediaservermngr.cpp M +2 -4 core/libs/dimg/filters/redeye/redeyecorrectionfilter.cpp M +4 -4 core/libs/facesengine/detection/opencv-dnn/dnnfacedetectorssd.cpp M +4 -4 core/libs/facesengine/detection/opencv-dnn/dnnfacedetectoryolo.cpp M +2 -2 core/libs/facesengine/preprocessing/recognition/openfacepreprocessor.cpp M +6 -6 core/libs/facesengine/recognition/opencv-dnn/dnnfaceextractor.cpp M +1 -1 core/libs/template/templatemanager.cpp M +2 -2 core/libs/widgets/mainview/dxmlguiwindow.cpp M +2 -2 core/showfoto/main/main.cpp M +1 -1 core/tests/mediaserver/dmediaserver_test.cpp M +2 -2 core/utilities/firstrun/migratefromdigikam4page.cpp M +1 -1 core/utilities/geolocation/geoiface/bookmark/gpsbookmarkowner.cpp M +1 -1 core/utilities/queuemanager/manager/workflowmanager.cpp M +4 -5 core/utilities/setup/downloader/filesdownloader.cpp https://invent.kde.org/graphics/digikam/commit/81b6de000a686e44532de918013afb58c7614521
@Gilles, you have an insecure redirection connection. There still seem to be mirrors on HTTP, I'll fix it. Maik
Git commit b4108688fe5398efe6bd82e658eb6b73818103bf by Maik Qualmann. Committed on 08/12/2020 at 22:15. Pushed by mqualmann into branch 'master'. use HTTP for download M +1 -1 core/utilities/setup/downloader/filesdownloader.cpp https://invent.kde.org/graphics/digikam/commit/b4108688fe5398efe6bd82e658eb6b73818103bf
We need a new PKG for MacOS ((:-)) Maik
Note: MAcports UPSTREAM tickets about QtWebEngine and BigSur support is here: https://trac.macports.org/ticket/61786 Gilles Caulier
Hi all, New PKG are online now with last changes from git/master codes... Gilles Caulier
Hi, thanks for that great and quick support. I can run digikam on Big Sur but it takes very log. It hangs on "checking ICC repository..."for approx one minute. Is this normal? Thanks!
The option in the collection setting to monitor the albums for external changes is (hopefully) deactivated? Maik
this was the problem, it starts up very fast now, perfect! Thanks!
some feedback about MAcports team progress: Qt5.15.2 will be prublished as main UPSTREAM release in a near future. 5.15.1 do not compile well under BigSur. Last tests are under progress, but it 's long as Macports team check for regression for backward compatibilty with older MacOS release. Last Qt 6.0 just released can not be considerated. It's more like a proof of concept as plenty of features for Qt5.x still missing. Later releases will be certainly packaged when code will be mature. So, i hope to see QtWebEngine supported well with BigSur. As MAcports team said, this huge component is just a big pain to maintain... Gilles Caulier
Hi Gilles, as reporter of this bug I really want to thank you and all the other who made this app possible for your work and your commitment. I´ve already donated and hope that all the ones who profit from your work do their share to support it. Martin Now back to using and testing digikam. (In reply to caulier.gilles from comment #71) > some feedback about MAcports team progress: > > Qt5.15.2 will be prublished as main UPSTREAM release in a near future. > 5.15.1 do not compile well under BigSur. Last tests are under progress, but > it 's long as Macports team check for regression for backward compatibilty > with older MacOS release. > > Last Qt 6.0 just released can not be considerated. It's more like a proof of > concept as plenty of features for Qt5.x still missing. Later releases will > be certainly packaged when code will be mature. > > So, i hope to see QtWebEngine supported well with BigSur. As MAcports team > said, this huge component is just a big pain to maintain... > > Gilles Caulier
Hello, big thank you to Gilles who made a great job. The pkg of 20201210 run very well on my iMac BigSur, It runs also well on my wife's iMac High-Sierra (just not localised in french, i don't know why because it's the same pkg) I see the work made, so I will donate uin the next days.
Hi, Thanks to all for your support. It very appreciate... The github thread about next Qt 5.15.2 integration in Macports progress well. I hope to be able to test it before Christmas. https://github.com/macports/macports-ports/pull/8744# In parallel, i upgraded my new MacBook Pro with a 2Tb SSD, and i reinstall all from scratch. Next stage is to support install relocation of PKG. Code is already here since a while but it do not work yet. I don't find free time to hack, and a new Mac is the good stage to work on this topic. To resume, the relocation will permit to install digiKam outside the /opt/digikam/, so in another external disk for example. Voilà, the plan is to have a clean/safe Mac installer for 7.2.0. another plan for the future is the auto-detection of devices as sd-card and camera. This is a tedious topic as it touch KF5:Solid API, not digiKam code as well... Gilles Caulier
(In reply to Cristofoto from comment #73) > Hello, big thank you to Gilles who made a great job. > > The pkg of 20201210 run very well on my iMac BigSur, > It runs also well on my wife's iMac High-Sierra (just not localised in > french, i don't know why because it's the same pkg) > > I see the work made, so I will donate uin the next days. auto reply, all is good, switched to english restart, switched to french, restart and all is now in french.
yes, to switch from one language to another one, it's the way under Linux, Mac, Windows... Normaly a dialog must be shown to details the operation to complete the switch. Best Gilles Caulier
Ok here screenshots from my imac BigSur running Digikam 7.2.0 beta2 https://s1.imghub.io/arjBm.png and another from my wife's mac HighSierra with Digikam 7.2.0 beta 2 too. https://s1.imghub.io/ar4bS.png
Git commit 8d8ad5c36ec80a9205a9709f442a03f54b79ad07 by Gilles Caulier. Committed on 13/12/2020 at 09:13. Pushed by cgilles into branch 'master'. bump KF5 from 5.76 to last 5.77 stable release Related: bug 429116 M +3 -3 project/bundles/3rdparty/ext_kf5_frameworks/CMakeLists.txt https://invent.kde.org/graphics/digikam/commit/8d8ad5c36ec80a9205a9709f442a03f54b79ad07
Git commit bb2cd9608d757810e218b47010942ae0456a7a4d by Gilles Caulier. Committed on 13/12/2020 at 09:35. Pushed by cgilles into branch 'master'. Another patch to build KF5.77 under Macports as Wayland do not exists under MacOS. M +2 -1 project/bundles/3rdparty/ext_kf5_frameworks/CMakeLists.txt A +13 -0 project/bundles/3rdparty/ext_kf5_frameworks/kguiaddons-macports.patch https://invent.kde.org/graphics/digikam/commit/bb2cd9608d757810e218b47010942ae0456a7a4d
Git commit f03750d90e4effbfa390a6455378fb4990da8ba3 by Gilles Caulier. Committed on 13/12/2020 at 09:49. Pushed by cgilles into branch 'dev'. Add MacOS limitaion for the Apple PKG installer (high Sierra, BigSur, Apple Silicon, Rosetta2). M +2 -1 content/download/binary.md https://invent.kde.org/websites/digikam-org/commit/f03750d90e4effbfa390a6455378fb4990da8ba3
A new version of the pre release 7.2.0 PKG installer is under finalization after a recompilation from scratch (it take 23 hours to compile!) This version include last KDE frameworks 5.77 just released one day ago. https://kde.org/announcements/kde-frameworks-5.77.0/ The most important part here is Solid which deal with devices detection as SD-card, Camera, Disk UUID for database, etc. Of course other part of KF5 are used in digiKam, but not too much, as we work a lots to reduce the dependency level with this framework. Another part which still used a lots is KXMLGui to manage main application windows. This version include last changes commited in digiKam source code of course. All feeback will be welcome. Best Gilles Caulier
IMPORTANT: If somebody has the chance to buy the last MAC computer based on Apple Silicon M1 (a very impressive CPU), it will be interresting to see if Apple Rosetta 2 emulator will be able to install and run digiKam 7.2.0 properly. A native Apple Silicon version will be planed later, when Macports support fully this architecture, and when will be able to have a Apple Silicon Computer to compile and test digiKam... Thanks in advance for your feedback. Gilles Caulier
Git commit 02f4c12c0a098604230872514081cadb9a5aad6e by Gilles Caulier. Committed on 13/12/2020 at 11:20. Pushed by cgilles into branch 'master'. Fix broken compilation user MacOS BigSur. Optimize install to only process dplugin. M +1 -1 project/bundles/3rdparty/ext_exiv2/CMakeLists.txt M +4 -0 project/bundles/3rdparty/ext_mosaicwall/CMakeLists.txt https://invent.kde.org/graphics/digikam/commit/02f4c12c0a098604230872514081cadb9a5aad6e
I tried the latest build (12/13/2020) and I was not able to start the digikam. The error message is "dyld: Library not loaded: /opt/digikam/lib/libKF5Service.5.dylib Referenced from: /opt/digikam/bin/kbuildsycoca5 Reason: image not found" I checked my /opt/digikam/lib and there is no libKF5Service.5.dylib I did have this problem for the previous build 2 or 3 days ago. Thanks, Joseph (In reply to caulier.gilles from comment #81) > A new version of the pre release 7.2.0 PKG installer is under finalization > after a recompilation from scratch (it take 23 hours to compile!) > > This version include last KDE frameworks 5.77 just released one day ago. > > https://kde.org/announcements/kde-frameworks-5.77.0/ > > The most important part here is Solid which deal with devices detection as > SD-card, Camera, Disk UUID for database, etc. > > Of course other part of KF5 are used in digiKam, but not too much, as we > work a lots to reduce the dependency level with this framework. Another part > which still used a lots is KXMLGui to manage main application windows. > > This version include last changes commited in digiKam source code of course. > > All feeback will be welcome. > > Best > > Gilles Caulier
Sorry, typo. I did NOT have this problem for the previous build 2 or 3 days ago. (In reply to Joseph Chang from comment #84) > I did have this problem for the previous build 2 or 3 days ago.
Hum strange the KF5 Service shared library is well compiled and available. Sound like a dependencies parsing stage is missing for the kbuildsycoca5 tool. I will check that Gilles Caulier
Et voilà, all that i hate with Macports. One llvm CLI tool is broken but updated in main stream. As i re-installed all from scratch since i upgraded th internal SSD from 500Gb to 2Tb, macports install last llvm, and at end we got an exception. Result: the bundle is do not include all target dependencies: digiKam version: 7.2.0-beta2 Check Packages CLI tool passed... ---------- Removing temporary packaging directory /Users/gilles/Devel/7.x/project/bundles/macports//opt/digikam Creating /Users/gilles/Devel/7.x/project/bundles/macports//opt/digikam ---------- Preparing Applications for MacOS digikam Found digikam in /Applications/KF5 Creating /Users/gilles/Devel/7.x/project/bundles/macports//opt/digikam/Applications/KF5 Copying digikam Creating launcher script for digikam Found icon for digikam launcher showfoto Found showfoto in /Applications/KF5 Copying showfoto Creating launcher script for showfoto Found icon for showfoto launcher ---------- Collecting dependencies for applications, binaries, and libraries: Traceback (most recent call last): File "/Users/gilles/Devel/7.x/project/bundles/macports/rll.py", line 186, in <module> deplist = deplist + embed_dependencies(dep) File "/Users/gilles/Devel/7.x/project/bundles/macports/rll.py", line 125, in embed_dependencies todo = dependencies(binary) File "/Users/gilles/Devel/7.x/project/bundles/macports/rll.py", line 94, in dependencies l = otool(binary) File "/Users/gilles/Devel/7.x/project/bundles/macports/rll.py", line 79, in otool raise Exception(stderr.readline().strip()) Exception: llvm-objdump: Unknown command line argument '-macho'. Try: '/opt/digikam/libexec/llvm-11/bin/llvm-objdump --help' Creating /Users/gilles/Devel/7.x/project/bundles/macports//opt/digikam/Parsing dependencies from binary Applications/KF5/digikam.app/Contents/MacOS Parsing dependencies from binary Applications/KF5/digikam.app/Contents/MacOS/digikam The bug is know: https://reviews.llvm.org/D92310?id= Gilles Caulier
Git commit 2696426197b2a82d0455fd452708aaa7f8448022 by Gilles Caulier. Committed on 13/12/2020 at 22:44. Pushed by cgilles into branch 'master'. Do not force PATH env.var to include macports install path while reccursive library depedencies collecting M +2 -2 project/bundles/macports/04-build-installer.sh https://invent.kde.org/graphics/digikam/commit/2696426197b2a82d0455fd452708aaa7f8448022
7.2.0 beta2 PKG files are now recompiled with relevant fixes to be usable. https://files.kde.org/digikam/ Please let's me here if all is fine now. Gilles Caulier
Maik, Look well the size of no-debug and debug PKG files digiKam-7.2.0-beta2-20201213T231914-MacOS-x86-64.pkg => 210.3 MB (220464851 bytes) digiKam-7.2.0-beta2-20201213T233053-MacOS-x86-64-debug.pkg => 223.4 MB (234239694 bytes) The difference is not to much high. Typically, digiKam + Showfoto + Exiv2 + all dplugins are compiled with debug symbols. All the rest do not include debug symbols. To compare, Linux versions are : digikam-7.2.0-beta2-20201210T103829-x86-64.appimage => 296.2 MB (310628392 bytes) digikam-7.2.0-beta2-20201210T104206-x86-64-debug.appimage =>607.4 MB (636870696 bytes) .. and Windows : digiKam-7.2.0-beta2-20201214T063937-Win64.exe => 101.1 MB (105992505 bytes) digiKam-7.2.0-beta2-20201214T065629-Win64-debug.exe => 321.4 MB (337013785 bytes) Typically, i expect to see a double size at least between both versions. So why MacOS files difference is small ? Note the code to cleanup debug symbols is located here: https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/macports/04-build-installer.sh#L450 Gilles
(In reply to caulier.gilles from comment #89) > 7.2.0 beta2 PKG files are now recompiled with relevant fixes to be usable. > > https://files.kde.org/digikam/ > > Please let's me here if all is fine now. > > Gilles Caulier Gilles, I was able to successfully open and use the beta2 PKG on Big Sur. Thanks!!
@Gilles, Google says this: https://forum.juce.com/t/symbol-stripping-on-osx-any-luck/8653 https://stackoverflow.com/questions/4236525/cant-strip-all-unneeded-symbols-on-a-mac-os-x-c-application Maik
(In reply to tzellman from comment #91) > (In reply to caulier.gilles from comment #89) > > 7.2.0 beta2 PKG files are now recompiled with relevant fixes to be usable. > > > > https://files.kde.org/digikam/ > > > > Please let's me here if all is fine now. > > > > Gilles Caulier > > Gilles, > > I was able to successfully open and use the beta2 PKG on Big Sur. Thanks!! Me too, Thanks Gilles
Git commit 9541292038a5b7fd1bf97c8a07d48020b6891783 by Gilles Caulier. Committed on 15/12/2020 at 09:24. Pushed by cgilles into branch 'master'. More files stripped with debug symbols CCBUGS:429103 M +1 -2 project/bundles/macports/04-build-installer.sh https://invent.kde.org/graphics/digikam/commit/9541292038a5b7fd1bf97c8a07d48020b6891783 diff --git a/project/bundles/macports/04-build-installer.sh b/project/bundles/macports/04-build-installer.sh index 6332277930..66c0519022 100755 --- a/project/bundles/macports/04-build-installer.sh +++ b/project/bundles/macports/04-build-installer.sh @@ -455,8 +455,7 @@ if [[ $DK_DEBUG = 1 ]] ; then find $TEMPROOT -name "*.so" | grep -Ev '(digikam|showfoto|exiv2)' | xargs strip -SXx find $TEMPROOT -name "*.dylib" | grep -Ev '(digikam|showfoto|exiv2)' | xargs strip -SXx else - find $TEMPROOT -name "*.so" | xargs strip -SXx - find $TEMPROOT -name "*.dylib" | xargs strip -SXx + find $TEMPROOT -perm +111 -type f | xargs strip -SXx 2>/dev/null fi if [[ $DK_DEBUG = 1 ]] ; then
@Gilles, I think it's not the debug symbols that make the package bigger. I unpacked the PKG, it contains many additional data files, e.g. Test tables from MariaDB, OpenCV haar-cascades files or all header files from Qt (70MB). Maik
Maik, The there are some data files to drop for the PKG to reduce the size, it's on my TODO list. But the main problem is the inverse: I'm sure that debug PKG version do not have debug symbols in fact. The size of PKG must the double if debug symbols are there, and it's not the case. Remember the old bugs reported under MacOS where backtraces only include assembly code. I think digiKam and plugins are not compiled with right options to include debug information in target binaries. The cmake setting is right as we use Debug option : https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/macports/03-build-digikam.sh#L134 ... passed to : https://invent.kde.org/graphics/digikam/-/blob/master/bootstrap.macports#L9 ... to setup cmake with -DCMAKE_BUILD_TYPE=Debug So here i'm lost. I suspect a compiler option forced by KF5::ECM script in backgroud which disable debug symbols. Gilles
Gilles Caulier <null@kde.org> 07:05 (il y a 0 minute) À kde-commits Traduire le message Désactiver pour : anglais Git commit 9068f28fdc4ccfe75b1f74bbbe9de13d86aafa95 by Gilles Caulier. Committed on 16/12/2020 at 06:05. Pushed by cgilles into branch 'master'. Check if Xcode SDK target minimal version is installed and patch Xcode backward binary compatibility automatically in settings M +12 -1 project/bundles/macports/common.sh M +1 -1 project/bundles/macports/config.sh https://invent.kde.org/graphics/digikam/commit/9068f28fdc4ccfe75b1f74bbbe9de13d86aafa95 diff --git a/project/bundles/macports/common.sh b/project/bundles/macports/common.sh index 4ed6612ce6..be785e3e66 100755 --- a/project/bundles/macports/common.sh +++ b/project/bundles/macports/common.sh @@ -38,6 +38,7 @@ else fi export MACOSX_DEPLOYMENT_TARGET=$OSX_MIN_TARGET +echo "Target OSX minimal version: $MACOSX_DEPLOYMENT_TARGET" MACOS_MAJOR=`echo $MACOSX_DEPLOYMENT_TARGET | awk -F '.' '{print $1 "." $2}'| cut -d . -f 1` MACOS_MINOR=`echo $MACOSX_DEPLOYMENT_TARGET | awk -F '.' '{print $1 "." $2}'| cut -d . -f 2` @@ -46,7 +47,17 @@ if [[ $MACOS_MAJOR -lt 11 && $MACOS_MINOR -lt 9 ]]; then export CXXFLAGS=-stdlib=libc++ fi -echo "Target OSX minimal version: $MACOSX_DEPLOYMENT_TARGET" +if [[ ! -f /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX$MACOS_MAJOR.$MACOS_MINOR.sdk ]] ; then + echo "XCode Target SDK minimal version is not installled in /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs" + echo "you can donwload an archive of SDK from https://github.com/phracker/MacOSX-SDKs/releases" + exit 1 +else + echo "Check XCode Target SDK minimal version passed..." +fi + +# Adjust the property "MinimumSDKVersion" from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Info.plist +/usr/libexec/PlistBuddy -c "Set MinimumSDKVersion $MACOS_MAJOR.$MACOS_MINOR" /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Info.plist + } ######################################################################## diff --git a/project/bundles/macports/config.sh b/project/bundles/macports/config.sh index 44dc9443b4..b627e626b5 100644 --- a/project/bundles/macports/config.sh +++ b/project/bundles/macports/config.sh @@ -62,7 +62,7 @@ DK_URL="http://download.kde.org/stable/digikam" DK_BUILDTEMP=~/dktemp # digiKam tag version from git. Official tarball do not include extra shared libraries. -# The list of tags can be listed with this url: https://quickgit.kde.org/?p=digikam.git&a=tags +# The list of tags can be listed with this url: https://invent.kde.org/graphics/digikam/-/tags # If you want to package current implementation from git, use "master" as tag. #DK_VERSION=v7.2.0-beta1 DK_VERSION=master
This morning, i restarted a whole Macport install from scratch, as Macports team has enabled Qt 5.15.2 officially as main Qt version to install by default. Until now all compile fine. All core Qt is installed. I near to compiled the famous Qtwebengine monster, which still the most problematic part (Chromium code take many hours to compile here). If all pass fine, i will close this reports. BigSur will be fully supported with backward binary regression to High Sierra. Later i will continue to improve PKG construction. We have other entries in bugzilla where pending tasks wait since a while to be fixed: https://bugs.kde.org/show_bug.cgi?id=396766 https://bugs.kde.org/show_bug.cgi?id=407236 https://bugs.kde.org/show_bug.cgi?id=426860 I would also to work on new version notification to end user, with the possibility to update application semi automatically. Depending of new students availability and skill, I will try to delegate this kind of implementation in January/February for next Goggle Summer of Code 2021 candidates. https://bugs.kde.org/show_bug.cgi?id=426997 Voilà. I will report here when new Qt5.15.2 version based PKG will be complete and ready to download for testing... Best regards Gilles Caulier
(In reply to caulier.gilles from comment #82) > IMPORTANT: > > If somebody has the chance to buy the last MAC computer based on Apple > Silicon M1 (a very impressive CPU), it will be interresting to see if Apple > Rosetta 2 emulator will be able to install and run digiKam 7.2.0 properly. > > A native Apple Silicon version will be planed later, when Macports support > fully this architecture, and when will be able to have a Apple Silicon > Computer to compile and test digiKam... > > Thanks in advance for your feedback. > > Gilles Caulier Hi Gilles, I was able to install, start and use digiKam on my Mac mini (M1) without problems with the latest beta release (14. Dec). Only some tasks like opening and switching between some HEIF images in preview mode is a little bit slow. Henrik
Git commit 8950f8eec298b4b0574c3d522409803e2a790aa3 by Gilles Caulier. Committed on 18/12/2020 at 04:25. Pushed by cgilles into branch 'master'. On Bigsur we need to switch cctools with xcode variant option to prevent broken compilation with objdump with activating QtWebEngine Problem is know and there are plenty of packages broken. See this report for exemple: https://trac.macports.org/ticket/61852 M +1 -0 project/bundles/macports/01-build-macports.sh M +1 -1 project/bundles/macports/config.sh https://invent.kde.org/graphics/digikam/commit/8950f8eec298b4b0574c3d522409803e2a790aa3
Maik, debug symbols un MacoOS are not include in target binay as under Linux, but in departe files, as explained here : https://stackoverflow.com/questions/51621742/what-is-in-the-target-dsym-directories-created-by-cmake-with-the-makefile-gene So with cmake, we must obtain something like .dSYM generated by -DCMAKE_BUILD_TYPE=Debug option, but it's not the case... Gilles
Hi all, Good news. I completed to compile and install last Qt 5.15.2, including QtWebEngine under BigSur with HighSierra backward compatibility. KF5 framework compile fine too, and now digiKam compilation started. The way to use QtWebEngine instead the old QtWebkit will increase the security and the compatibility when digiKAm use web services. A new PKG version will be ready in few hours at usual place of course. Gilles Caulier
Hi all, New 7.2.0-beta2 PKG is available for testing at usual place: https://files.kde.org/digikam/ This version use now last Qt 5.15.2 and go back to QtWebEngine. Thanks for your feedback. Gilles Caulier
Maik, I investigate the debug symbols problematic under MacOS. We compile digiKam using clang/G++ from Macports, not XCode directly. XCode is only used by Macports to compile all background Unix libraries. Only XCode can generate the Dsym directory at compilation. Debug Symbols under MacOS are not include in target binary, but as separated files. It's optional. This is why strip CLI tool do not reduce a lots the bundle size: there is no debugs to remove, or a very small parts in shared libraries. This is why too, when we run digiKam in XCode debugger, we only seen assembly codes. I configure digiKam with cmake to target XCode build system, not Unix makefiles. After that, i compiled digiKam with xcodebuild CLI tool and all is built fine. Debug symbols are there. XCode propose also plenty of CLI tool to bundle and relocate binary files. I must investigate this way for the future. I will close this file now as for me the BigSur support is now fixed. I will continue to improve MacOS support with other files from bugzilla. Gilles
Git commit 5a75bf569ff1a2304713ccdee6b7c7642db347df by Gilles Caulier. Committed on 19/12/2020 at 18:09. Pushed by cgilles into branch 'master'. Finaly i found a way to generate debug symbols for MacOS with CMake without to use XCode. Cmake do not support yet this kind of rules. See this reports for details: https://gitlab.kitware.com/cmake/cmake/-/issues/20256 M +20 -0 core/CMakeLists.txt https://invent.kde.org/graphics/digikam/commit/5a75bf569ff1a2304713ccdee6b7c7642db347df