On October 1, 2010 09:07:47 pm Matthew Petroff wrote: > On Sep 30, 4:17 pm, Henk Tijdink <[email protected]> wrote: > > when you go to the preference screen and > > you load the defaults the path to the CPG folder is gone and Hugin > > expects then the control point generators in the Hugin binary folder. > > This is because the paths are hard-coded into the hugin binary and > have nothing to do with the installer.
The hard-coded paths are just defaults in case nothing else is set in the registry. You can set the registry from the installer, at least this is what I did back in the 0.7.0 days. The syntax will be different with NSIS, and there have been changes to the CP generators, but the principle is still the same. Check out how the old InnoSetup baed installer [0] around line 214 handled it. > It does however make sense to > have the binary in the installer revert to the paths used by the > installer, so I patched the binary to do so. This updated build is > available here: http://www.box.net/shared/meeaobr9ec why patch the binaries if it can be done with the installer by simply setting a couple of registry entries? note: I did not look at your patch, i don't use Windows. Yuv [0] http://hugin.hg.sourceforge.net/hgweb/hugin/hugin/file/default/platforms/windows/installer/hugin_prerelease.iss
signature.asc
Description: This is a digitally signed message part.
