[ptx] New HuginOSX is out

[Ippei UKAI]

Hi,

Thank you for your email.

First, Boost is not needed to be compiled; Hugin only requires its 
source. I just preferred to install it because it just worked without 
any effort (except being patient for a while) in my case. Please check 
out the hugin sources and Xcode project, and just make sure the header 
search path lets the compiler find the boost files when called like 
#include <boost/graph/properties.hpp> in the hugin code.

Second, the only reason I stick with xcode is that I do not know 
anything about GNU make. If you can build hugin with wxGTK, that's 
super. If you compile a carbon application with wxMac, then you need to 
make a .app package around the binary 'cause that's how OSX works. The 
odd situation like command-line app opening a window does not let the 
Window Server to handle that window correctly. There are documentations 
how to make app package with command line tools, but I just couldn't 
bother learning all those stuff (I'm a Mac user, not a real unix user).

Lastly, I still have no idea for the optimizer problem. Does the 
current build on Windows handle the single photo optimising technique? 
If not, I have to leave it that to the main developers as I'm simply 
working around the problems specific to the OSX port. I don't think 
there are much platform specific codes around optimizer.

Thanks,
Ippei

-- 
  ->> 鵜飼 一平  (UKAI Ippei) ->>>>>>>>>>>>>>>>>>>>>>>>>
   My general MSN, AIM, and E-Mail: ippei_ukai at mac.com
   Homepage:  http://homepage.mac.com/ippei_ukai/

On 29 Mar 2005, at 01:30, Tim wrote:

> Ippei,
>
> Thank you very much for your work on HuginOSX.  I was in the process of
> doing my own porting when I received your email.  I downloaded the 
> files and
> the program looks and works very well.  However, I regretfully have to
> inform you that the optimizer still doesn't work correctly.  It's still
> returning all zeros.  I would really like to help you solve this 
> problem but
> I haven't had much success using Xcode.  I was able to successfully 
> compile
> the Hugin using the GNU make utility.  However, the program froze when 
> I
> first started it.  At that point I started configuring Xcode so I 
> could do
> some debugging.  I have yet to have a successful compile.  Next, I 
> tried the
> source code from your website using Xcode.  I also had a problem with 
> that
> because boost isn't located in the same path that it was in your 
> machine.  I
> had to use Fink to install boost because bjam hung during compiling.  
> On my
> machine boost is located in /sw/include/.  It seems logical that my 
> next
> step should be to get boost installed without using Fink.  I tried 
> following
> the instructions provided in install-boost.rtf and that is when it got 
> hung
> up.  Do you have any other suggestions on how to get boost installed?  
> It
> may have something to do with my configuration.  I'm using a dual G5 
> with
> Panther 10.3.  Has anyone else had this problem?
>
>
> Thanks.
>
> Tim
>
>
>
>
>
> On 3/28/05 10:38 AM, "Ippei UKAI" <ippei_ukai at mac.com> wrote:
>
>> Hello everyone,
>>
>> Finally the semester is over and I'm now in the easter break:) Through
>> the weekend, I worked on the experimental build of HuginOSX and 
>> updated
>> the files on my web.
>>
>> Please find them on http://homepage.mac.com/ippei_ukai/software/
>>
>> Big news is that, with new release of Mono for OSX, now autopano-sift
>> works on OSX as well! I included some related files, so please try it
>> out.
>>
>> Sadly, I gave up internationalisation, for now, because wxMac 2.5.1
>> does not have working Unicode implementation, and newer versions' XRC
>> is not working. I would love to see both XRC and Unicode on a wxMac
>> version in the future, but all depend on wxMac project team. (Please
>> make donations: http://www.wxwidgets.org/fundraising.htm )
>>
>> autopano-old is no longer included because the better autopano is
>> working (I can send you a copy if you need it). nona is included as
>> there was a request from a user of 'clens' utility.
>>
>> Again, myself didn't do much work on the source code itself, though a
>> couple of fixes will be committed as soon as I get a connection 
>> without
>> this annoyingly strict firewall. Big thanks to the developers who are
>> making progress in the main cvs tree.
>>
>> Cheers,
>> Ippei
>