[ptx] HuginOSX news

[Ippei UKAI]

Hello. Now I have arrived at Edinburgh and got internet connection in 
my room.
The network provided by university accommodation here got apparently 
all the ports closed to the outside world, and nothing other than 
things going through proxy works. So, I will try asking computer 
service, but it is unlikely to get cvs and other connection for a 
while.

Anyway, I should answer the question about Mac port's source structures.

First of all, .DS_Store files are OSX's system file. Just ignore it. It 
has nothing more than cache and settings etc. of the file browser, and 
has no meaning on other operating system.

Second, I'm using Xcode's native build system, which has nothing to do 
with Makefile, although I'm fixing Xcode project every time when 
Makefiles are changed, so that it does the same. The reason is simply 
that I do not know how to write make files, how to build Carbon App 
with command line tools, and it takes only few minutes to make a new 
native build target on Xcode without any of those knowledge. (Xcode 
gave me an advantage in speed as well while at my home in Japan as I 
and my father have total three Macs to do distributed compilation.) You 
could integrate Mac port into Makefile, but I have no idea how.

At last, the resource included in HuginOSX are not very special to 
Hugin Mac port. Resources used on Mac are Icons and application bundle 
info plist file (XML file with application information), .rsrc resource 
file required by and provided with wx2.5.1, xrc folder just copying 
from src/hugin to the Resource folder of the Application bundle.

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

On 9 Sep 2004, at 00:28, Pablo d'Angelo wrote:

> On Tue, 07 Sep 2004, Ippei UKAI wrote:
>
>> Hello,
>>
>> Thank you for your interests! I've got two emails about Hugin on OSX
>> last week asking how to compile. I have updated all the files on my
>> homepage, binaries and sources. A kind of installation guide for
>> libraries have been included in the sources.
>
> Hmm, how about the build system. can it be added easily? (See lots of
> ._.DS_Store files and so on in your sources.)
> Are all these files needed to build hugin on the mac? Or would it be
> possible to use the existing Makefiles? (with different compilerflags, 
> of
> cause). This would make maintance easier, since I would only need to
> update the Makefiles, if new classes etc. occur.
>
> I have noticed that wxWindows allready contains something like 
> ressources
> (basically a virtual file system compiled into the binary executable, 
> if I
> remember correctly). How does that differ from the MacOS specific
> ressources you have used? Maybe it's possible to do the ressources in a
> cross platform way (its probably useful on windows as well).
>
>> If the developers on not only Mac but other systems downloaded the
>> sources and checked what changes have been made, I would be more than
>> happy.
>
> I have just added your changes to the current CVS. they should be 
> available
> whenever the anonymous CVS get updated. (less than 24 hours). Could 
> you try
> and see if it works out of the box?
>
> If you want, I can also add you to the developers list on sourceforge,
> so you can commit fixes for the mac directly. There is also a mailing 
> list
> for all changes in the CVS repository, maybe that's interesting as 
> well.
>
>
>> If you are Mac user, please try out the binaries and report bugs and
>> problems on this mailing list. As the new semester is starting, I'm
>> going to be busy, but I would live to try my best, and, moreover, 
>> there
>> are many other developers as well in the community.
>
> I'll try to add the MacOS stuff more timely next time. Good luck with 
> your
> studies.
>
> Btw. is it ok to add a link from the hugin homepage to your site?
>
> ciao
>   Pablo
>