Hi Tom, On May 16, 5:40 pm, Tom Glastonbury <[email protected]> wrote: > my Sourceforge user id is "glastonbury".
welcome on board! you now have write privilege to the Hg repo. > I too have limited time (most of mine > is happily sucked up by a 2.5yr old son :-) ), but I'll do what I can to > get it going. you're 0.75yr ahead of me :-) and since my son will go to full time school in September, this summer is his summer with me. > I note that there are no official Win32 (let alone x64) builds for 0.8.0 > and 2010.0. Is there a reason for this other than lack of someone to > produce them? Would it make sense for me to (attempt to) produce them? 2010.0 makes sense. 0.8.0 I don't think. At some point in history there were some really badly broken dependencies that had serious consequences on Windows releases but not on Linux (where they are distributed separately). IIRC it was Autopano-SIFT-C before the release of 2.5.1; and buggy Enblend-Enfuse binaries for a long time. And lack of time / volunteers to test the whole combination to be of equal or better quality than 0.7.0 which had a lot of intensive testing and polishing. The main difference between Windows-Hugin and Linux-Hugin from a user perspective is that in Windows the Hugin installer also delivers Enblend-Enfuse and Autopano-SIFT-C because of the lack of package manager on that platform. In Linux, the Hugin package only delivers Hugin and describes its dependencies, making updates and maintenance easier. > I was interested to read that the idea worked on in the past for the Win > SDK is based around a script that downloads 3rd party source/binaries as > needed. I'll see what I can find in the Wiki, but notably I'd be > interested to know which scripting system was being suggested - perhaps > NSIS is a good choice? AFAIK NSIS is an installer script. Hugin currently uses InnoSetup for the installer. IIRC there is some NSIS cruft from an old (pre 0.7.0) installer. Back then I tried to understand NSIS and found it easier to implement InnoSetup (of which I had previous experience) from scratch. Since then I moved to Linux almost completely. IIRC Ad Huikeshoven contributed a whole script to build Hugin and the installer inside the SDK and I think it was simple batch scripting. > The other issue that I've mentioned before is that of producing x64 and > Win32 builds from one source tree/SDK. If you find it easier to have two separate SDKs, one for x64 and one for Win32, go ahead. In the documentation on the Wiki Guido worked mainly on Win32 and Ryan contributed x64 patches and changes. On Sourceforge we can have unlimited Hg repos, so having one for each Win architecture would not be a problem. When I was still on Windows and maintaining my own SDK I had written some notes for each of the packages / subfolders that together made the SDK. I shall try to find copies of them on my old HDDs. I envisioned a mix between two extremes: the "stable" SDK and the "bleeding edge" SDK, with two different purposes. The stable SDK would contain stable versions of the dependencies for the generation of binaries for productive use by the general public. The bleeding edge SDK would contain the latest versions of the dependenciesfor testing purposes so that we can give early warning / feedback to upstream dependencies in case of bugs there; and we can be alert to changes upstream that affect Hugin. IIRC there are about two dozens packages in the SDK. Not all of them are so dynamic. Ideally there would be a script that fetches them from the web (with wget or something similar); applies patches if applicable; triggers the building process for fetched source packages and re-create the whole SDK from scratch. A less ambitious idea was to create an up to date SDK, make it available for download, and then, as upstream packages update, put up drop-in updates for individual components. Since moving to Ubuntu (and then to Kubuntu late last year) there is no way back for me. I was lured by Microsoft's 40$ student licenses for Windows 7 last autumn but have not been able to make sense of it for me. I occasionally boot my aging Win XP partition for video editing (was not able to replace SONY Vegas so far, nor to use it with WIne on Linux). Yuv -- 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
