[Digikam-users] digiKam Software Collection 3.4.0 is out...

[Benjamin Girault]

2013/9/8 Elle Stone <l.elle.stone at gmail.com>:
> On 9/8/13, Benjamin Girault <benjamin.girault at gmail.com> wrote:
>> As I said before, installing outside KDE install prefix is tricky. Can
>> you start a new thread in the mailing list for that? I can help you if
>> you get stuck, it's just that we may need to exchange a few more
>> emails.
>
> The next time I have a reason to test digiKam from git, may I take you
> up on your kind offer at that point?

Any time.

>>> Also, I'd really like to install digiKam after disabling almost all of
>>> the kipi plugins, along with face recognition, geo-location, and
>>> versioning. Can any of these be disabled at build time?
>
> With "make" rather than cmake usually there is a ./configure file that
> allows setting of certain options. Is there something similiar with
> cmake?

./configure an unreadable script generated by an ugly (in my opinion)
and old build systems (namely, the autotools). Many project stick to
it maybe because a lot of work was put into the autotools scripts, but
build systems like CMake have a wider range of features. Note that a
project whose build system is CMake still using make for the
compilation...

As for option switches during configuration prior to compilation, I
think that it's only a matter of implementing it (or not). At the
moment, for the Kipi-plugins, at don't see any in the CMakeLists.txt
file. If that's something you want, maybe you can open an entry in the
bugzilla?

> The only kipi plugin I actually use is import/export from/to remote
> computer (which is a strange label for exporting images to another
> drive on my own computer, but that's what the plugin is called). A
> long time ago I built digikam without most of the kipi plugins by
> deleting the individual plugin build folders. But I forget exactly
> what I did and was hoping there were configurable options.

You can manually delete (or comment) any line beginning with
"ADD_SUBDIRECTORY" in extra/kipi-plugins/CMakeLists.txt (except for
"common") you do not need.

>> I do not think that there is a way to prevent plugin from being built
>> (except for missing depencies, but some of those plugins have none).
>> However, you still can disable them in digiKam's configuration.
>
> It seems that every time I upgrade digiKam all those plugins get
> re-enabled again.

Maybe another bugzilla entry then?

-- 
Benjamin.