[Digikam-users] Digikam crashes under MacOS when built using git + MacPorts

[Phil Stanford]

Many thanks for your hints and tips Brad -
I did download the 2.3 tarball last night and gave that a go following your
instructions;
I had some issues with FindMarble.cmake which turned out to be a known
problem, but following the traditional consultation with Google and the
tearing out of a few remaining precious hairs,  it all built and ran OK.

I will also have a go at building from git + your latest patch too and see
how that goes.
Thanks again
Phil


On 11 January 2012 15:50, brad <bkn at ithryn.net> wrote:

>
> > Brad, thanks for your mails, sorry for tardy replies but work gets in the
> > way of fun sometimes .....!
> >
> no worries, i can relate.
>
> >
> > Re this  'too many open files' issue in
> > https://bugs.kde.org/show_bug.cgi?id=289330  -
> > I'm still a bit unclear there;  is it some new feature / behaviour in
> > Digikam  post 2.3  that's now causing this MacOS 'files per process'
> limit
> > to be reached?  I've tried with various versions of qt (4.7.2 - 4.7.4)
> and
> > it doesn't make any difference.
> >
> the digikam code is using a feature of QT, which is not quite working on
> OS X.
> QT's implementation on OS X regarding file-watching has a hard limit of 255
> files, so you have less than 255 images (actually more like 240 images),
> then
> you're all set :). You should actually be able to open the first images
> out of
> your first album (up to, around the first 240 images), i think.
>
> > I saw re the albumwatch.patch  file but my knowledge doesn't extend to
> > knowing where or how to apply that!
> >
> Take another look at the bug report, there's more info on applying the
> patch.
> https://bugs.kde.org/show_bug.cgi?id=289330
>
> i just submitted another patch which is pretty straightforward to apply.
> Try
> the following,
>  * checkout the source again and run download-repos
>  * download the patch from the bug report (
> 0001-disable-filewatching-on-OS-X-
> but-dir-watching-still-.patch)
>  * change directories to digikam-sc/core
>  * run: git am
> path/tofile/0001-disable-filewatching-on-OS-X-but-dir-watching-
> still-.patch
>  * then go back to digikam-sc, and run bootstrap.macports and compile.
>
> > In terms of my strategy now -
> > It would seem to be sensible for me to try and get a known-working
> version
> > (2.3 from what you say) up and running.
> >
> > I failed to work out how to use git to get a known and released digikam
> > version back from
> >
> https://projects.kde.org/projects/extragear/graphics/digikam/digikam-softwar
> > e-compilation/repository
> >
> >
> > That is probably my lack of knowledge about git of course.
> >
> i have this problem too :) everybody does when they start out, but i'm
> trying
> to get better.
>
> > I also wasn't clear on what the difference was between the above URL and
> > https://projects.kde.org/projects/extragear/graphics/digikam/repository
> >
> This is a little confusing, no doubt. Digikam has a lot of subprojects
> which
> are kept in different git repos. The
> digikam-software-compilation/repository is
> simply a small git repo which doesn't actually have the source code, it's
> just
> meant to be a place holder or stagine area of directories and cmake files.
> When
> you execute download-repos, git pulls down the actually source code for
> digikam and it's subprojects (i.e. plugins and other libraries) which are
> spread across several different git repos. So, the second URL you
> referenced,
> digikam/repository is the core code of digikam -- no plugins or optional
> libraries. This code is downloaded when you execute download-repos.
>
>
> > My final attempt last night was to try and see if I could get things to
> > work by downloading the tarball from
> > http://sourceforge.net/projects/digikam/files/digikam/2.3.0/
> >
> > I unpacked that, and the directories looked similar to what I'd got back
> > using git (for the 2.6 development release) so I followed the
> instructions
> > I had done before,  in
> >
> https://projects.kde.org/projects/extragear/graphics/digikam/repository/revi
> > sions/master/entry/README.MACOSX
> >
> > However, that fell at the first hurdle, when I ran the ./download-repos
> > script it fell over -
> >
> If you use the tar ball from the web, then download-repos is not necessary,
> all the code should already be in the tar ball, and therefor already on
> your
> system. Follow the instructions on this page for compilation from the tar
> file:
>  http://digikam.org/drupal/download/tarball
>
>
> >
> > I would still like to crack this issue of not having to rely on the
> > Macports version getting updated by the supporter - even though that is
> by
> > far the simplest way of getting things working!  Having prodded quite a
> bit
> > with people's help,  with a bit more understanding (and learning on my
> > part!) I feel it ought to be achievable!
> >
> it's all a learning process. as long as you feel it's achievable, then it
> is
> :).
>
> > So if there are still any further hints to be had re either getting hold
> of
> > a specific Digikam release under git,   or on how to make the tarball
> work
> > on MacOS,  I would be grateful ........
> >
> try the above information -- hopefully that's give you a push in the right
> direction.
>
>
> cheers,
>  - brad
>
> _______________________________________________
> Digikam-users mailing list
> Digikam-users at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20120112/77695ed2/attachment.html>