svn 4450 hugin installer for Windows Vista
Ad Huikeshoven
As attachment I do include two files:
1 hugin.iss the innoset installer compiler script - with some minor modifications compared to the one at svn ... for example hard coded paths to the directory with precompiled versions of autopano
2 build-hugin-installer.bat the automated build batch file (which doesn't include updating autopano and libpano yet, nor compiling autopano) and has a peculiar way to get the date and format it, which depends on the localisation of your vista version - this one differs from the previous one I posted tweaked to compile a 2009.2 version
As a precautionary note: both are script that depend on what is preinstalled on the machine and depend on specific locations of files. So both scripts are only examples and need some editing before it will work on your machine.
Ad Huikeshoven
Yuval Levy
Ad Huikeshoven wrote:
> Last night I did build from scratch and got 4 fatal compile errors. This
> morning I build from scratch and got a new installer for hugin for Windows
> Vista, you can find at http://hugin.huikeshoven.org/
for all practical purposes, this is Hugin 2009.2.0_RC1. although the
results differ from the results on OSX and on Linux depending on the
dependencies (pun intended).
I admit that the spurious errors are worrying me. they may indicate
problems in the build chain and thus in the quality of the result.
> As attachment I do include two files:
thanks, will look at them and integrate them in the SVN repository, with
your notes.
> this one differs from the previous one
> I posted tweaked to compile a 2009.2 version
so if I understand correctly, this bat file is for 2009.2 and the
previous one is for trunk? or are there also other changes?
Yuv
Oskar Sander
I don't get this install to work properly. (I used hugin uninstall for previous installation first)
It doesn't find any control point matches for me with (default installation options), although it reports features found. This seems to happen on all projects.
after a few tries with different sets of images previously used in other projects i tried create control point in an already optimized project, and got this error.
User or developer fault? ;-)
/O
--
/O
Oskar Sander
Destination location:
C:\Program Files\Hugin
Setup type:
Default installation (Autopano-SIFT-C)
Selected components:
Hugin
Hugin Language Pack
Enblend/Enfuse
Autopano-SIFT-C (Patent issues in the USA!)
Panotools Command Line Tools
Start Menu folder:
Hugin
Additional tasks:
System:
Set Default Settings? (partially implemented)
Additional icons:
Create desktop icons
only for the current user
Hugin
Enblend Droplets
Enfuse Droplets
Create additional entries in Program Files menu
Yuval Levy
> User or developer fault? ;-)
nobody's really.
Autopano-SIFT-C is known to be unstable/broken in trunk. And the
previous version is known to have memory leaks that are fixed in trunk.
Ad informs you on his download site about some of the more dynamic
dependencies in his installers. Specifically for the hugin-SVN4450
installer he used autopano-SIFT-C SVN 4450.
The safest thing for you to do is to go back to that version of Hugin
that worked for you.
If you're adventurous, you can look into C:\Program Files\Hugin\bin (or
wherever Hugin is installed on your system) and replace
autopano-sift-c.exe with the older one (from the version of Hugin that
worked for you).
You can have both versions of Hugin side by side by installing in a
folder different than the default folder. In this case, the two versions
will share settings (i.e. registry!). If the settings are messed up,
there is a convenient "reset defaults" button in the preferences.
thanks for testing and reporting. keep them coming
Yuv
Oskar Sander
How do would you like me to report on this problem (is it known?) i only find 3 open bug reports in the tracker when searching on autopano-sift-c. What traces would be of interest?
When Ad reports SVN4450 for hugin and APC alike, is it possible to see what the APC revision using this?
I would assume that the relevant APV version is something else like for example 4217.
Cheers
Bruno Postle
>No worries, I rather use the RC version of hugin, so it is the matter of
>finding a decent autopano-sift-c.exe to run with it.
>
>How do would you like me to report on this problem (is it known?) i only
>find 3 open bug reports in the tracker when searching on autopano-sift-c.
>What traces would be of interest?
It is almost certainly this bug:
autopano-sift-c --projection parameter no longer works - ID: 2858780
http://sourceforge.net/tracker/?func=detail&aid=2858780&group_id=77506&atid=550441
You can test by removing the "--projection %f,%v" part of the
Autopano-SIFT-C options in Preferences -> Control point Creator.
Matching should then work (but without conformal feature detection).
--
Bruno
Oskar Sander
It seems to do the trick. Ad, If you are building a new installer with RC1, please add another default setting for autopano-sift-c. Then it will run "out of the box"
Cheers
It is almost certainly this bug:
autopano-sift-c --projection parameter no longer works - ID: 2858780
http://sourceforge.net/tracker/?func=detail&aid=2858780&group_id=77506&atid=550441
--
/O
Bruno Postle
>
>It seems to do the trick. Ad, If you are building a new installer with
>RC1, please add another default setting for autopano-sift-c. Then it will
>run "out of the box"
No, please nobody distribute snapshots of the autopano-sift-C trunk
as various stuff is broken.
The 2.5.0 release had a serious memory leak which is fixed in
svn3895, so this would be a good version to package. This is the
version that will work with the default hugin-2009.2.0 control point
settings.
--
Bruno
>2009/9/23 Bruno Postle <br...@postle.net>
Yuval Levy
> The 2.5.0 release had a serious memory leak which is fixed in
> svn3895, so this would be a good version to package. This is the
> version that will work with the default hugin-2009.2.0 control point
> settings.
since we do not know when trunk will be fixed, may I suggest to:
1) tag autopano-sift-C revision 3895
2) release it (tarball, binaries, etc.)
for the release, we need a version number. would 2.5.2 do? then we can
call the next one 2.5.4. alternatively: 2.5.0a ?
Yuv
Bruno Postle
Something like that, we could call it 2.5.1 since I don't think this
was ever released.
I think it needs a branch as there is also Ippei's patch (svn4213)
which fixes the 'filenames with whitespace bug', and probably some
other minor fixes.
--
Bruno
Yuval Levy
> Something like that, we could call it 2.5.1 since I don't think this
> was ever released.
>
> I think it needs a branch as there is also Ippei's patch (svn4213)
> which fixes the 'filenames with whitespace bug', and probably some
> other minor fixes.
ok, I implemented inside autopano-sift-C the same layout as in Hugin;
the 2.5.1 codeline is started ,Ippei's patch applied to it, version
number bumped.
the process is the same as I have documented for Hugin [0].
I did already 3.7.1 - there won't be much 3.7.2 (unless somebody
identifies other changes from trunk that are worth back porting).
The next step is to go through 3.7.3 and issue a beta1. Then in one week
an RC1 and in two weeks autopano-sift-C 2.5.1 is released.
It would be nice if there was one volunteer who is not a current
maintainer, builder, or coder, that would go through the rest of the
process. I'll be happy to mentor. Volunteers?
Yuv
[0] http://wiki.panotools.org/Development_of_Open_Source_tools#Release