> Thanks for the info. > Out of curiosity, is there a reason why it is not a single branch with 2 > build targets, but one branch 32, and patches for 64? > > Thanks, > > nick
That's definitely my goal and on my todo in the coming weeks. The big reason for it not being yet resolved is that the initial goal was to get it working, and get it out there, so that other people can reproduce it. There are a lot of hardcoded interdependencies in the project files on various libraries, and the projects come from several different distributions - some source, some binary, some from svn repos, etc. Being familiar with the process as I am now, it isn't a hard thing, in terms of technical difficulty, it's just a matter of going through everything and checking. My priority at present has been more in the experimenting with the low-hanging fruit of optimizations, as that seems to be able to benefit a larger crowd than the build process smoothing. The patches aren't just for 64-bit though, I should mention. The patches at present are meant to simplify a much longer process that even 32-bit users had to go through in resolving the various conflicts/issues (eg: updating solution files to VS2008, changing paths/dependencies, etc). It's just that the patches at present, in addition to resolving everything for 32-bit, introduce the new 64-bit configurations as options. You end up with 4 projects - Debug, RelMinSize, Release, RelWithDebInfo - and two configurations - 32-bit and 64-bit. You just can't change the configuration of Hugin without also going back through and updating a number of things (from enblend/enfuse to recompiling wxWidgets + OpenEXR etc) Does that help any? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
