I think I found the problem. I had recently installed the Glade Win32 developer environment, which had screwed up my hugin build by insisting on pointing to some of its own libraries. Don't ask me why. As the only component of Glade I really needed was the runtime, I uninstalled Glade and that worked.
I built a complete installer including panomatic, autopano-sift-c and enblend/enfuse. Right now it's on my website at http://allardkatan.net/misc/hugin/Hugin08_release_Win32_setup.exe , but I'll move it if it generates too much traffic. The warnings at the first screen of the installer don't make much sense yet because I have not adapted that particular piece of text. Also, because it is based on the officially dubbed 0.8 release 4008, while Ad has already released 4012, the page it refers you to after installation says this is an old version.... This being said, I live in the US now too, so maybe someone else should handle that official release because of patent issues. allard On Jul 17, 11:25 pm, "Ryan Sleevi" <[email protected]> wrote: > Hard to tell exactly what it might be, but the error is stemming from the > fact that you have at least two instances of the JPEG/zlib libraries loaded > (wxjpeg.lib and jpeg.lib via jpeg64.dll, wxzlib.lib z.lib via zlib1.dll). > The latter for each of those is probably coming from one of the other > libraries you built/linked (other than wxWidgets, since it contains its > own).http://wiki.panotools.org/Hugin_SDK_%28MSVC_2008%29_Patchesdetails > some of the changes necessary to the various libraries, which include > updating them to point to wxWdigets for TIFF/JPEG/ZLIB where appropriate. If > I were to wager though, you may want to check exiv2 to make sure it's > linking right, but that's just a guess. Other than that, it's simply a > matter of tracking down which library isn't linking against wxWidgets' > implentation. You can always start with building a fresh SDK > (http://wiki.panotools.org/Hugin_SDK_%28MSVC_2008%29) if you're still not > able to trace it down. > > As to building the installer, I would suspect that Ad might be planning on > doing it, given as how he's been building installers for XP/Vista x32 during > development > (http://adhuikeshoven.pbworks.com/hugin%C2%A0installer%C2%A0for%C2%A0W... > %C2%A0Vista ). He's got 4007 built, and IIRC, the only difference between > 4007 and 4008 was a translation change. > > I don't know if anyone has stepped up for the Win x64 'release' build. Being > in the US, I'm only really able to push a patent-free installer out, and if > people drop in a CP gen that is 32-bit, it's possible there will be WoW64 > issues with filenaming / reg keys / the like between Hugin (native x64) and > the CP gen (32-bit). That's why I hope someone else can step up, so they can > build/ship all the bins (including the CP generators) x64 and potentially > dodge that problem. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
