[Digikam-devel] the new pano tool

Benjamin GIRAULT benjamin.girault at gmail.com
Wed Oct 12 18:23:12 BST 2011


2011/10/11 bkn <bkn at ithryn.net>:
> Fortunately, there are basically two ways of installing Hugin on OS X.
>  1) Using macports, in which case the binaries would be in /opt/local/bin
>  2) Using the standalone Hugin package directly from Hugin's website, in which
> case the binaries would be in /Applications/Hugin/HuginTools/
>
> Perhaps if digikam is being run on OS X these paths could be explicitly added
> to the environment after cleanEnv. is called. This might also solve the
> problem of locating the binaries in the first place in those cpfindbinary.cpp
> classes and the like. This would likely be helpful for those OS X users who
> are not savvy enough to edit their PATH, or for those who want to launch the
> app from the OS X Dock.
>
> Does this sound like a good general solution? i'm hoping there is a more
> elegant way to at these paths without hardcoding them (actually using `kde4-
> config --prefix` appears to work in the first case of using macports).

There should be a way to not hardcode such a thing, since the QT and
KDE APIs are meant for OS abstraction.

Have you set your PATH with /etc/paths, or in a file in the directory
/etc/paths.d/? Those seems to be the standard way of setting the PATH
under Mac OSX.

-- 
Benjamin.



More information about the Digikam-devel mailing list