I have assembled two digikam 4.9.0 binary packages for OS X, including external MySQL database support. They were made using bash/python scripts to build it from MacPorts in a a virtual machine. One was built with a +debug variant, the other isn't. I've seen regular requests for OS X binary packages on the web page and this list, as well as complaints about the length/complexity/reliability of building digikam with MacPorts. So I figure I should share -- if you would like to test them, email me directly and I'll send you a link. I'm not posting links to the list for two reasons. First, I don't want someone to just grab and install binary packages, expecting a stable, official digikam release, instead of a risky bastardized derivation that I've cobbled together. I'm not a coder. This is my first crack at packaging a MacOS application. The build/package scripts include "rm -rf" but not error checking. My testing has been limited to opening digikam and showfoto, looking through my photos, and some photo manipulations. Some photographs I rotated using my digikam 4.0.0 package were corrupted -- I don't know if that was due to my packaging. Anyone who is testing the packages or scripts should be very cautious -- back up the photos and the computer it's running on, test it in a VM, etc.. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Hello,
good work. I guess we can but your packaging scripts on the git, since we also have different bootstrap stripts for different linux distribution. Having them on the git, somebody else can pick them up and improve, if needed. Veaceslav On Thu, Apr 16, 2015 at 8:51 PM, Account, Listserv <[hidden email]> wrote: > I have assembled two digikam 4.9.0 binary packages for OS X, including > external MySQL database support. They were made using bash/python scripts to > build it from MacPorts in a a virtual machine. One was built with a +debug > variant, the other isn't. > > I've seen regular requests for OS X binary packages on the web page and this > list, as well as complaints about the length/complexity/reliability of > building digikam with MacPorts. So I figure I should share -- if you would > like to test them, email me directly and I'll send you a link. > > I'm not posting links to the list for two reasons. First, I don't want > someone to just grab and install binary packages, expecting a stable, > official digikam release, instead of a risky bastardized derivation that > I've cobbled together. I'm not a coder. This is my first crack at packaging > a MacOS application. The build/package scripts include "rm -rf" but not > error checking. My testing has been limited to opening digikam and > showfoto, looking through my photos, and some photo manipulations. Some > photographs I rotated using my digikam 4.0.0 package were corrupted -- I > don't know if that was due to my packaging. Anyone who is testing the > packages or scripts should be very cautious -- back up the photos and the > computer it's running on, test it in a VM, etc.. > > Second, I don't think I'll have time to properly support OS X binary > releases. From what I can tell, properly scripting this build and package > process would have been be simple for someone who knows what they're doing. > Due obligations and lack of skill, it's taken me over a year of intermittent > work to make my clumsy scripts. I likely won't have time or skill to fix > problems. If you notice something's not right (e.g. why won't the packaged > versions use Aqua widgets?) you'll have to investigate and fix it yourself > (then share the answer hopefully). > > All that said, email me off-list if you understand my cautions and are > interested in testing -- and improving upon -- what I've put together. > > Shanti > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Shanti,
thanks to share your experience. I would to know more your your bin packaging workflow under OSX. I use MacBook pro here, so, if your host your script in digiKam git repository, i will able to build bin package for next version Your script must be documented. A text file is enough to host with script. We need to know all dependencies, settings, OSX-XCode-macports version to use, etc... Q : how did you solve KDE run time dependency with you package. For ex, digiKam still to use KIO-Slave. How did you package it ? Gilles Caulier 2015-04-16 21:12 GMT+02:00 Veaceslav Munteanu <[hidden email]>: > Hello, > > good work. > > I guess we can but your packaging scripts on the git, since we also > have different bootstrap stripts for different linux distribution. > > Having them on the git, somebody else can pick them up and improve, if needed. > > Veaceslav > > On Thu, Apr 16, 2015 at 8:51 PM, Account, Listserv > <[hidden email]> wrote: >> I have assembled two digikam 4.9.0 binary packages for OS X, including >> external MySQL database support. They were made using bash/python scripts to >> build it from MacPorts in a a virtual machine. One was built with a +debug >> variant, the other isn't. >> >> I've seen regular requests for OS X binary packages on the web page and this >> list, as well as complaints about the length/complexity/reliability of >> building digikam with MacPorts. So I figure I should share -- if you would >> like to test them, email me directly and I'll send you a link. >> >> I'm not posting links to the list for two reasons. First, I don't want >> someone to just grab and install binary packages, expecting a stable, >> official digikam release, instead of a risky bastardized derivation that >> I've cobbled together. I'm not a coder. This is my first crack at packaging >> a MacOS application. The build/package scripts include "rm -rf" but not >> error checking. My testing has been limited to opening digikam and >> showfoto, looking through my photos, and some photo manipulations. Some >> photographs I rotated using my digikam 4.0.0 package were corrupted -- I >> don't know if that was due to my packaging. Anyone who is testing the >> packages or scripts should be very cautious -- back up the photos and the >> computer it's running on, test it in a VM, etc.. >> >> Second, I don't think I'll have time to properly support OS X binary >> releases. From what I can tell, properly scripting this build and package >> process would have been be simple for someone who knows what they're doing. >> Due obligations and lack of skill, it's taken me over a year of intermittent >> work to make my clumsy scripts. I likely won't have time or skill to fix >> problems. If you notice something's not right (e.g. why won't the packaged >> versions use Aqua widgets?) you'll have to investigate and fix it yourself >> (then share the answer hopefully). >> >> All that said, email me off-list if you understand my cautions and are >> interested in testing -- and improving upon -- what I've put together. >> >> Shanti >> >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users >> > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Gilles and Veaceslav -- First, I appreciate your years of work on the digikam project. Thank you. I sent you links to download the scripts, after adding some comments. Hopefully those and the readme will provide enough explanation to be comprehensible. I don't mind if you put them on the git repository if that would be useful, but I suggest they should be sanity-checked by someone who knows what they're doing first. In response to Gilles' question: The packaging script uses a staging directory to hold files actually needed to run digikam and the other applications. I made a list through trial and error, of libraries, configuration files, icons, etc. which otool couldn't identify but which should be included. These include the runtime libraries, or at least the ones whose absence caused a problem that I noticed (e.g. the qtmysql library). I manually added them to the list files to be run through the dependency lister and copied to the package. I presume that manually listing files for inclusion will cause the script or finished packages to break whenever the runtime dependencies change. But I'm not aware of any automated way to prepare that list. Please let me know if you have questions. On Thu, Apr 16, 2015 at 3:29 PM, Gilles Caulier <[hidden email]> wrote: Shanti, _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
I too would like to thank Gilles and Veachslav and everyone that has
ever worked on digiKam. I have been using it since 2007 and except
for a couple of unstable versions, it's positively the BEST photo
management program ever written.
I manage almost a million photos in digiKam. I have a dual Xeon 8 core computer running Debian and 16MB RAM. I hope one day digiKam can take advantage of all those cores. There's nothing out there that comes close to the capabilities of digiKam. Thank you all. Keep up the great work. Jeff Account, Listserv wrote:
-- "Everything you've ever wanted is on the other side of fear." -George Addair _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by S Kulkarni
Shanti,
I will review your scripts and packaging rules after 4.10.0 planned next week. I'm also busy with lessons writing in my office. I must complete it in few days. After that, i will update macports install on my Macbook pro, and i will try to build digiKam DMG using your scripts. I'm sure that questions will come. Best Gilles Caulier 2015-04-17 6:18 GMT+02:00 Account, Listserv <[hidden email]>: > Gilles and Veaceslav -- First, I appreciate your years of work on the > digikam project. Thank you. > > In response to Gilles' question: The packaging script uses a staging > directory to hold files actually needed to run digikam and the other > applications. I made a list through trial and error, of libraries, > configuration files, icons, etc. which otool couldn't identify but which > should be included. These include the runtime libraries, or at least the > ones whose absence caused a problem that I noticed (e.g. the qtmysql > library). I manually added them to the list files to be run through the > dependency lister and copied to the package. > > I presume that manually listing files for inclusion will cause the script or > finished packages to break whenever the runtime dependencies change. But I'm > not aware of any automated way to prepare that list. > > I sent you links to download the scripts, after adding some comments. > Hopefully those and the readme will provide enough explanation to be > comprehensible. I don't mind if you put them on the git repository if that > would be useful, but I suggest they should be sanity-checked by someone who > knows what they're doing first. > > Please let me know if you have questions. > > Shanti > > On Thu, Apr 16, 2015 at 3:29 PM, Gilles Caulier <[hidden email]> > wrote: >> >> Shanti, >> >> thanks to share your experience. >> >> I would to know more your your bin packaging workflow under OSX. I use >> MacBook pro here, so, if your host your script in digiKam git >> repository, i will able to build bin package for next version >> >> Your script must be documented. A text file is enough to host with >> script. We need to know all dependencies, settings, OSX-XCode-macports >> version to use, etc... >> >> Q : how did you solve KDE run time dependency with you package. For >> ex, digiKam still to use KIO-Slave. How did you package it ? >> >> Gilles Caulier >> >> 2015-04-16 21:12 GMT+02:00 Veaceslav Munteanu >> <[hidden email]>: >> > Hello, >> > >> > good work. >> > >> > I guess we can but your packaging scripts on the git, since we also >> > have different bootstrap stripts for different linux distribution. >> > >> > Having them on the git, somebody else can pick them up and improve, if >> > needed. >> > >> > Veaceslav >> > >> > On Thu, Apr 16, 2015 at 8:51 PM, Account, Listserv >> > <[hidden email]> wrote: >> >> I have assembled two digikam 4.9.0 binary packages for OS X, including >> >> external MySQL database support. They were made using bash/python >> >> scripts to >> >> build it from MacPorts in a a virtual machine. One was built with a >> >> +debug >> >> variant, the other isn't. >> >> >> >> I've seen regular requests for OS X binary packages on the web page and >> >> this >> >> list, as well as complaints about the length/complexity/reliability of >> >> building digikam with MacPorts. So I figure I should share -- if you >> >> would >> >> like to test them, email me directly and I'll send you a link. >> >> >> >> I'm not posting links to the list for two reasons. First, I don't want >> >> someone to just grab and install binary packages, expecting a stable, >> >> official digikam release, instead of a risky bastardized derivation >> >> that >> >> I've cobbled together. I'm not a coder. This is my first crack at >> >> packaging >> >> a MacOS application. The build/package scripts include "rm -rf" but not >> >> error checking. My testing has been limited to opening digikam and >> >> showfoto, looking through my photos, and some photo manipulations. >> >> Some >> >> photographs I rotated using my digikam 4.0.0 package were corrupted -- >> >> I >> >> don't know if that was due to my packaging. Anyone who is testing the >> >> packages or scripts should be very cautious -- back up the photos and >> >> the >> >> computer it's running on, test it in a VM, etc.. >> >> >> >> Second, I don't think I'll have time to properly support OS X binary >> >> releases. From what I can tell, properly scripting this build and >> >> package >> >> process would have been be simple for someone who knows what they're >> >> doing. >> >> Due obligations and lack of skill, it's taken me over a year of >> >> intermittent >> >> work to make my clumsy scripts. I likely won't have time or skill to >> >> fix >> >> problems. If you notice something's not right (e.g. why won't the >> >> packaged >> >> versions use Aqua widgets?) you'll have to investigate and fix it >> >> yourself >> >> (then share the answer hopefully). >> >> >> >> All that said, email me off-list if you understand my cautions and are >> >> interested in testing -- and improving upon -- what I've put together. >> >> >> >> Shanti >> >> >> >> _______________________________________________ >> >> Digikam-users mailing list >> >> [hidden email] >> >> https://mail.kde.org/mailman/listinfo/digikam-users >> >> >> > _______________________________________________ >> > Digikam-users mailing list >> > [hidden email] >> > https://mail.kde.org/mailman/listinfo/digikam-users >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users > > > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Shanti,
It will be appreciate to attach your DMG build scripts to this bugzilla entry : https://bugs.kde.org/show_bug.cgi?id=257679 Thanks in advance Gilles Caulier 2015-05-04 13:04 GMT+02:00 Gilles Caulier <[hidden email]>: > Shanti, > > I will review your scripts and packaging rules after 4.10.0 planned > next week. I'm also busy with lessons writing in my office. I must > complete it in few days. > > After that, i will update macports install on my Macbook pro, and i > will try to build digiKam DMG using your scripts. I'm sure that > questions will come. > > Best > > Gilles Caulier > > 2015-04-17 6:18 GMT+02:00 Account, Listserv <[hidden email]>: >> Gilles and Veaceslav -- First, I appreciate your years of work on the >> digikam project. Thank you. >> >> In response to Gilles' question: The packaging script uses a staging >> directory to hold files actually needed to run digikam and the other >> applications. I made a list through trial and error, of libraries, >> configuration files, icons, etc. which otool couldn't identify but which >> should be included. These include the runtime libraries, or at least the >> ones whose absence caused a problem that I noticed (e.g. the qtmysql >> library). I manually added them to the list files to be run through the >> dependency lister and copied to the package. >> >> I presume that manually listing files for inclusion will cause the script or >> finished packages to break whenever the runtime dependencies change. But I'm >> not aware of any automated way to prepare that list. >> >> I sent you links to download the scripts, after adding some comments. >> Hopefully those and the readme will provide enough explanation to be >> comprehensible. I don't mind if you put them on the git repository if that >> would be useful, but I suggest they should be sanity-checked by someone who >> knows what they're doing first. >> >> Please let me know if you have questions. >> >> Shanti >> >> On Thu, Apr 16, 2015 at 3:29 PM, Gilles Caulier <[hidden email]> >> wrote: >>> >>> Shanti, >>> >>> thanks to share your experience. >>> >>> I would to know more your your bin packaging workflow under OSX. I use >>> MacBook pro here, so, if your host your script in digiKam git >>> repository, i will able to build bin package for next version >>> >>> Your script must be documented. A text file is enough to host with >>> script. We need to know all dependencies, settings, OSX-XCode-macports >>> version to use, etc... >>> >>> Q : how did you solve KDE run time dependency with you package. For >>> ex, digiKam still to use KIO-Slave. How did you package it ? >>> >>> Gilles Caulier >>> >>> 2015-04-16 21:12 GMT+02:00 Veaceslav Munteanu >>> <[hidden email]>: >>> > Hello, >>> > >>> > good work. >>> > >>> > I guess we can but your packaging scripts on the git, since we also >>> > have different bootstrap stripts for different linux distribution. >>> > >>> > Having them on the git, somebody else can pick them up and improve, if >>> > needed. >>> > >>> > Veaceslav >>> > >>> > On Thu, Apr 16, 2015 at 8:51 PM, Account, Listserv >>> > <[hidden email]> wrote: >>> >> I have assembled two digikam 4.9.0 binary packages for OS X, including >>> >> external MySQL database support. They were made using bash/python >>> >> scripts to >>> >> build it from MacPorts in a a virtual machine. One was built with a >>> >> +debug >>> >> variant, the other isn't. >>> >> >>> >> I've seen regular requests for OS X binary packages on the web page and >>> >> this >>> >> list, as well as complaints about the length/complexity/reliability of >>> >> building digikam with MacPorts. So I figure I should share -- if you >>> >> would >>> >> like to test them, email me directly and I'll send you a link. >>> >> >>> >> I'm not posting links to the list for two reasons. First, I don't want >>> >> someone to just grab and install binary packages, expecting a stable, >>> >> official digikam release, instead of a risky bastardized derivation >>> >> that >>> >> I've cobbled together. I'm not a coder. This is my first crack at >>> >> packaging >>> >> a MacOS application. The build/package scripts include "rm -rf" but not >>> >> error checking. My testing has been limited to opening digikam and >>> >> showfoto, looking through my photos, and some photo manipulations. >>> >> Some >>> >> photographs I rotated using my digikam 4.0.0 package were corrupted -- >>> >> I >>> >> don't know if that was due to my packaging. Anyone who is testing the >>> >> packages or scripts should be very cautious -- back up the photos and >>> >> the >>> >> computer it's running on, test it in a VM, etc.. >>> >> >>> >> Second, I don't think I'll have time to properly support OS X binary >>> >> releases. From what I can tell, properly scripting this build and >>> >> package >>> >> process would have been be simple for someone who knows what they're >>> >> doing. >>> >> Due obligations and lack of skill, it's taken me over a year of >>> >> intermittent >>> >> work to make my clumsy scripts. I likely won't have time or skill to >>> >> fix >>> >> problems. If you notice something's not right (e.g. why won't the >>> >> packaged >>> >> versions use Aqua widgets?) you'll have to investigate and fix it >>> >> yourself >>> >> (then share the answer hopefully). >>> >> >>> >> All that said, email me off-list if you understand my cautions and are >>> >> interested in testing -- and improving upon -- what I've put together. >>> >> >>> >> Shanti >>> >> >>> >> _______________________________________________ >>> >> Digikam-users mailing list >>> >> [hidden email] >>> >> https://mail.kde.org/mailman/listinfo/digikam-users >>> >> >>> > _______________________________________________ >>> > Digikam-users mailing list >>> > [hidden email] >>> > https://mail.kde.org/mailman/listinfo/digikam-users >>> _______________________________________________ >>> Digikam-users mailing list >>> [hidden email] >>> https://mail.kde.org/mailman/listinfo/digikam-users >> >> >> >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users >> Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Gilles Caulier-4
Hi I have set up digiKam on MOS W7 and there the things are going well. I also intended to do so on my MacBook Air 11 Yosemite (Mid 2011) but there the digiKam does't start. The application icon shows up on the Dock, disappears and is followed by drkonqi.app and the ladybug icon - they also fade away.On Mon, May 4, 2015 at 11:04 AM, Gilles Caulier <[hidden email]> wrote: Shanti, -- ================================== Guðbjartur Kristófersson Heima: + 354 552 1099 Mobil: + 354 895 5341 [hidden email] http://www.mr.is/gk http://www.mr.is/~gk/jfr/ordskyr/ http://www.mr.is/~gk/efr/eordskyr/ http://www.mr.is/~gk/OO/ ================================== _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
What do you see as debug trace when you start digiKam from a console ?
Gilles Caulier 2015-05-04 13:50 GMT+02:00 Guðbjartur Kristófersson <[hidden email]>: > Hi > > I have set up digiKam on MOS W7 and there the things are going well. I also > intended to do so on my MacBook Air 11 Yosemite (Mid 2011) but there the > digiKam does't start. The application icon shows up on the Dock, disappears > and is followed by drkonqi.app and the ladybug icon - they also fade away. > > This looks like "Incompatible software" but nothing is to be found in that > mac osx folder. > > I followed the README.MACOSX.txt paper. I am patient and can wait for help > if it is out there. > > Regards, > Gudbjartur Kristofersson > > On Mon, May 4, 2015 at 11:04 AM, Gilles Caulier <[hidden email]> > wrote: >> >> Shanti, >> >> I will review your scripts and packaging rules after 4.10.0 planned >> next week. I'm also busy with lessons writing in my office. I must >> complete it in few days. >> >> After that, i will update macports install on my Macbook pro, and i >> will try to build digiKam DMG using your scripts. I'm sure that >> questions will come. >> >> Best >> >> Gilles Caulier >> >> 2015-04-17 6:18 GMT+02:00 Account, Listserv <[hidden email]>: >> > Gilles and Veaceslav -- First, I appreciate your years of work on the >> > digikam project. Thank you. >> > >> > In response to Gilles' question: The packaging script uses a staging >> > directory to hold files actually needed to run digikam and the other >> > applications. I made a list through trial and error, of libraries, >> > configuration files, icons, etc. which otool couldn't identify but which >> > should be included. These include the runtime libraries, or at least the >> > ones whose absence caused a problem that I noticed (e.g. the qtmysql >> > library). I manually added them to the list files to be run through the >> > dependency lister and copied to the package. >> > >> > I presume that manually listing files for inclusion will cause the >> > script or >> > finished packages to break whenever the runtime dependencies change. But >> > I'm >> > not aware of any automated way to prepare that list. >> > >> > I sent you links to download the scripts, after adding some comments. >> > Hopefully those and the readme will provide enough explanation to be >> > comprehensible. I don't mind if you put them on the git repository if >> > that >> > would be useful, but I suggest they should be sanity-checked by someone >> > who >> > knows what they're doing first. >> > >> > Please let me know if you have questions. >> > >> > Shanti >> > >> > On Thu, Apr 16, 2015 at 3:29 PM, Gilles Caulier >> > <[hidden email]> >> > wrote: >> >> >> >> Shanti, >> >> >> >> thanks to share your experience. >> >> >> >> I would to know more your your bin packaging workflow under OSX. I use >> >> MacBook pro here, so, if your host your script in digiKam git >> >> repository, i will able to build bin package for next version >> >> >> >> Your script must be documented. A text file is enough to host with >> >> script. We need to know all dependencies, settings, OSX-XCode-macports >> >> version to use, etc... >> >> >> >> Q : how did you solve KDE run time dependency with you package. For >> >> ex, digiKam still to use KIO-Slave. How did you package it ? >> >> >> >> Gilles Caulier >> >> >> >> 2015-04-16 21:12 GMT+02:00 Veaceslav Munteanu >> >> <[hidden email]>: >> >> > Hello, >> >> > >> >> > good work. >> >> > >> >> > I guess we can but your packaging scripts on the git, since we also >> >> > have different bootstrap stripts for different linux distribution. >> >> > >> >> > Having them on the git, somebody else can pick them up and improve, >> >> > if >> >> > needed. >> >> > >> >> > Veaceslav >> >> > >> >> > On Thu, Apr 16, 2015 at 8:51 PM, Account, Listserv >> >> > <[hidden email]> wrote: >> >> >> I have assembled two digikam 4.9.0 binary packages for OS X, >> >> >> including >> >> >> external MySQL database support. They were made using bash/python >> >> >> scripts to >> >> >> build it from MacPorts in a a virtual machine. One was built with a >> >> >> +debug >> >> >> variant, the other isn't. >> >> >> >> >> >> I've seen regular requests for OS X binary packages on the web page >> >> >> and >> >> >> this >> >> >> list, as well as complaints about the length/complexity/reliability >> >> >> of >> >> >> building digikam with MacPorts. So I figure I should share -- if you >> >> >> would >> >> >> like to test them, email me directly and I'll send you a link. >> >> >> >> >> >> I'm not posting links to the list for two reasons. First, I don't >> >> >> want >> >> >> someone to just grab and install binary packages, expecting a >> >> >> stable, >> >> >> official digikam release, instead of a risky bastardized derivation >> >> >> that >> >> >> I've cobbled together. I'm not a coder. This is my first crack at >> >> >> packaging >> >> >> a MacOS application. The build/package scripts include "rm -rf" but >> >> >> not >> >> >> error checking. My testing has been limited to opening digikam and >> >> >> showfoto, looking through my photos, and some photo manipulations. >> >> >> Some >> >> >> photographs I rotated using my digikam 4.0.0 package were corrupted >> >> >> -- >> >> >> I >> >> >> don't know if that was due to my packaging. Anyone who is testing >> >> >> the >> >> >> packages or scripts should be very cautious -- back up the photos >> >> >> and >> >> >> the >> >> >> computer it's running on, test it in a VM, etc.. >> >> >> >> >> >> Second, I don't think I'll have time to properly support OS X binary >> >> >> releases. From what I can tell, properly scripting this build and >> >> >> package >> >> >> process would have been be simple for someone who knows what they're >> >> >> doing. >> >> >> Due obligations and lack of skill, it's taken me over a year of >> >> >> intermittent >> >> >> work to make my clumsy scripts. I likely won't have time or skill to >> >> >> fix >> >> >> problems. If you notice something's not right (e.g. why won't the >> >> >> packaged >> >> >> versions use Aqua widgets?) you'll have to investigate and fix it >> >> >> yourself >> >> >> (then share the answer hopefully). >> >> >> >> >> >> All that said, email me off-list if you understand my cautions and >> >> >> are >> >> >> interested in testing -- and improving upon -- what I've put >> >> >> together. >> >> >> >> >> >> Shanti >> >> >> >> >> >> _______________________________________________ >> >> >> Digikam-users mailing list >> >> >> [hidden email] >> >> >> https://mail.kde.org/mailman/listinfo/digikam-users >> >> >> >> >> > _______________________________________________ >> >> > Digikam-users mailing list >> >> > [hidden email] >> >> > https://mail.kde.org/mailman/listinfo/digikam-users >> >> _______________________________________________ >> >> Digikam-users mailing list >> >> [hidden email] >> >> https://mail.kde.org/mailman/listinfo/digikam-users >> > >> > >> > >> > _______________________________________________ >> > Digikam-users mailing list >> > [hidden email] >> > https://mail.kde.org/mailman/listinfo/digikam-users >> > >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users > > > > > -- > ================================== > Guðbjartur Kristófersson > Heima: + 354 552 1099 > Mobil: + 354 895 5341 > [hidden email] > http://www.mr.is/gk > http://www.mr.is/~gk/jfr/ordskyr/ > http://www.mr.is/~gk/efr/eordskyr/ > http://www.mr.is/~gk/OO/ > ================================== > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Ok I am not experienced in linux. Where can I get the debug trace?Can I run debug in Terminal and on what apps/files? Gudbjartur Kristofersson On Mon, May 4, 2015 at 12:02 PM, Gilles Caulier <[hidden email]> wrote: What do you see as debug trace when you start digiKam from a console ? -- ================================== Guðbjartur Kristófersson Heima: + 354 552 1099 Mobil: + 354 895 5341 [hidden email] http://www.mr.is/gk http://www.mr.is/~gk/jfr/ordskyr/ http://www.mr.is/~gk/efr/eordskyr/ http://www.mr.is/~gk/OO/ ================================== _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Look here :
https://www.digikam.org/contrib Gilles Caulier 2015-05-04 14:41 GMT+02:00 Guðbjartur Kristófersson <[hidden email]>: > Ok > > I am not experienced in linux. Where can I get the debug trace? > > Can I run debug in Terminal and on what apps/files? > > Regards, > Gudbjartur Kristofersson > > On Mon, May 4, 2015 at 12:02 PM, Gilles Caulier <[hidden email]> > wrote: >> >> What do you see as debug trace when you start digiKam from a console ? >> >> Gilles Caulier >> >> 2015-05-04 13:50 GMT+02:00 Guðbjartur Kristófersson <[hidden email]>: >> > Hi >> > >> > I have set up digiKam on MOS W7 and there the things are going well. I >> > also >> > intended to do so on my MacBook Air 11 Yosemite (Mid 2011) but there the >> > digiKam does't start. The application icon shows up on the Dock, >> > disappears >> > and is followed by drkonqi.app and the ladybug icon - they also fade >> > away. >> > >> > This looks like "Incompatible software" but nothing is to be found in >> > that >> > mac osx folder. >> > >> > I followed the README.MACOSX.txt paper. I am patient and can wait for >> > help >> > if it is out there. >> > >> > Regards, >> > Gudbjartur Kristofersson >> > >> > On Mon, May 4, 2015 at 11:04 AM, Gilles Caulier >> > <[hidden email]> >> > wrote: >> >> >> >> Shanti, >> >> >> >> I will review your scripts and packaging rules after 4.10.0 planned >> >> next week. I'm also busy with lessons writing in my office. I must >> >> complete it in few days. >> >> >> >> After that, i will update macports install on my Macbook pro, and i >> >> will try to build digiKam DMG using your scripts. I'm sure that >> >> questions will come. >> >> >> >> Best >> >> >> >> Gilles Caulier >> >> >> >> 2015-04-17 6:18 GMT+02:00 Account, Listserv <[hidden email]>: >> >> > Gilles and Veaceslav -- First, I appreciate your years of work on the >> >> > digikam project. Thank you. >> >> > >> >> > In response to Gilles' question: The packaging script uses a staging >> >> > directory to hold files actually needed to run digikam and the other >> >> > applications. I made a list through trial and error, of libraries, >> >> > configuration files, icons, etc. which otool couldn't identify but >> >> > which >> >> > should be included. These include the runtime libraries, or at least >> >> > the >> >> > ones whose absence caused a problem that I noticed (e.g. the qtmysql >> >> > library). I manually added them to the list files to be run through >> >> > the >> >> > dependency lister and copied to the package. >> >> > >> >> > I presume that manually listing files for inclusion will cause the >> >> > script or >> >> > finished packages to break whenever the runtime dependencies change. >> >> > But >> >> > I'm >> >> > not aware of any automated way to prepare that list. >> >> > >> >> > I sent you links to download the scripts, after adding some comments. >> >> > Hopefully those and the readme will provide enough explanation to be >> >> > comprehensible. I don't mind if you put them on the git repository if >> >> > that >> >> > would be useful, but I suggest they should be sanity-checked by >> >> > someone >> >> > who >> >> > knows what they're doing first. >> >> > >> >> > Please let me know if you have questions. >> >> > >> >> > Shanti >> >> > >> >> > On Thu, Apr 16, 2015 at 3:29 PM, Gilles Caulier >> >> > <[hidden email]> >> >> > wrote: >> >> >> >> >> >> Shanti, >> >> >> >> >> >> thanks to share your experience. >> >> >> >> >> >> I would to know more your your bin packaging workflow under OSX. I >> >> >> use >> >> >> MacBook pro here, so, if your host your script in digiKam git >> >> >> repository, i will able to build bin package for next version >> >> >> >> >> >> Your script must be documented. A text file is enough to host with >> >> >> script. We need to know all dependencies, settings, >> >> >> OSX-XCode-macports >> >> >> version to use, etc... >> >> >> >> >> >> Q : how did you solve KDE run time dependency with you package. For >> >> >> ex, digiKam still to use KIO-Slave. How did you package it ? >> >> >> >> >> >> Gilles Caulier >> >> >> >> >> >> 2015-04-16 21:12 GMT+02:00 Veaceslav Munteanu >> >> >> <[hidden email]>: >> >> >> > Hello, >> >> >> > >> >> >> > good work. >> >> >> > >> >> >> > I guess we can but your packaging scripts on the git, since we >> >> >> > also >> >> >> > have different bootstrap stripts for different linux distribution. >> >> >> > >> >> >> > Having them on the git, somebody else can pick them up and >> >> >> > improve, >> >> >> > if >> >> >> > needed. >> >> >> > >> >> >> > Veaceslav >> >> >> > >> >> >> > On Thu, Apr 16, 2015 at 8:51 PM, Account, Listserv >> >> >> > <[hidden email]> wrote: >> >> >> >> I have assembled two digikam 4.9.0 binary packages for OS X, >> >> >> >> including >> >> >> >> external MySQL database support. They were made using bash/python >> >> >> >> scripts to >> >> >> >> build it from MacPorts in a a virtual machine. One was built with >> >> >> >> a >> >> >> >> +debug >> >> >> >> variant, the other isn't. >> >> >> >> >> >> >> >> I've seen regular requests for OS X binary packages on the web >> >> >> >> page >> >> >> >> and >> >> >> >> this >> >> >> >> list, as well as complaints about the >> >> >> >> length/complexity/reliability >> >> >> >> of >> >> >> >> building digikam with MacPorts. So I figure I should share -- if >> >> >> >> you >> >> >> >> would >> >> >> >> like to test them, email me directly and I'll send you a link. >> >> >> >> >> >> >> >> I'm not posting links to the list for two reasons. First, I don't >> >> >> >> want >> >> >> >> someone to just grab and install binary packages, expecting a >> >> >> >> stable, >> >> >> >> official digikam release, instead of a risky bastardized >> >> >> >> derivation >> >> >> >> that >> >> >> >> I've cobbled together. I'm not a coder. This is my first crack at >> >> >> >> packaging >> >> >> >> a MacOS application. The build/package scripts include "rm -rf" >> >> >> >> but >> >> >> >> not >> >> >> >> error checking. My testing has been limited to opening digikam >> >> >> >> and >> >> >> >> showfoto, looking through my photos, and some photo >> >> >> >> manipulations. >> >> >> >> Some >> >> >> >> photographs I rotated using my digikam 4.0.0 package were >> >> >> >> corrupted >> >> >> >> -- >> >> >> >> I >> >> >> >> don't know if that was due to my packaging. Anyone who is testing >> >> >> >> the >> >> >> >> packages or scripts should be very cautious -- back up the photos >> >> >> >> and >> >> >> >> the >> >> >> >> computer it's running on, test it in a VM, etc.. >> >> >> >> >> >> >> >> Second, I don't think I'll have time to properly support OS X >> >> >> >> binary >> >> >> >> releases. From what I can tell, properly scripting this build and >> >> >> >> package >> >> >> >> process would have been be simple for someone who knows what >> >> >> >> they're >> >> >> >> doing. >> >> >> >> Due obligations and lack of skill, it's taken me over a year of >> >> >> >> intermittent >> >> >> >> work to make my clumsy scripts. I likely won't have time or skill >> >> >> >> to >> >> >> >> fix >> >> >> >> problems. If you notice something's not right (e.g. why won't the >> >> >> >> packaged >> >> >> >> versions use Aqua widgets?) you'll have to investigate and fix it >> >> >> >> yourself >> >> >> >> (then share the answer hopefully). >> >> >> >> >> >> >> >> All that said, email me off-list if you understand my cautions >> >> >> >> and >> >> >> >> are >> >> >> >> interested in testing -- and improving upon -- what I've put >> >> >> >> together. >> >> >> >> >> >> >> >> Shanti >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> Digikam-users mailing list >> >> >> >> [hidden email] >> >> >> >> https://mail.kde.org/mailman/listinfo/digikam-users >> >> >> >> >> >> >> > _______________________________________________ >> >> >> > Digikam-users mailing list >> >> >> > [hidden email] >> >> >> > https://mail.kde.org/mailman/listinfo/digikam-users >> >> >> _______________________________________________ >> >> >> Digikam-users mailing list >> >> >> [hidden email] >> >> >> https://mail.kde.org/mailman/listinfo/digikam-users >> >> > >> >> > >> >> > >> >> > _______________________________________________ >> >> > Digikam-users mailing list >> >> > [hidden email] >> >> > https://mail.kde.org/mailman/listinfo/digikam-users >> >> > >> >> _______________________________________________ >> >> Digikam-users mailing list >> >> [hidden email] >> >> https://mail.kde.org/mailman/listinfo/digikam-users >> > >> > >> > >> > >> > -- >> > ================================== >> > Guðbjartur Kristófersson >> > Heima: + 354 552 1099 >> > Mobil: + 354 895 5341 >> > [hidden email] >> > http://www.mr.is/gk >> > http://www.mr.is/~gk/jfr/ordskyr/ >> > http://www.mr.is/~gk/efr/eordskyr/ >> > http://www.mr.is/~gk/OO/ >> > ================================== >> > >> > _______________________________________________ >> > Digikam-users mailing list >> > [hidden email] >> > https://mail.kde.org/mailman/listinfo/digikam-users >> > >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users > > > > > -- > ================================== > Guðbjartur Kristófersson > Heima: + 354 552 1099 > Mobil: + 354 895 5341 > [hidden email] > http://www.mr.is/gk > http://www.mr.is/~gk/jfr/ordskyr/ > http://www.mr.is/~gk/efr/eordskyr/ > http://www.mr.is/~gk/OO/ > ================================== > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Hi I am most likely in the deep end of the swimming pool. bjartur@ubuntu:~$ gdb GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) Quit (gdb) On Mon, May 4, 2015 at 12:45 PM, Gilles Caulier <[hidden email]> wrote: Look here : -- ================================== Guðbjartur Kristófersson Heima: + 354 552 1099 Mobil: + 354 895 5341 [hidden email] http://www.mr.is/gk http://www.mr.is/~gk/jfr/ordskyr/ http://www.mr.is/~gk/efr/eordskyr/ http://www.mr.is/~gk/OO/ ================================== _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
No, you don't need GDB yet on your mac. Just run digiKam executable
installed somewhere in Applications/Macports/KDE. Run it from the console with debug spaces enable with kdebugdialog program installed through KDE. It's explained on contrib page from digikam.org All messages will be printed on the console. Gilles Caulier 2015-05-04 16:30 GMT+02:00 Guðbjartur Kristófersson <[hidden email]>: > Hi > I am most likely in the deep end of the swimming pool. > > Giving the command gdb in Mac Terminal I get: > -bash: gdb: command not found > > In my virtual linux/xubuntu on my PC I get in Terminal: > > bjartur@ubuntu:~$ gdb > GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1 > Copyright (C) 2014 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "i686-linux-gnu". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>. > Find the GDB manual and other documentation resources online at: > <http://www.gnu.org/software/gdb/documentation/>. > For help, type "help". > Type "apropos word" to search for commands related to "word". > (gdb) Quit > (gdb) > > Do I have to set GDB up on my mac? > > On Mon, May 4, 2015 at 12:45 PM, Gilles Caulier <[hidden email]> > wrote: >> >> Look here : >> >> https://www.digikam.org/contrib >> >> Gilles Caulier >> >> 2015-05-04 14:41 GMT+02:00 Guðbjartur Kristófersson <[hidden email]>: >> > Ok >> > >> > I am not experienced in linux. Where can I get the debug trace? >> > >> > Can I run debug in Terminal and on what apps/files? >> > >> > Regards, >> > Gudbjartur Kristofersson >> > >> > On Mon, May 4, 2015 at 12:02 PM, Gilles Caulier >> > <[hidden email]> >> > wrote: >> >> >> >> What do you see as debug trace when you start digiKam from a console ? >> >> >> >> Gilles Caulier >> >> >> >> 2015-05-04 13:50 GMT+02:00 Guðbjartur Kristófersson <[hidden email]>: >> >> > Hi >> >> > >> >> > I have set up digiKam on MOS W7 and there the things are going well. >> >> > I >> >> > also >> >> > intended to do so on my MacBook Air 11 Yosemite (Mid 2011) but there >> >> > the >> >> > digiKam does't start. The application icon shows up on the Dock, >> >> > disappears >> >> > and is followed by drkonqi.app and the ladybug icon - they also fade >> >> > away. >> >> > >> >> > This looks like "Incompatible software" but nothing is to be found in >> >> > that >> >> > mac osx folder. >> >> > >> >> > I followed the README.MACOSX.txt paper. I am patient and can wait for >> >> > help >> >> > if it is out there. >> >> > >> >> > Regards, >> >> > Gudbjartur Kristofersson >> >> > >> >> > On Mon, May 4, 2015 at 11:04 AM, Gilles Caulier >> >> > <[hidden email]> >> >> > wrote: >> >> >> >> >> >> Shanti, >> >> >> >> >> >> I will review your scripts and packaging rules after 4.10.0 planned >> >> >> next week. I'm also busy with lessons writing in my office. I must >> >> >> complete it in few days. >> >> >> >> >> >> After that, i will update macports install on my Macbook pro, and i >> >> >> will try to build digiKam DMG using your scripts. I'm sure that >> >> >> questions will come. >> >> >> >> >> >> Best >> >> >> >> >> >> Gilles Caulier >> >> >> >> >> >> 2015-04-17 6:18 GMT+02:00 Account, Listserv >> >> >> <[hidden email]>: >> >> >> > Gilles and Veaceslav -- First, I appreciate your years of work on >> >> >> > the >> >> >> > digikam project. Thank you. >> >> >> > >> >> >> > In response to Gilles' question: The packaging script uses a >> >> >> > staging >> >> >> > directory to hold files actually needed to run digikam and the >> >> >> > other >> >> >> > applications. I made a list through trial and error, of libraries, >> >> >> > configuration files, icons, etc. which otool couldn't identify but >> >> >> > which >> >> >> > should be included. These include the runtime libraries, or at >> >> >> > least >> >> >> > the >> >> >> > ones whose absence caused a problem that I noticed (e.g. the >> >> >> > qtmysql >> >> >> > library). I manually added them to the list files to be run >> >> >> > through >> >> >> > the >> >> >> > dependency lister and copied to the package. >> >> >> > >> >> >> > I presume that manually listing files for inclusion will cause the >> >> >> > script or >> >> >> > finished packages to break whenever the runtime dependencies >> >> >> > change. >> >> >> > But >> >> >> > I'm >> >> >> > not aware of any automated way to prepare that list. >> >> >> > >> >> >> > I sent you links to download the scripts, after adding some >> >> >> > comments. >> >> >> > Hopefully those and the readme will provide enough explanation to >> >> >> > be >> >> >> > comprehensible. I don't mind if you put them on the git repository >> >> >> > if >> >> >> > that >> >> >> > would be useful, but I suggest they should be sanity-checked by >> >> >> > someone >> >> >> > who >> >> >> > knows what they're doing first. >> >> >> > >> >> >> > Please let me know if you have questions. >> >> >> > >> >> >> > Shanti >> >> >> > >> >> >> > On Thu, Apr 16, 2015 at 3:29 PM, Gilles Caulier >> >> >> > <[hidden email]> >> >> >> > wrote: >> >> >> >> >> >> >> >> Shanti, >> >> >> >> >> >> >> >> thanks to share your experience. >> >> >> >> >> >> >> >> I would to know more your your bin packaging workflow under OSX. >> >> >> >> I >> >> >> >> use >> >> >> >> MacBook pro here, so, if your host your script in digiKam git >> >> >> >> repository, i will able to build bin package for next version >> >> >> >> >> >> >> >> Your script must be documented. A text file is enough to host >> >> >> >> with >> >> >> >> script. We need to know all dependencies, settings, >> >> >> >> OSX-XCode-macports >> >> >> >> version to use, etc... >> >> >> >> >> >> >> >> Q : how did you solve KDE run time dependency with you package. >> >> >> >> For >> >> >> >> ex, digiKam still to use KIO-Slave. How did you package it ? >> >> >> >> >> >> >> >> Gilles Caulier >> >> >> >> >> >> >> >> 2015-04-16 21:12 GMT+02:00 Veaceslav Munteanu >> >> >> >> <[hidden email]>: >> >> >> >> > Hello, >> >> >> >> > >> >> >> >> > good work. >> >> >> >> > >> >> >> >> > I guess we can but your packaging scripts on the git, since we >> >> >> >> > also >> >> >> >> > have different bootstrap stripts for different linux >> >> >> >> > distribution. >> >> >> >> > >> >> >> >> > Having them on the git, somebody else can pick them up and >> >> >> >> > improve, >> >> >> >> > if >> >> >> >> > needed. >> >> >> >> > >> >> >> >> > Veaceslav >> >> >> >> > >> >> >> >> > On Thu, Apr 16, 2015 at 8:51 PM, Account, Listserv >> >> >> >> > <[hidden email]> wrote: >> >> >> >> >> I have assembled two digikam 4.9.0 binary packages for OS X, >> >> >> >> >> including >> >> >> >> >> external MySQL database support. They were made using >> >> >> >> >> bash/python >> >> >> >> >> scripts to >> >> >> >> >> build it from MacPorts in a a virtual machine. One was built >> >> >> >> >> with >> >> >> >> >> a >> >> >> >> >> +debug >> >> >> >> >> variant, the other isn't. >> >> >> >> >> >> >> >> >> >> I've seen regular requests for OS X binary packages on the web >> >> >> >> >> page >> >> >> >> >> and >> >> >> >> >> this >> >> >> >> >> list, as well as complaints about the >> >> >> >> >> length/complexity/reliability >> >> >> >> >> of >> >> >> >> >> building digikam with MacPorts. So I figure I should share -- >> >> >> >> >> if >> >> >> >> >> you >> >> >> >> >> would >> >> >> >> >> like to test them, email me directly and I'll send you a link. >> >> >> >> >> >> >> >> >> >> I'm not posting links to the list for two reasons. First, I >> >> >> >> >> don't >> >> >> >> >> want >> >> >> >> >> someone to just grab and install binary packages, expecting a >> >> >> >> >> stable, >> >> >> >> >> official digikam release, instead of a risky bastardized >> >> >> >> >> derivation >> >> >> >> >> that >> >> >> >> >> I've cobbled together. I'm not a coder. This is my first crack >> >> >> >> >> at >> >> >> >> >> packaging >> >> >> >> >> a MacOS application. The build/package scripts include "rm >> >> >> >> >> -rf" >> >> >> >> >> but >> >> >> >> >> not >> >> >> >> >> error checking. My testing has been limited to opening >> >> >> >> >> digikam >> >> >> >> >> and >> >> >> >> >> showfoto, looking through my photos, and some photo >> >> >> >> >> manipulations. >> >> >> >> >> Some >> >> >> >> >> photographs I rotated using my digikam 4.0.0 package were >> >> >> >> >> corrupted >> >> >> >> >> -- >> >> >> >> >> I >> >> >> >> >> don't know if that was due to my packaging. Anyone who is >> >> >> >> >> testing >> >> >> >> >> the >> >> >> >> >> packages or scripts should be very cautious -- back up the >> >> >> >> >> photos >> >> >> >> >> and >> >> >> >> >> the >> >> >> >> >> computer it's running on, test it in a VM, etc.. >> >> >> >> >> >> >> >> >> >> Second, I don't think I'll have time to properly support OS X >> >> >> >> >> binary >> >> >> >> >> releases. From what I can tell, properly scripting this build >> >> >> >> >> and >> >> >> >> >> package >> >> >> >> >> process would have been be simple for someone who knows what >> >> >> >> >> they're >> >> >> >> >> doing. >> >> >> >> >> Due obligations and lack of skill, it's taken me over a year >> >> >> >> >> of >> >> >> >> >> intermittent >> >> >> >> >> work to make my clumsy scripts. I likely won't have time or >> >> >> >> >> skill >> >> >> >> >> to >> >> >> >> >> fix >> >> >> >> >> problems. If you notice something's not right (e.g. why won't >> >> >> >> >> the >> >> >> >> >> packaged >> >> >> >> >> versions use Aqua widgets?) you'll have to investigate and fix >> >> >> >> >> it >> >> >> >> >> yourself >> >> >> >> >> (then share the answer hopefully). >> >> >> >> >> >> >> >> >> >> All that said, email me off-list if you understand my cautions >> >> >> >> >> and >> >> >> >> >> are >> >> >> >> >> interested in testing -- and improving upon -- what I've put >> >> >> >> >> together. >> >> >> >> >> >> >> >> >> >> Shanti >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> >> Digikam-users mailing list >> >> >> >> >> [hidden email] >> >> >> >> >> https://mail.kde.org/mailman/listinfo/digikam-users >> >> >> >> >> >> >> >> >> > _______________________________________________ >> >> >> >> > Digikam-users mailing list >> >> >> >> > [hidden email] >> >> >> >> > https://mail.kde.org/mailman/listinfo/digikam-users >> >> >> >> _______________________________________________ >> >> >> >> Digikam-users mailing list >> >> >> >> [hidden email] >> >> >> >> https://mail.kde.org/mailman/listinfo/digikam-users >> >> >> > >> >> >> > >> >> >> > >> >> >> > _______________________________________________ >> >> >> > Digikam-users mailing list >> >> >> > [hidden email] >> >> >> > https://mail.kde.org/mailman/listinfo/digikam-users >> >> >> > >> >> >> _______________________________________________ >> >> >> Digikam-users mailing list >> >> >> [hidden email] >> >> >> https://mail.kde.org/mailman/listinfo/digikam-users >> >> > >> >> > >> >> > >> >> > >> >> > -- >> >> > ================================== >> >> > Guðbjartur Kristófersson >> >> > Heima: + 354 552 1099 >> >> > Mobil: + 354 895 5341 >> >> > [hidden email] >> >> > http://www.mr.is/gk >> >> > http://www.mr.is/~gk/jfr/ordskyr/ >> >> > http://www.mr.is/~gk/efr/eordskyr/ >> >> > http://www.mr.is/~gk/OO/ >> >> > ================================== >> >> > >> >> > _______________________________________________ >> >> > Digikam-users mailing list >> >> > [hidden email] >> >> > https://mail.kde.org/mailman/listinfo/digikam-users >> >> > >> >> _______________________________________________ >> >> Digikam-users mailing list >> >> [hidden email] >> >> https://mail.kde.org/mailman/listinfo/digikam-users >> > >> > >> > >> > >> > -- >> > ================================== >> > Guðbjartur Kristófersson >> > Heima: + 354 552 1099 >> > Mobil: + 354 895 5341 >> > [hidden email] >> > http://www.mr.is/gk >> > http://www.mr.is/~gk/jfr/ordskyr/ >> > http://www.mr.is/~gk/efr/eordskyr/ >> > http://www.mr.is/~gk/OO/ >> > ================================== >> > >> > _______________________________________________ >> > Digikam-users mailing list >> > [hidden email] >> > https://mail.kde.org/mailman/listinfo/digikam-users >> > >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users > > > > > -- > ================================== > Guðbjartur Kristófersson > Heima: + 354 552 1099 > Mobil: + 354 895 5341 > [hidden email] > http://www.mr.is/gk > http://www.mr.is/~gk/jfr/ordskyr/ > http://www.mr.is/~gk/efr/eordskyr/ > http://www.mr.is/~gk/OO/ > ================================== > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by S Kulkarni
I seen your script to make DMG file use Packages freeware application.
http://s.sudre.free.fr/Software/Packages/about.html There is an alternative to Packages ? Typically, XCode from Apple which is mandatory to build DMG do not include a similar tool ? Currently, i test first build script... Gilles Caulier 2015-04-16 20:51 GMT+02:00 Account, Listserv <[hidden email]>: > I have assembled two digikam 4.9.0 binary packages for OS X, including > external MySQL database support. They were made using bash/python scripts to > build it from MacPorts in a a virtual machine. One was built with a +debug > variant, the other isn't. > > I've seen regular requests for OS X binary packages on the web page and this > list, as well as complaints about the length/complexity/reliability of > building digikam with MacPorts. So I figure I should share -- if you would > like to test them, email me directly and I'll send you a link. > > I'm not posting links to the list for two reasons. First, I don't want > someone to just grab and install binary packages, expecting a stable, > official digikam release, instead of a risky bastardized derivation that > I've cobbled together. I'm not a coder. This is my first crack at packaging > a MacOS application. The build/package scripts include "rm -rf" but not > error checking. My testing has been limited to opening digikam and > showfoto, looking through my photos, and some photo manipulations. Some > photographs I rotated using my digikam 4.0.0 package were corrupted -- I > don't know if that was due to my packaging. Anyone who is testing the > packages or scripts should be very cautious -- back up the photos and the > computer it's running on, test it in a VM, etc.. > > Second, I don't think I'll have time to properly support OS X binary > releases. From what I can tell, properly scripting this build and package > process would have been be simple for someone who knows what they're doing. > Due obligations and lack of skill, it's taken me over a year of intermittent > work to make my clumsy scripts. I likely won't have time or skill to fix > problems. If you notice something's not right (e.g. why won't the packaged > versions use Aqua widgets?) you'll have to investigate and fix it yourself > (then share the answer hopefully). > > All that said, email me off-list if you understand my cautions and are > interested in testing -- and improving upon -- what I've put together. > > Shanti > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |