I did update documentation of the process. http://wiki.panotools.org/Hugin_SDK_%28MSVC_2008%29
and http://wiki.panotools.org/Hugin_SDK_%28MSVC_2008%29_Patches The "downside" to the current process is it requires two sets of SDKs/wxWidgets/etc. The sheer impact of being able to get side-by-side libraries (eg: ilmbase.x64.lib and ilmbase.x32.lib) and all the project settings were way more headache and heartache than I wanted to invest during the weekend that I worked on getting everything running, although that is the logical next step. I'm working on updating the patch set mentioned on the patch pages, as it looks like there was one bit of patch trouble with libpano, although it was resolved in < 5 minutes. Other than that, the directions are still valid and can be done from scratch, as I went through everything again last night when setting up the x32 build for Howard. I've definitely seen benefits to the x64 version - Most notably on autopano-sift-c, as I'm able to throw my larger projects at it and have it go well into the 7-8 gig range on my system generating control points, rather than having to manually break things into chunks. Of course, it sounds like the future work on getting rows/columns setup and optimizing how CP generation gets done will resolve that. Lately I've been working on getting profile-guided versions of enblend/enfuse/hdrmerge and the other 'heavy lifters' of the Hugin stack, and have been seeing performance gains on an order of 10-25%. Quite handy on the large projects. In the enblend-enfuse case, are you talking about a debug binary or a release binary with debug symbols? In the case of Windows, debug symbols are stored in a separate file (.pdb), which makes it easy to ship "Production" exes (with no debug code/memory address alterations/etc), but when crashes occur, be able to load the symbols and correlate the lines/files/etc. Optimizing compilers can naturally make this harder, but my experience with .pdb's is that it's fairly accurate. Using the Intel Compiler chain, which can perform much more rigorous (and intelligent) optimizations, it does get harder to make both "screaming awesome" and "debuggable", but it's not impossible. I was just proposing that the .PDBs be preserved (for the SDK and for Hugin itself) when a release is made, possibly on the project file store, and that way anyone with Visual Studio (including the Express Editions, IIRC), would be able to load those up and step through the crashes. As for the SDK, like I mentioned, everything was built by hand from scratch following the directions on that page, which AFAIK is how Ad is building his, so we'll see. Hopefully Howard will have more information using the build I provided him, and we'll be able to get to the bottom of this. > > Hi again, Ryan, > > Ryan Sleevi wrote: > > I went ahead and built a binary based on the latest SVN (for > native > > x64), through the full build process, including the installer. > > this means that you also built enblend-enfuse? autopano-sift-c? > libpano? > wxwidgets? and all the other SDK components? for native x64? it would > be > nice if you could contribute documentation of the process so that we > can > release an x64 "official" version as well. > > we had a case recently when enblend-enfuse built with debug symbols > would work while stripped of them it would crash - the debug symbols > were just enough "padding" for the overflow not to do too much damage. > I > hope this is not the explanation for why your build does not crash. > > On the other hand, it could be that the bug is in the updated SDK. > Would > have to take the old SDK, re-build the old wxWidgets to support the > GLCanvas and try a recent Hugin SVN against it... > > 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 -~----------~----~----~----~------~----~------~--~---
