From: Daniel M. G. <dm...@uv...> - 2006-10-23 15:55:59
|
Hi Max, Max> That is fine with me. However, the binaries on my site are different from the Max> "official" 2.8.4 release...in a good way! They *are* binary compatible with Max> PTStitcher and PTMender. I know I'm contradicting the conventional wisdom Max> here, but these versions of PTMender.exe and PTStitcher.exe both work with Max> pano12.dll. How is this possible? It is because the change that "broke" Max> binary compatibility happened just before 2.8.4 was released, and these files Max> are from immediately prior to that change. You have the right to distribute the code, but please don't call it 2.8.4. It is confusing. The official 2.8.4 is different than the one you are distributing. Please call it something different. Perhaps 2.8.4m? It will avoid confusion with the users. Max> I think that folks will need/use PTStitcher for some time to come. In addition Max> to fisheye support which reportedely does not work (I haven't tested), PTMender Max> still doesn't do feathering and crashes in a nasty way if fed some of the Max> script parameters that work quite happily with PTStitcher (e.g. Max> colour/brightness correction). Version 2.4.5pre4 of pano13 supports all colour and brightness corrections and should not crash under any circumstances. Max> I use MingW, and I've never been able to build using the autotools either. It Max> sounds like a good idea in the Unix world, but seems to cause problems in the Max> the Windows world! Unfortunately, the test suite relies on this as well, so Max> I'm not sure how much use of the test suite should be expected from Windows Max> developers! Look into Makefile.am in each of the tests directories. It is a very simple process. Just run the script panoAutomateTest.pl with the name of the script to test. >> I think that pano12 is going to go into indefinite bugfix mode given >> that maintaining this binary compatability is such a drag...pano13 is >> the focus of development for PTmender etc... it will be numbered 3.0.0 >> or something to differentiate it from pano12. Max> My guess is that pano12 will be more-or-less abandonned as developers make Max> changes to the pano13 code, but not pano12. It is a shame because until/unless Max> someone rewrites PTMorpher, PTInterpolate, PTStereo and all the other Panorama Max> Tools programs, we'll still need to rely on pano12 for those to work. Max> As for documentation, I think this would be an enormous help. I haven't looked Max> recently, but last time I checked, the code was hard or impossible to find, and Max> I found multiple versions of build instructions...none of which appeared to Max> work! I think you mean bild instructions under Windows. In the unix world (both Linux and Mac OS) they are: ./boostrap ./configure make -- Daniel M. German "When asked whether or not we are Marxists, our position is the same as that of a physicist or a biologist who is asked if he is a `Newtonian', or if Che Guevara -> he is a `Pasteurian'" http://turingmachine.org/ http://silvernegative.com/ dmg (at) uvic (dot) ca replace (at) with @ and (dot) with . |