2010/7/23 Eric O'Brien <[email protected]>
> For what it's worth...
>
> I have very little idea of what I'm doing here, but I managed to compile
> this on my Macintosh. It may not have been completely "successful" however.
>
> The program ended up at /usr/Application/Hugin.app, along with separate
> programs "HuginStitchProject.app" and "PTBatcherGUI.app."
>
> The program will *run* but the stitching window opens, displays three lines
> of text, then vanishes too quickly for me to read what those lines were.
> Maybe this is just a symptom of what you are describing?
>
> In regards to trying to track this sort of thing down, is Hugin and friends
> writing to any log(s)?
>
> eo
>
>
>
for the analysis:
@Eric:
- Please check your "~/Library/Logs/CrashReporter" folder. It contains crash
reports (you did see that coming, didn't you). I'm not sure whether you will
find anything there as Hugin didn't crash and HuginStitchProject didn't
start (I think), but you never know.
- Please try to stitch again. Immediately after the vanishing stitching
window, please do a "tail -50 /var/log/systen.log". It will show you the
last 50 lines of the system log. Maybe it mentions something.
- Are you sure they are in "/usr/Application/" instead of
"/usr/Applications/" (mind the ending "s" in Applications)?
- Are they not in /usr/local ?
(I'm still not done rebuilding all the stuff, so this is a theoretical
approach but I'm quite sure of it.)
I think the problem is that when starting the stitching, Hugin searches for
HuginStitchProject (as binary). The current cmake compilation does build
three bundles: Hugin.app, HuginStitchProject.app and PTBatcherGui.app.
As mentioned by Eric, the bundles are installed in /usr//Applications.
The HuginStitchProject binary simply can't be found.
Inside the XCode bundle the (internal) PATHS are well defined and the binary
can be found.
Error/Problem 1: The /Applications/MacPorts folder is not in the PATH. Even
the bundle can't be found.
Error/Problem 2: Even if the folder that containds the bundles would have
been in the PATH, the binaries still can't be found as the binaries are not
in the PATH. They are "hidden" inside the bundle like
<Binary>.app/Contents/MacOS/<Binary>.
Error/Problem 3: The applications should never have been installed in
/usr/Applications, but in /usr/local/Applications), or did you specify that
prefix?
Possible solutions (still for 2010.2?):
A) Don't build bundles when using cmake. Use the plain "unix way" and
install the plain binaries inside the prefix. That worked up and including
some recent versions.
B) As a last step in the "make install" (for OSX) create a "ln -s
${CMAKE_INSTALL_PREFIX}/Applications/<binary>.app/Contents/MacOS/<binary>
${CMAKE_INSTALL_PREFIX}/bin/<binary>"
A) would be the simplest to realize. Next to that: a bundle should be "self
containing". The cmake bundles are not.
"Bundled" binaries are in <prefix>/Applications.
Libraries are in <prefix>/lib.
Binaries like pano_info, tca_correct etc. are in <prefix>/bin.
Xrc and data and so on are in <prefix>/share.
If we make it completely "unix like" it will work (as long as the prefix is
in the PATH).
B) Is an option too but it is either "the best of both worlds" or "the worst
of both worlds", depending how you look at it.
@Eric: Just to try: Could you do a "sudo ln -s
/usr/Applications/HuginStitchProject.app/Contents/MacOS/HuginStitchPropject
/usr/bin/HuginStitchProject".
And when you're done trying you could remove the softlink with "sudo rm
/usr/bin/HuginStitchProject".
Change paths accordingly.
My personal preference would be A). Simply because the XCode build provides
a bundle as OSX expects a bundle to be. cmake is not that far yet when it
comes to such a very complicated bundle as Hugin is. It will require extra
scripting and so on. I have been working on that in the past but I abandoned
it as XCode is so much better equipped for that.
If we want to have A) or B) in 2010.2 and if I'm the one supposed to do
that, it will be end of August or early September as I will be on holiday
for 3 weeks next weekend. I have no idea whether I will have internet access
and whether I feel "obliged" to work on it during my holidays.
It should not be a very difficult change but we do need to test.
(Please don't think I'm so arrogant to think that I'm the only who can do
that because there are more who can do that, but I think that I've been the
most active one lately on OSX).
Hoi,
Harry
--
You received this message because you are subscribed to the Google Groups
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
