[MacPorts] #51605: Hugin App bundles not finding binaries

[MacPorts]

#51605: Hugin App bundles not finding binaries
---------------------------+--------------------------------
 Reporter:  rpspringuel@…  |      Owner:  macports-tickets@…
     Type:  defect         |     Status:  new
 Priority:  Normal         |  Milestone:
Component:  ports          |    Version:  2.3.4
 Keywords:                 |       Port:  hugin-app
---------------------------+--------------------------------
 On Mac OS 10.10.5, hugin-app creates app bundles in the MacPorts folder.
 The command-line tools, naturally, are in `/opt/local/bin`.  However, when
 launching processes using the GUI apps, the program looks for the command
 line tools in the same location as the GUI apps by default.  Now, while
 I've been able to correct this via the preferences inside hugin for
 enblend and enfuse, I can't seem to correct this for nona and exiftool.

 I've been able to bypass the problem for nona by creating a symlink from
 where the GUI is looking
 (`/Applications/MacPorts/PTBatchGUI.app/Contents/MacOS/nona`) to where
 nona actually is (`/opt/local/bin/nona`), but said solution is likely to
 be fragile and break when MacPorts updates hugin in the future.

 Something similar seems to be occuring with exiftool, which is installed
 as /opt/local/bin/exiftool-5.22 (i.e. the PERL versionnumber is appended).
 However, in this case the log file isn't descriptive enough for me to tell
 where it's looking for exiftool so I don't know where to put the symlink
 to get around this (`/usr/local/bin` doesn't work).

 When I reported
 this([https://answers.launchpad.net/hugin/+question/294894]) to the hugin
 developers, I got the following response:

 > In our CMake build system there are 2 possibilities to build on Mac:
 > 1. A *nix way: Here the tools are installed and search in a fixed path,
 which is given during building. (For the external tools, like enblend,
 enfuse, exiftool, also the PATH environment variable is taken into account
 to search for the program.)
 > 2. Building an OS/X bundle. In this case all the tools are bundled into
 a bundled and searched in the bundled.
 >
 > Here it sounds there is something mixed up. I don't know what the
 > MacPort maintainer do to build it (which patches are applied and with
 > which options it is build). So please report your problems to the
 > MacPort maintainers.

-- 
Ticket URL: <https://trac.macports.org/ticket/51605>
MacPorts <https://www.macports.org/>
Ports system for OS X